date:20170221

Isn't that the opposite of how Feature Freeze Exception requests go,
that it should be more likely to be accepted if there are *not* many
changes?

Yesterday, it was reported that Ubuntu will have GNOME 3.24. And the
first thing a GNOME packager for another distro said was well it isn't
really GNOME 3.24 if you don't have *all* of it.

Now my first choice is that the MIR for PCRE2 be approved and I've been
disappointed in how bug 163 has been handled so far.

I got the impression I was being told to try to revert the PCRE2 stuff
in vte/gnome-terminal (since trying to port everything in main to PCRE2
is an unreasonable request). So it would be frustrating after I do the
work if the answer is both No to the MIR and No to doing the update with
the reverts.

I believe the reverts are safe for zesty; my maintainability concerns
are more about maybe a year from now when the code has drifted more.

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

Title:
FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
New
Status in vte2.91 package in Ubuntu:
New

Bug description:
gnome-terminal and vte are still at their 3.20 (and 0.44) versions
because they now hard-depend on pcre2, but the pcre2 MIR (LP:
#163) has stalled because there is already one version of pcre in
main and it would be a major task to convert all of main to use pcre2.

So I reverted 3 commits for gnome-terminal and 5 for vte to make that
MIR less urgent. I am concerned about the long-term maintainability of
this approach - the vte patch is over 1600 lines.

gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
Staging PPA for yakkety and zesty for months. I am not aware of any
issues from that. This is slightly different since I haven't tested
those versions without pcre2 until this weekend.

The development cycle for gnome-terminal and vte has been fairly quiet
so I believe it's safe to go ahead and update gnome-terminal to
3.23.90 and vte to 0.47.90.

https://git.gnome.org/browse/gnome-terminal/log
https://git.gnome.org/browse/vte/log

The packages are currently available for testing at

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+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 1450429] Re: Backups configuration duplicated folders

2017-02-21 Thread Donald Pedersen

On Ubuntu 16.04.

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

Title:
  Backups configuration duplicated folders

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04
  unity-control-center 15.04.0+15.04.20150410-0ubuntu1

  Just a small UI bug.
  I'm using the Backups UI from Settings/System to backup files to a network 
share.
  I've removed the ~/Downloads folder from the 'Folders to ignore' section.
  When I open the Backups UI now for the first time, the folders in 'Folders to 
save' and 'Folders to ignore' are correct.
  But when I go back to All Settings and then open Backups again, each folder 
in these sections will be shown twice.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 13:03:05 2015
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-02-11 (77 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (0 days ago)
  usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1450429/+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 1666443] [NEW] [MacBookPro9, 2, Cirrus Logic CS4206, Mic, Internal] Recording problem

2017-02-21 Thread Bagus Tris

Public bug reported:

I cannot record any sound with internal microphone.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bagustris   1799 F pulseaudio
CurrentDesktop: Unity
Date: Tue Feb 21 15:35:35 2017
InstallationDate: Installed on 2017-01-09 (42 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_Type: None of the above
Title: [MacBookPro9,2, Cirrus Logic CS4206, Mic, Internal] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP91.88Z.00D3.B0E.1610201614
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B0E.1610201614:bd10/20/2016:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.name: MacBookPro9,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-21T14:46:25.281945

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [MacBookPro9,2, Cirrus Logic CS4206, Mic, Internal] Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I cannot record any sound with internal microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bagustris   1799 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 21 15:35:35 2017
  InstallationDate: Installed on 2017-01-09 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: None of the above
  Title: [MacBookPro9,2, Cirrus Logic CS4206, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D3.B0E.1610201614
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B0E.1610201614:bd10/20/2016:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.name: MacBookPro9,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-02-21T14:46:25.281945

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666443/+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 792085] Re: Automatic remount of safely removed USB 3.0 drive

2017-02-21 Thread Martin Wildam

I can also confirm fix after upgrading from something older to
4.4.0-63-generic. Thanks to everybody who was involved bringing the
solution!

Best wishes, Martin.

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

Title:
  Automatic remount of safely removed USB 3.0 drive

Status in Nautilus:
  New
Status in thunar:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  In Progress
Status in nautilus source package in Precise:
  New
Status in thunar source package in Precise:
  New
Status in udev source package in Precise:
  New
Status in linux source package in Trusty:
  In Progress
Status in nautilus source package in Trusty:
  New
Status in thunar source package in Trusty:
  New
Status in udev source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in Fedora:
  Unknown
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: nautilus

  When I choose "Safely remove drive" context menu entry for an external
  USB drive within a nautilus window or directly clicking on the desktop
  icon, after about 10 seconds the drive is automatically remounted and
  a Nautilus window showing the root folder opens.

  I have noticed that similar already happened with a very old Ubuntu
  version - Bug #110589 and as that is so long time ago I thought it is
  better to open a new bug. Reason of the problem might even be
  completely different.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: nautilus 1:2.32.2.1-0ubuntu13
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Thu Jun  2 23:40:08 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

  break-fix: - 37be66767e3cae4fd16e064d8bb7f9f72bf5c045

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/792085/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

This issue has been fixed by the following four commits.

>From 1b925c0028cdaaf14d4ebd1f07848ba5640915c6 Mon Sep 17 00:00:00 2001 
From: Tony Espy 
Date: Thu, 16 Jun 2016 15:07:33 -0400
Subject: [PATCH] wifi: clear WiFi requested_scan if suppl exits

It's possible for wpa_supplicant to exit with an
outstanding requested_scan pending.  This can lead
to a stall condition where scanning no longer occurs.

https://mail.gnome.org/archives/networkmanager-list/2016-June/msg00117.html
(cherry picked from commit 899d7e5cb1eb3bddaf92de3644c49c9f634b675e)
---

>From eed8fd2e43d244caa856d9993e750ff19ba62fd7 Mon Sep 17 00:00:00 2001 
>   
> 
From: Tony Espy 
Date: Thu, 16 Jun 2016 15:07:32 -0400
Subject: [PATCH] wifi: clear WiFi requested_scan if suppl goes INACTIVE

It's possible for wpa_supplicant to transition to INACTIVE
state with an outstanding requested_scan pending.  This can
lead to a stall condition where scanning no longer occurs.

[thal...@redhat.com: added break statement to avoid fall-through]

https://mail.gnome.org/archives/networkmanager-list/2016-June/msg00116.html
---

>From 788583d9fd35f9a83c932c5fa6ca059e19fcd7c6 Mon Sep 17 00:00:00 2001 
>   
> 
From: Thomas Haller 
Date: Wed, 6 Jul 2016 09:30:46 +0200
Subject: [PATCH] wifi: fix missing pending-action-remove for "scan"

  [1467730406.7343] device (wlp3s0): add_pending_action (2): scan 
already pending
file devices/nm-device.c: line 10443 (nm_device_add_pending_action): should 
not be reached

Fixes: eed8fd2e43d244caa856d9993e750ff19ba62fd7
---

>From f270bc34b4e503d5ba79d6aad1129fb4f49fee05 Mon Sep 17 00:00:00 2001 
>   
> 
From: Thomas Haller 
Date: Tue, 14 Feb 2017 15:10:36 +0100
Subject: [PATCH] device/wifi: block autoconnect while scanning is in progress

We should only start autoconnecting after the scan is complete.
Otherwise, we might activate a shared connection or pick a
connection based on an incomplete scan list.

https://bugzilla.gnome.org/show_bug.cgi?id=770938
(cherry picked from commit 2ab2254dd7336b9b7baa03ea1eb1f1c72f7ab6a8)
---

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

** Patch added: "network-manager_1.2.4-0ubuntu0.16.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4823281/+files/network-manager_1.2.4-0ubuntu0.16.04.2.debdiff

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

2017-02-21 Thread Iain Lane

On Mon, Feb 20, 2017 at 06:15:21PM -, Jeremy Bicha wrote:
> ** Changed in: vte2.91 (Ubuntu)
>Importance: Undecided => Low
> 
> ** Description changed:
> 
>   gnome-terminal and vte are still at their 3.20 (and 0.44) versions
>   because they now hard-depend on pcre2, but the pcre2 MIR (LP: #163)
>   has stalled because there is already one version of pcre in main and it
>   would be a major task to convert all of main to use pcre2.
>   
>   So I reverted 3 commits for gnome-terminal and 5 for vte to make that
>   MIR less urgent. I am concerned about the long-term maintainability of
>   this approach - the vte patch is over 1600 lines.
>   
>   gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3 Staging
>   PPA for yakkety and zesty for months. I am not aware of any issues from
>   that. This is slightly different since I haven't tested those versions
>   without pcre2 until this weekend.
>   
>   The development cycle for gnome-terminal and vte has been fairly quiet
>   so I believe it's safe to go ahead and update gnome-terminal to 3.23.90
>   and vte to 0.47.90.

If there aren't many changes (other than porting to PCRE2), what's the
proposed upside of getting onto the new versions?

It seems risky and annoying to maintain such a patch going forward -
it's only going to become harder to keep it working as time goes on,
until we get to drop it.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+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 1637638] Re: Gnome Software causes heavy prolonged disk on start-up

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

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

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

Title:
  Gnome Software causes heavy prolonged disk on start-up

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  After booting and logging in, it takes a long time for the computer to
  settle down and become properly usable. Heaving hard-disc activity by
  gnome-software which lasts for over a minute. This is revealed by
  `iotop` as the only application with around 99% of the disk access.

  This is a serious problem on single-disk machines as programs can't
  properly start until it's over.

  The program appears to be present in Startup Applications with the
  command `/usr/bin/gnome-software --gapplication-service`, even for the
  guest user.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 28 21:49:59 2016
  InstallationDate: Installed on 2016-06-03 (147 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1637638/+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 1637638] Re: Gnome Software causes heavy prolonged disk on start-up

2017-02-21 Thread gUI

Hi !

Exact same issue on Ubuntu 16.10
On every start, I must wait about 1 minute before being able to open a single 
xterm.

iotop gives exact same result : gnome-software --gapplication-service is
having heavy disk access. Once finished, the system gets back to normal
reactivity.

Really annoying on harddrive laptop.

Is there a known workaround to stop this ?

Thanks !

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

Title:
  Gnome Software causes heavy prolonged disk on start-up

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  After booting and logging in, it takes a long time for the computer to
  settle down and become properly usable. Heaving hard-disc activity by
  gnome-software which lasts for over a minute. This is revealed by
  `iotop` as the only application with around 99% of the disk access.

  This is a serious problem on single-disk machines as programs can't
  properly start until it's over.

  The program appears to be present in Startup Applications with the
  command `/usr/bin/gnome-software --gapplication-service`, even for the
  guest user.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 28 21:49:59 2016
  InstallationDate: Installed on 2016-06-03 (147 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1637638/+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 1639896] Re: Backport support for AMD Polaris

2017-02-21 Thread Timo Aaltonen

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

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

Title:
  Backport support for AMD Polaris

Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs.

  Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6
  backported instead

  [Test case]
  Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration

  [Regression potential]
  This is a stable upstream release, and 16.10 ships the same versions so 
regression potential should be minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

2017-02-21 Thread Iain Lane

Oh come on, there's no hive mind conspiracy against you here, you know
that. It's individual developers answering questions that are asked of
them and giving you their own judgement. If you'd have asked me before
starting this work then I would have given the same answer ("do it only
if the other changes make it worthwhile [and maybe consider cherry-
picking those first if possible]").

The concern is this

 - Big revert patch
 - Can never drop it as long as we don't move to PCRE 2
 - Gets harder to maintain over time
 - No clear path to moving to PCRE 2
 - Given that, does having the new releases bring features and/or fixes that 
mean we should take on these difficulties or is this just taking on an unknown 
amount of work indefinitely just to have a larger number in the version string?

That is a *question*, not an accusation.

Or are you saying that I shouldn't be allowing these considerations to
weigh into Feature Freeze requests, since the net change of *this*
upload will be small?

Maybe that's fair and if that's the case then it means I'm answering as
a fellow desktop team member, not as someone in the release team. In
that case, your two ways to get this upload (three if you count 'ignore
me and upload anyway' as one) are

 - Provide an explanation that this upload is worth the above future 
difficulties
 - Show that the net change is small and convince another member of the release 
team to +1 this request

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+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-21 Thread Treviño

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 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
Status in appmenu-qt5 source package in Xenial:
  Fix Committed
Status in libappindicator source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Xenial:
  New
Status in snapd source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Committed

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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-02-21 Thread Ben

I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by 
removing all xscreensaver remnants (which I believe to be conflicting with 
Light Locker). I did this, but use at your own risk:
```
sudo apt-get remove $(apt-cache search "^xscreensaver" | cut -d ' ' -f1 | tr 
'\n' ' ')
```

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-21 Thread Rik Shaw

@fourdollars does this commit get applied to 16.04 proposed and then to
backports?  I (and I am sure others) would be happy to test this for
xenial but I am unclear as to the path the patches follow to get to the
main repositories.

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus

2017-02-21 Thread Treviño

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

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

Title:
  Window management - Apps raised from indicators sometimes dont have
  the focus

Status in Ayatana Design:
  Fix Committed
Status in Messaging Menu:
  Fix Released
Status in Messaging Menu 13.04 series:
  Fix Released
Status in The Sound Menu:
  Fix Released
Status in The Sound Menu 13.04 series:
  Fix Released
Status in DBus Menu:
  Triaged
Status in MPRIS:
  Confirmed
Status in Ubuntu One Client:
  Fix Committed
Status in empathy package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in libdbusmenu package in Ubuntu:
  Confirmed
Status in sni-qt package in Ubuntu:
  New
Status in tomboy package in Ubuntu:
  Confirmed
Status in ubuntuone-client package in Ubuntu:
  Fix Released
Status in empathy source package in Xenial:
  New
Status in indicator-messages source package in Xenial:
  New
Status in indicator-sound source package in Xenial:
  New
Status in libdbusmenu source package in Xenial:
  New
Status in sni-qt source package in Xenial:
  Fix Committed
Status in tomboy source package in Xenial:
  New
Status in ubuntuone-client source package in Xenial:
  New

Bug description:
  Ubuntu 11.10 beta
  compiz 1:0.9.5.94+bzr2803-0ubuntu5
  unity 4.16.0-0ubuntu1

  1. open banshee, start a song in it and minimize
  2. open another application lets say gnome-terminal
  3. click on the sound menu and select banshee

  What happens
  banshee icon in the launcher wiggles and banshee main window is not shown

  What should happen
  banshee main window should come to focus

  This is a long standing bug which Ted Gould thinks should be fixed at
  window manager's level.

  Some other observations=
  The problem wont happen
  1. if every other app is minimized or
  2. Banshee is the only opened app or
  3. after opening gnome-terminal, banshee window is closed so that it hides to 
the SoundMenu and opened again

  =Comment from Ted Gould=
   tedg, Hi! any thoughts on the long standing bug 627195 ? Its been 
there before unity so I guess we can conclude unity not to be responsible

   om26er, My thought is that window managers should $%#$ get
  fixed... though I haven't convinced smspillaz of it yet.

  =The good rule=
  3v1n0: Indicators should present the application windows by passing to them 
the timestamp of the menu item activation event.

  Unfortunately for indicator-sound, this is not trival as it sounds, since it 
needs a change to the MPRIS dbus specification.
  See comment https://bugs.launchpad.net/ayatana-design/+bug/627195/comments/26 
for more informations.

  For what concerns libappindicator based indicators (such as the one used by 
tomboy), since it's not currently possible in libdbusmenu to pass the event 
during activation (so that clients will be able to get the proper timestamp 
using gtk_get_current_event_time), there are two "hackish" ways:
  1. Use the server time to present a window:
     https://bugzilla.gnome.org/show_bug.cgi?id=688830
  2. Get the event timestamp from the dbus-menu linked to the gtk-menus:
     https://archive.is/2tLX6
  3. Qt applications workaround: http://is.gd/WnW9eN

  Window managers will obey to it.

  ===

  SRU for sni-qt:

  [Test case]

  git clone https://github.com/3v1n0/indicators-examples-snaps
  cd indicators-examples-snaps/qt4-systray
  qmake-qt4
  ./systray

  Close the app, now try to restore it from in the indicator (after having 
played with some app writing text on it such as gnome-terminal or gedit).
  The app should be in foreground now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/627195/+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 1636514] Re: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()

2017-02-21 Thread ivavis

Same problem moving file in an owncloud folder

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

Title:
  nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()

Status in Ubuntu GNOME:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  This crash occurred just after I had asked Nautilus to move several
  large files (in groups) to several different locations. Then I believe
  that I minimized Nautilus and in a few minutes noticed the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.22.1-1ubuntu0~yakkety2 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 25 13:52:09 2016
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-05-15 (162 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcCmdline: nautilus .
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_view_set_cursor_on_cell () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_tree_view_set_cursor_on_cell()
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (5 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   dropbox2015.10.28
   gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1636514/+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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-02-21 Thread O. Farid

Hi Ben, before removing the packages, have you tried to kill the deamon,
suspend & resume to see if there was some effects?

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

I made a PPA at https://launchpad.net/~fourdollars/+archive/ubuntu/lp1585863 to 
include comment #84.
You can try it and give some feedback.

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

Oops, sorry. The package is built failed.
I need to revise the patch again.

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1666545] Re: package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-02-21 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 gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1666545

Title:
  package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  unsure of what is the issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpam-gnome-keyring:amd64 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Feb 21 08:22:24 2017
  DuplicateSignature:
   package:libpam-gnome-keyring:amd64:3.18.3-0ubuntu2
   Setting up libpaper1:amd64 (1.1.24+nmu4ubuntu1) ...
   dpkg: error processing package libpaper1:amd64 (--configure):
subprocess installed post-installation script was killed by signal (Broken 
pipe)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-02-17 (4 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: gnome-keyring
  Title: package libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1666545/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2017-02-21 Thread Raman

I have the same problem. My laptop is Acer Aspire VN7-592G. Internal microphone 
isn't detected. For external microphone the same problem is reproduced. 
At this moment I use usb headset and it works fine.

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

I missed this commit. It should work now.

>From 6eaded9071fbf868476255adb8ee5f416e7ad134 Mon Sep 17 00:00:00 2001 
From: Thomas Haller 
Date: Tue, 14 Feb 2017 12:45:38 +0100
Subject: [PATCH] device: add get_autoconnect_allowed() virtual function

It allows derived classes to override the autoconnect-allowed
state.

We already have

- NM_DEVICE_AUTOCONNECT property, which is two parts:
  - NMDevicePrivate::autoconnect_user, which is settable via
D-Bus by the use, to allow the device to autoconnect.
  - NMDevicePrivate::autoconnect_intern, which is set by
internal decision.
- NM_DEVICE_AUTOCONNECT_ALLOWED signal, where other devices can
  subscribe to block autoconnect. Currently that is only used
  by NMDeviceOlpcMesh.

These two make up for nm_device_autoconnect_allowed().

Add another way to allow derived classes to disable autoconnect
temporarily. This could also be achieved by having the device
subscribe to NM_DEVICE_AUTOCONNECT_ALLOWED of self, or by adding
a signal slot. But a plain function pointer seems easier.

** Patch added: "network-manager_1.2.4-0ubuntu0.16.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+attachment/4823486/+files/network-manager_1.2.4-0ubuntu0.16.04.2.debdiff

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

I don't like the revert idea either.

But like I pointed out almost 4 months ago, there are just 3 options, right?
1. Accept PCRE2 in main
2. Keep gnome-terminal at 3.20 and vte at 0.44 indefinitely
3. Revert the PCRE2 changes, which allows postponing a choice between the first
two.

I don't think #2 is better for maintainability than #3 really (We've
done that with other packages before and it means that Ubuntu will only
get a handful of bugfixes. Long term, it means we'll have created a
mostly dead fork and I'm not convinced we had a good enough reason to do
that. #3 is a fork too but it won't be as dead as quickly.)

I really think #1 is the right answer here but if we go with #3, we can
keep ignoring the MIR for several more months.

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

Title:
FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
New
Status in vte2.91 package in Ubuntu:
New

So I reverted 3 commits for gnome-terminal and 5 for vte to make that
MIR less urgent. I am concerned about the long-term maintainability of
this approach - the vte patch is over 1600 lines.

The development cycle for gnome-terminal and vte has been fairly quiet
so I believe it's safe to go ahead and update gnome-terminal to
3.23.90 and vte to 0.47.90.

https://git.gnome.org/browse/gnome-terminal/log
https://git.gnome.org/browse/vte/log

The packages are currently available for testing at

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

[Desktop-packages] [Bug 1641629] Re: Autocomplete popups are misplaced

2017-02-21 Thread gpothier

Ok, that's probably two separate bugs. I have a 100% reproducible scenario in 
Firefox, even with a single monitor, on an up to date, freshly booted 17.04:
1. Go to https://yoast.com/research/autocompletetype.php
2. Don't input anything and press Submit your name. An extended form appears, 
with fields for name, email, and more
3. Start typing your name in the name field. The autocomplete menu pops up and 
shows several alternatives (assuming you have some autocomplete values 
registered). Do not select anything, but instead keep typing random letters 
until there is no autocomplete match and the autocomplete menu disappears.
4. Go to the email field, and type the first letter of your email (assuming 
your email is registered as an autocomplete value)

Result: the autocomplete menu appears, but it is anchored to the name
field, not the email field. Moreover, it is out of sync with the mouse
position (it behaves as it it was at the correct position, therefore the
highlighted item does not match the mouse position).

If in step 3 you choose an autocomplete entry instead of typing random
stuff and having the menu disappear, the problem does not occur.

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

Title:
  Autocomplete popups are misplaced

Status in Ubuntu GNOME:
  New
Status in firefox package in Ubuntu:
  New
Status in gdm package in Ubuntu:
  New

Bug description:
  Since Ubuntu 16.10, Firefox misplaces autocomplete popups. In the
  attached screenshot, the autocomplete popup is displayed below the
  "Nombre transferencia" field, although the focused field is "Mensaje
  para destinatario", below. Also, moving the mouse pointer below the
  correct field actually highlights completion options as if the menu
  was there (see the mouse pointer position on the screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 49.0.2+build2-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gpothier   3169 F pulseaudio
   /dev/snd/controlC0:  gpothier   3169 F pulseaudio
  BuildID: 20161025164528
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Mon Nov 14 11:57:19 2016
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-01-23 (660 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MostRecentCrashID: bp-604f3b87-472e-4026-8588-3d2122160725
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=49.0.2/20161025164528 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   rhythmbox-mozilla 3.4.1-1ubuntu1
   gnome-shell   3.20.4-0ubuntu2
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-604f3b87-472e-4026-8588-3d2122160725
   bp-1cd058b7-bfd2-4105-a9b4-1852d2160703
   bp-b5b0d8b4-2b5b-40f5-b468-f5eec2160122
   bp-aba8367f-3da0-4f1c-9342-b377f2151224
  UpgradeStatus: Upgraded to yakkety on 2016-10-30 (15 days ago)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN43WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1641629/+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 1665018] Re: client tools ignore -h option without port number

2017-02-21 Thread Dariusz Gadomski

** Tags removed: sts-sponsor

-- 
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:
  Fix Committed

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 1272461] Re: djvu search doesn't list results

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

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

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

Title:
  djvu search doesn't list results

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Evince version 3.10.0-0ubuntu2
  Ubuntu 13.10

  When searching .djvu files, the sidebar appears, but stays empty instead of 
showing a list of results.
  (If it is not possible to list results, I would prefer the sidebar to stay 
hidden.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1272461/+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 1646956] Comment bridged from LTC Bugzilla

2017-02-21 Thread bugproxy

--- Comment From ru...@us.ibm.com 2017-02-21 10:05 EDT---
Thanks Steve.

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

Title:
  ping -I support broken in yakkety version 3:20150815-2ubuntu3
  (multicast test failure)

Status in iputils package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 ==
  ---Problem Description---
  Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x)
   
  Machine Type = S822l1 
   
  ---Steps to Reproduce---
   On Host:  Enable multicast for the test interface
  1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
  2. ip link set enP5p1s0f1 allmulticast on
  root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1
  enP5p1s0f1: flags=4675  mtu 1500
  inet 170.1.1.20  netmask 255.255.255.0  broadcast 170.1.1.255
  inet6 fe80::9abe:94ff:fe5c:f1c1  prefixlen 64  scopeid 0x20
  ether 98:be:94:5c:f1:c1  txqueuelen 1000  (Ethernet)
  RX packets 488  bytes 50254 (50.2 KB)
  RX errors 0  dropped 442  overruns 0  frame 0
  TX packets 25  bytes 2226 (2.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 226  memory 0x3d400100-3d40017f 


  On Peer: --> catch the Test interface from the multicast group
  ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20

   
  ---uname output---
  Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 ==

  I'm able to replicate this behavior in a KVM environment with Yakkety,
  so it does not appear to be related to the specific type of interface.

  From my testing, it looks like the SO_BINDTODEVICE option is not being
  honored, so both broadcasts and multicasts are going out the default
  route device instead of the device specified by -I option to ping.

  I am unable to replicate this on a xenial host with the same 4.8.0-27
  kernel version. so I suspect some other setting is interfering with
  the ability to bind the output to a specific device.

  From my own testing:

  Xenial:

  # ip addr show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enp0s6:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff
  inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe15:b7ba/64 scope link 
 valid_lft forever preferred_lft forever
  3: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fee1:35be/64 scope link 
 valid_lft forever preferred_lft forever

  # ping -I enp0s6 -i 30 224.0.0.1
  PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data.
  64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms
  64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!)
  ^C
  ...

  Yakkety:

  # ip addr show
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: enp0s5:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff
  inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:febe:97ab/64 scope link 
 valid_lft forever preferred_lft forever
  3: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1
 valid_lft forever preferred_lft forever
  inet6 fe80::5054:ff:fe30:d014/64 scope link 
 valid_lft forever preferred_lft forever

  # ping -I enp0s5 -i 30 224.0.0.1
  PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data.
  64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms
  64 bytes from

Re: [Desktop-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-02-21 Thread Ben

I'm afraid I did not, no.

On 21 February 2017 at 10:16, Ben <1434...@bugs.launchpad.net> wrote:

> I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by
> removing all xscreensaver remnants (which I believe to be conflicting with
> Light Locker). I did this, but use at your own risk:
> ```
> sudo apt-get remove $(apt-cache search "^xscreensaver" | cut -d ' ' -f1 |
> tr '\n' ' ')
> ```
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1434351
>
> Title:
>   X fonts and widgets disappear after suspend/resume cycle
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a suspend/resume cycle, the screen comes up normally, but every
>   time I move my mouse over a piece of text, button, widget, etc, the
>   text vanishes and it's replaced by a plain rectangle.
>
>   This does not affect xterm, but it does affect any GTK apps, firefox,
>   etc.
>
>   xfce-panel vanishes, although it's still responding to mouse-clicks.
>   Newly opened menus are grey rectangles.
>
>   The lines underlining menu hotkeys do NOT disappear.
>
>   In the attached screenshot, you can clearly see which buttons I have
>   waved the mouse over, and which I have not.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
>   ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
>   Uname: Linux 3.19.0-9-generic x86_64
>   ApportVersion: 2.16.2-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Mar 19 19:51:37 2015
>   InstallationDate: Installed on 2015-03-05 (14 days ago)
>   InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150218.1)
>   SourcePackage: xserver-xorg-video-intel
>   UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions
>

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1589585] Re: Ubuntu Software tab Installed refreshing endlessly every 2 seconds

2017-02-21 Thread Wayne Ho

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

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

Title:
  Ubuntu Software tab Installed refreshing endlessly every 2 seconds

Status in fwupd package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  New
Status in fwupd source package in Xenial:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in fwupd source package in Yakkety:
  Fix Released
Status in gnome-software source package in Yakkety:
  Triaged

Bug description:
  I have fresh installed Ubuntu 16.04 Desktop 32-bit. After each install
  for years one of the first thing I do is uninstall some of the
  applications that I don't need to preserve some downloading/installing
  of applications that I don't need.

  I opened Ubuntu Software, click on Installed tab and now the problem
  appears. Every two seconds whole screen gets to gray and refreshing
  appears which takes 2 seconds. This loops endlessly. It is very
  frustrating, because Ubuntu Software is unusable in my case.

  I have asked the question on forum:
  http://ubuntuforums.org/showthread.php?t=2326701=13498876 and one of
  suggestion was to remove the software and install it back.

  I did:
  sudo apt install gnome-software
  sudo apt purge gnome-software
  sudo apt autoremove
  sudo apt autoclean
  sudo apt install gnome-software

  Started Ubuntu Software and the problem remains the same.

  P.S. New problem appeared now Ubuntu Software icon on Launcher is not
  the same (orange color), but it has changed (white color). But this is
  not huge problem, just annoyance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Jun  6 18:18:47 2016
  InstallationDate: Installed on 2016-06-03 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1589585/+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 1391219] Re: package fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1 failed to install/upgrade: package fonts-unfonts-core is not ready for configuration cannot configure (c

2017-02-21 Thread Changwoo Ryu

** Changed in: fonts-unfonts-core (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1 failed to
  install/upgrade: package fonts-unfonts-core is not ready for
  configuration  cannot configure (current status `half-installed')

Status in fonts-unfonts-core package in Ubuntu:
  Invalid

Bug description:
  One of my USB 3 ports is not working. Is this a known bug for this
  distro of ubuntu or a hardware issue.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Mon Nov 10 06:57:20 2014
  DuplicateSignature: 
package:fonts-unfonts-core:1.0.3.is.1.0.2-080608-10ubuntu1:package 
fonts-unfonts-core is not ready for configuration  cannot configure (current 
status `half-installed')
  ErrorMessage: package fonts-unfonts-core is not ready for configuration  
cannot configure (current status `half-installed')
  InstallationDate: Installed on 2014-11-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: fonts-unfonts-core
  Title: package fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1 failed to 
install/upgrade: package fonts-unfonts-core is not ready for configuration  
cannot configure (current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-unfonts-core/+bug/1391219/+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 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

This bug was fixed in the package qtmir -
0.5.1+17.04.20170215.1-0ubuntu1

---
qtmir (0.5.1+17.04.20170215.1-0ubuntu1) zesty; urgency=medium

  [ Michał Sawicz ]
  * We're at provides 26 already (LP: #1662608)

  [ Alan Griffiths ]
  * Identify the code that depends directly on mirserver-dev headers

  [ Albert Astals Cid ]
  * Check we provide the same unity-application-impl that we require

  [ Daniel d'Andrada ]
  * Resolve mir cursor names using mir symbols instead of plain strings
(LP: #1662827)

  [ Gerry Boland ]
  * ScreenModel: Only expose windows on displays that are turned on (LP:
#1521403, #1638611, #1656250)
  * Restore lost LTTng tracepoints, and delete unused ones (LP:
#1658084)

  [ Nick Dedekind ]
  * Added Extended Display Information Data (EDID) parsing.

  [ Alan Griffiths, Nick Dedekind ]
  * Iteration 0 of miral::PersistDisplayConfig. This does nothing yet
(and breaks nothing in the process). This MP creates a place (miral-
prototypes) to build prototype miral features and sketches out what
will need to be implemented for PersistDisplayConfig. (LP: #1644189)

 -- Michał Sawicz   Wed, 15 Feb 2017
13:23:17 +

** Changed in: qtmir (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521403/+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 1631288] Re: XV video screen always on top

2017-02-21 Thread dabrain

The bug seems to be fixed now in 16.04 but i encounter often screen
corruption.

** Attachment added: "Screenshot from 2017-02-21 16-16-44.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+attachment/4823487/+files/Screenshot%20from%202017-02-21%2016-16-44.png

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

Title:
  XV video screen always on top

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  When playing a video with vlc, gstreamer(xvimagesink), the video stays on top 
of every X window.
  In VLC this bug can be bypassed disabling overlay video. 
  In Gstreamer using ximagsink is ok too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  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 Oct  7 09:45:31 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Toshiba America Info Systems Skylake Integrated Graphics 
[1179:001d]
 Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d]
  InstallationDate: Installed on 2016-10-03 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: TOSHIBA TECRA Z50-C
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.70
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z50-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z50-C
  dmi.product.version: PT577E-01100GCE
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct  6 17:44:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1237 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1665140] Re: Emoji that should be wide, according to Unicode 9, display incorrectly in the terminal

2017-02-21 Thread Egmont Koblinger

Just for the record:

glibc has just upgraded to Unicode 9.0 in git (forthcoming 2.26 release):
https://sourceware.org/bugzilla/show_bug.cgi?id=20313

** Bug watch added: Sourceware.org Bugzilla #20313
   https://sourceware.org/bugzilla/show_bug.cgi?id=20313

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

Title:
  Emoji that should be wide, according to Unicode 9, display incorrectly
  in the terminal

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When editing Unicode in the terminal, it is important for the terminal
  and applications to agree on the width of characters. Otherwise,
  display glitches will occur.

  In prior versions of Unicode, the character width of emoji was
  "ambiguous". As of Unicode 9, they are supposed to be double-wide and
  take up two character cells. gnome-terminal displays them as
  overlapping, single-wide characters, like it has for a long time. This
  is a problem because many applications I use on Ubuntu now treat emoji
  as double-wide. The behavior of gnome-terminal conflicts with the
  cursor positioning in vim, for example.

  I've long considered gnome-terminal to have the least buggy Unicode
  implementation among terminal applications, and this may no longer be
  the case.

  The *desired behavior* of emoji is that they are double-wide: they
  take up two character cells, advance the cursor by two cells when
  displayed, and text-editing applications move the cursor by two cells
  when moving past them. The *actual behavior* is inconsistent:
  typically, the emoji advance the cursor only by one character cell,
  even though the text-editing cursor moves by two character cells when
  moving past them, causing the cursor to be misaligned with the text.

  I hope this bug reporting interface lets me attach screenshots so I
  can show the example with vim.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 15 16:13:31 2017
  InstallationDate: Installed on 2016-08-09 (190 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1633408] Re: [SRU] 3.22.0 wont allow cut in history pane

I verified the test cases on yakkety-proposed.

By the way, this update also fixes bug 1566513.


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

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

Title:
  [SRU] 3.22.0 wont allow cut in history pane

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

Bug description:
  Impact
  ==
  This update includes the new upstream bugfix 3.22.1 and 3.22.2 releases.

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

  Overview of changes in gnome-calculator 3.22.2:

  Fix reusing results from the history stack #766155
  Ctrl+Backspace should deletes only last number, not everything (bgo#725114)
  Fixed possible errors on currency conversion (bgo#750672)
  Fixed first expression with parentheses (bgo#700617)
  Fixed conversion unit switch, fixes #748732.

  Test Case
  =
  *Fix reusing results from the history stack #766155
   - A click on the equation would replace the current expression
   - A click on the result would append it to the current expression
  * Ctrl+Backspace should deletes only last number, not everything (bgo#725114)
   - input some expression, press Ctrl+Backspace it will delete last number 
instead of clear everything.
  * Fixed possible errors on currency conversion (bgo#750672)
   - gnome-calculator --solve '1500 EUR in USD' you will get just result, no 
more spamming stderr
  * Fixed first expression with parentheses (bgo#700617)
   - 3(7) you will get result: 21
  * Fixed conversion unit switch, fixes #748732
   - Be in Financial mode, choose "Botswana Pula" on the left side and 
"Algerian Dinar" on the right side
  2. Type 1
  3. Click Switch conversation units
  the displayed number will change correctly as long as the currencies switched

  Regression Potential
  
  The uploads are happening under the GNOME Micro Release Exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calculator/+bug/1633408/+subscriptions

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

[Desktop-packages] [Bug 1648992] Re: [SRU] Update gnome-calculator to 3.22.2

I verified the test cases on yakkety-proposed.

The first test case results are a bit unusual, but they fix the
regression so it's ok for now. (If you're curious, see the discussion at
https://bugzilla.gnome.org/766155 )

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

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

Title:
  [SRU] Update gnome-calculator to 3.22.2

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

Bug description:
  Impact
  ==
  This update includes the new upstream bugfix 3.22.1 and 3.22.2 releases.

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

  Overview of changes in gnome-calculator 3.22.2:

  Fix reusing results from the history stack #766155
  Ctrl+Backspace should deletes only last number, not everything (bgo#725114)
  Fixed possible errors on currency conversion (bgo#750672)
  Fixed first expression with parentheses (bgo#700617)
  Fixed conversion unit switch, fixes #748732.

  Test Case
  =
  *Fix reusing results from the history stack #766155
   - A click on the equation would replace the current expression
   - A click on the result would append it to the current expression
  * Ctrl+Backspace should deletes only last number, not everything (bgo#725114)
   - input some expression, press Ctrl+Backspace it will delete last number 
instead of clear everything.
  * Fixed possible errors on currency conversion (bgo#750672)
   - gnome-calculator --solve '1500 EUR in USD' you will get just result, no 
more spamming stderr
  * Fixed first expression with parentheses (bgo#700617)
   - 3(7) you will get result: 21
  * Fixed conversion unit switch, fixes #748732
   - Be in Financial mode, choose "Botswana Pula" on the left side and 
"Algerian Dinar" on the right side
  2. Type 1
  3. Click Switch conversation units
  the displayed number will change correctly as long as the currencies switched

  Regression Potential
  
  The uploads are happening under the GNOME Micro Release Exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1648992/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again

2017-02-21 Thread Yuan-Chen Cheng

I run the test case on xenial with the new package, it works fine and
the test case passed !

But as I replace step 7 to:

close the "user accounts panel" and make sure we quit all instance of
unity-control-center, and launch "user accounts panel" again, and choose
to Re-open the password dialog as in step 4.

Then the test failed with after re-launch user account panel in the way

1. can't ""Click "Unlock" at the top right, and enter the user's password."" 
because the password is clear in step 5.
2. if we just change the password without unlock first, the system request 
password prompt "Authentication is required to change user data". Any password 
won't work for it. Then I need to press 'cancel' button, then the password is 
set, but user still in nopasswdlogin group.

I propose we refine the bug description instead of open a new bug. Feel
free to propose otherwise.


** Tags added: verification-failed

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

Title:
  No password needed to Log in after cancel the password and then reset
  again

Status in Light Display Manager:
  Invalid
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  If you use unity-control-center to set the current user from "Log in
  without a password" to having a password again, the user is not
  removed from the 'nopasswdlogin' UNIX group, and so can log in without
  a password still.

  [ Test case ]

  1. Open the dash, type "User Accounts", open the user accounts panel of 
unity-control-center.
  2. Make sure the current user (which must be an admin) is selected in the 
list of user's on the left hand side.
  3. Click "Unlock" at the top right, and enter the user's password.
  4. Click the dots to the right of "Password", to open the dialog where you 
can change the password mode.
  5. In the combo box at the top, select "Log in without a password". Save the 
dialog.
  6. Open a terminal, and execute `grep nopasswdlogin /etc/group'. Note that 
the current user is present.
  7. Re-open the password dialog as in step 4.
  8. Select "Set a password now", and set a password. Save the dialog.
  9. Open a terminal, and execute `grep nopasswdlogin /etc/group'.

  At step 9, if the bug is present then the user will still be in the
  group. If it is fixed then the user will not.

  [ Fix ]

  unity-control-center's user-accounts panel contains a codepath to call
  `passwd' directly when changing the current user's password. There's
  another path when setting the password for a different user which uses
  AccountsService. In the former codepath, the AccountsService call
  required to remove the user from `nopasswdlogin' is not executed
  (act_user_set_password_mode (..., ACT_USER_PASSWORD_MODE_REGULAR)).

  The proposed fix (in the attached MP) is to always make this call when
  setting a password, even in this passwd case.

  [ QA ]

  Run the test case above. Additionally,

   - Try to use the dialog to change passwords without unlocking it.
   - Try to change both the current and another user's password.

  Make sure the nopasswdlogin membership is right at all times and the
  new password always gets applied (e.g. try logging out and in to check
  the settings).

  [ Regression potential ]

  The fix changes a couple of things

- We now call act_user_set_password_mode () after running passwd.
- We now call act_user_set_password () before act_user_set_password_mode 
(), which is the opposite of the previous order.

  AFAIK both of these changes are fine, but we should run the QA tests
  above to get confidence that they didn't break password setting.

  [ Original description ]

  1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system 
setting.
  2. Click "Password --> Action --> Log in without password -->Change to clear 
Log in password. (as doing so, the user is added to group "nopasswdlogin")
  3. Check that the user is in the nopasswdlogin group
  4. Then do the similar action "Set a password now" as the same way to set Log 
in password.
  5. Check that the user is *not* in the nopasswdlogin group.

  The key problem is: it won't remove user from nopasswdlogin in step 4.
  At step 5, you are left in the group.

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

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

[Desktop-packages] [Bug 1666759] [NEW] package vino 3.8.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-02-21 Thread Jesus Lopez

Public bug reported:

Hello, I just turned my PC on and this message appeared
I'm not sure if this has any relation, but my Ubunutu Software Center stopped 
working some days ago.
I reinstalled it and now its working.

Thanks

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: vino 3.8.1-0ubuntu9
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Feb 21 19:47:32 2017
DuplicateSignature:
 package:vino:3.8.1-0ubuntu9
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package vino (--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 2017-02-16 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: vino
Title: package vino 3.8.1-0ubuntu9 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: vino (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 vino in Ubuntu.
https://bugs.launchpad.net/bugs/1666759

Title:
  package vino 3.8.1-0ubuntu9 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in vino package in Ubuntu:
  New

Bug description:
  Hello, I just turned my PC on and this message appeared
  I'm not sure if this has any relation, but my Ubunutu Software Center stopped 
working some days ago.
  I reinstalled it and now its working.

  Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vino 3.8.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Feb 21 19:47:32 2017
  DuplicateSignature:
   package:vino:3.8.1-0ubuntu9
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package vino (--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 2017-02-16 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: vino
  Title: package vino 3.8.1-0ubuntu9 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/vino/+bug/1666759/+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 1666759] Re: package vino 3.8.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-02-21 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 vino in Ubuntu.
https://bugs.launchpad.net/bugs/1666759

Title:
  package vino 3.8.1-0ubuntu9 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in vino package in Ubuntu:
  New

Bug description:
  Hello, I just turned my PC on and this message appeared
  I'm not sure if this has any relation, but my Ubunutu Software Center stopped 
working some days ago.
  I reinstalled it and now its working.

  Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vino 3.8.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Feb 21 19:47:32 2017
  DuplicateSignature:
   package:vino:3.8.1-0ubuntu9
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package vino (--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 2017-02-16 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: vino
  Title: package vino 3.8.1-0ubuntu9 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/vino/+bug/1666759/+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 1597654] Re: Xorg crashed with SIGABRT during system resume after suspend

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

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

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

Title:
  Xorg crashed with SIGABRT during system resume after suspend

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Information attached.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.3-1ubuntu6
  Uname: Linux 4.7.0-994-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Wed Jun 29 20:10:47 2016
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2016-03-13 (108 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to yakkety on 2016-05-22 (38 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1597654/+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 1650905] Re: libcheese-gtk23 dependency issue

[Expired for unity-control-center (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  libcheese-gtk23 dependency issue

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

Bug description:
  I was trying to compile xserver, for which I needed to install libgl1
  -mesa-dri, but trying to install gives following errors:

  The following packages have unmet dependencies:
   gnome-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not 
going to be installed
  Depends: libcheese7 (>= 3.0.1) but it is not going to 
be installed
   libgl1-mesa-dev : Depends: libgl1-mesa-glx (= 10.1.3-0ubuntu0.6) or
  libgl1-mesa-glx-lts-utopic but it is not going to 
be installed or
  libgl1-mesa-glx-lts-vivid but it is not going to 
be installed or
  libgl1-mesa-glx-lts-wily but it is not going to 
be installed or
  libgl1-mesa-glx-lts-xenial but it is not going to 
be installed
   unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not 
going to be installed
  Depends: libcheese7 (>= 3.0.1) but it is not going to 
be installed
   xorg : Depends: xserver-xorg (>= 1:7.7+1ubuntu8.1) or
   xserver-xorg-renamed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  while checking libcheese-gtk23 package gives:
  Version: 3.10.2-0ubuntu2
  and for libcheese7:
  Version: 3.10.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1650905/+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 1666741] [NEW] Thinkpad X1 + OneLink+ dock - audio not available after docking

Public bug reported:

After docking my X1 Carbon (4th gen) with the OneLink+ dock, neither the
headphone jack on my laptop, nor on the dock work--only the laptop
speakers work. As a workaround I created a script to reset the audio
preferences after I dock (attached: fix-audio). This moves all active
inputs to the dock and sets the dock as a default, but seems to be a bit
heavy-handed.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "fix-audio"
   https://bugs.launchpad.net/bugs/1666741/+attachment/4823867/+files/fix-audio

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

Title:
  Thinkpad X1 + OneLink+ dock - audio not available after docking

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After docking my X1 Carbon (4th gen) with the OneLink+ dock, neither
  the headphone jack on my laptop, nor on the dock work--only the laptop
  speakers work. As a workaround I created a script to reset the audio
  preferences after I dock (attached: fix-audio). This moves all active
  inputs to the dock and sets the dock as a default, but seems to be a
  bit heavy-handed.

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

2017-02-21 Thread Chris Halse Rogers

Hello Aron, or anyone else affected,

Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/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 (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 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:
  Fix Committed
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 1666741] Re: Thinkpad X1 + OneLink+ dock - audio not available after docking

** Attachment added: "Output of pactl list while undocked"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666741/+attachment/4823869/+files/pactl.undocked

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

Title:
  Thinkpad X1 + OneLink+ dock - audio not available after docking

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After docking my X1 Carbon (4th gen) with the OneLink+ dock, neither
  the headphone jack on my laptop, nor on the dock work--only the laptop
  speakers work. As a workaround I created a script to reset the audio
  preferences after I dock (attached: fix-audio). This moves all active
  inputs to the dock and sets the dock as a default, but seems to be a
  bit heavy-handed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666741/+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 1666741] Re: Thinkpad X1 + OneLink+ dock - audio not available after docking

** Attachment added: "Output of pactl list after dock, before fix"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666741/+attachment/4823870/+files/pactl.docked-boot

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

Title:
  Thinkpad X1 + OneLink+ dock - audio not available after docking

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After docking my X1 Carbon (4th gen) with the OneLink+ dock, neither
  the headphone jack on my laptop, nor on the dock work--only the laptop
  speakers work. As a workaround I created a script to reset the audio
  preferences after I dock (attached: fix-audio). This moves all active
  inputs to the dock and sets the dock as a default, but seems to be a
  bit heavy-handed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666741/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2017-02-21 Thread jhansonxi

Possibly related Debian bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750533
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813334

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

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

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1666469] [NEW] [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes

You have been subscribed to a public bug:

unitu 17.04 unity8 deb session
[unity8] child windows don't have a minimum size, you can resize the windows to 
ludicrous sizes 

open a random app, open a child window (help>about or whatever), resize
the window as small as it's allowed. see attached screenshot

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
[unity8] child windows don't have a minimum size, you can resize the windows to 
ludicrous sizes 
https://bugs.launchpad.net/bugs/1666469
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 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 1525477] Re: X server crash when pasting selection using middle button in Chromium

2017-02-21 Thread Andrei Borzenkov

It does not look like live image includes Chromium (at least, I do not
see it in Dash search results), so unfortunately I cannot test it - the
problem so far was observed only when pasting in Chromium.

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

Title:
  X server crash when pasting selection using middle button in Chromium

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  xorg 1:7.7+1ubuntu8.1

  Select any text; use middle button to paste selection in Chromium (I
  observed it pasting in URL bar or in any form text input field,
  including previous attempt to report this bug :) ). Session crashes.

  It does not happen, when either pasting into different application
  (like terminal) or wen use Copy - Paste instead of middle button.

  I noticed it about a week ago, so it must be some recent change; I use
  selection paste often enough to notice something like this before.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Dec 12 11:09:22 2015
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:062b]
  InstallationDate: Installed on 2015-07-02 (162 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Latitude E5450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 
video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 06J17N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Dec 12 11:08:11 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1133 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+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 1566513] Re: Complex numbers are exponentiated incorrectly

This will be fixed in this version for Ubuntu 16.10. I'm going to go
ahead and close the 16.10 bug task now since it wasn't mentioned in the
changelog.

https://launchpad.net/ubuntu/+source/gnome-
calculator/1:3.22.2-1ubuntu0.1

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

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

Title:
  Complex numbers are exponentiated incorrectly

Status in GNOME Calculator:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-calculator source package in Xenial:
  Triaged
Status in gnome-calculator source package in Yakkety:
  Fix Released

Bug description:
  The calculator incorrectly performs exponentiation if the base is
  complex and the exponent is a positive integer. Under these conditions
  the calculator exponentiates the real part of the base and leaves its
  imaginary part intact, that does not agree with the complex numbers
  operation rules. If the exponent is not a positive integer, the
  calculation is performed correctly.

  Steps to reproduce the bug:

  1. Start the program.
  2. Evaluate expression "i^2". The displayed result is "i".
  3. Evaluate expression "(1+i)^2". The displayed result is "1+i".
  4. Evaluate expression "(2+i)^2". The displayed result is "4+i".

  Please find a quick fix patch attached. I did not study its
  comprehensiveness and optimality, but it seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-calculator 1:3.16.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  5 22:59:29 2016
  InstallationDate: Installed on 2014-09-29 (554 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-calculator
  UpgradeStatus: Upgraded to wily on 2015-10-29 (159 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calculator/+bug/1566513/+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 1589215] Re: 'Unknown Application Name' menu item in Indicator Applet Appmenu when LibreOffice is running

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

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

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

Title:
  'Unknown Application Name' menu item in Indicator Applet Appmenu when
  LibreOffice is running

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Sometimes I get the issue of a menu having the name of a different
  application and being unusable, or being an application menu for the
  focused window but being titled 'Unknown Application Name', with
  LibreOffice. I also get this with GNOME apps but was told that this is
  a separate issue to the one I reported here:
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  calculator/+bug/1584720 (see comment #5).

  The issue is with using Indicator Applet Appmenu in the panel on
  gnome-flashback installed on standard Ubuntu (which I call Ubuntu
  (GNOME) Flashback).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libreoffice-writer 1:5.1.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jun  5 10:32:35 2016
  InstallationDate: Installed on 2016-04-26 (39 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1589215/+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 1625595] Re: Libre Office Writer Icons unreadability on YY and ZZ with Intel Drivers

2017-02-21 Thread Marco Parillo

This may be resolved with Kubuntu ZZ Beta 1.

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

Title:
  Libre Office Writer Icons unreadability on YY and ZZ with Intel
  Drivers

Status in xorg package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  glxinfo | grep -i vendor
  server glx vendor string: SGI
  client glx vendor string: Mesa Project and SGI
  Vendor: Intel Open Source Technology Center (0x8086)
  OpenGL vendor string: Intel Open Source Technology Center

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625595/+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 1625595] Re: Libre Office Writer Icons unreadability on YY and ZZ with Intel Drivers

2017-02-21 Thread buzzmandt

I have tested this with my ZZ it now works properly, Fixed i think

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

Title:
  Libre Office Writer Icons unreadability on YY and ZZ with Intel
  Drivers

Status in xorg package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  glxinfo | grep -i vendor
  server glx vendor string: SGI
  client glx vendor string: Mesa Project and SGI
  Vendor: Intel Open Source Technology Center (0x8086)
  OpenGL vendor string: Intel Open Source Technology Center

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

2017-02-21 Thread Alex Tu

** Description changed:

  [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.
+ 
+ needed by:
+ lp #1647283

-- 
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:
  Fix Committed
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.

  needed by:
  lp #1647283

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 1636666] Re: [MIR] pcre2

I added an Other Info section.

** Description changed:

  Availability
  
  Synced with Debian. Built for all supported architectures.
  
  Rationale
  =
  Required by gnome-terminal 3.22+ and vte2.91 0.46+
  
  Security
  
  At least one open security issue, affecting Ubuntu 16.04 LTS
  https://people.canonical.com/~ubuntu-security/cve/pkg/pcre2.html
  https://security-tracker.debian.org/tracker/source-package/pcre2
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pcre
  
  Quality assurance
  =
  - Please subscribe Ubuntu Desktop Bugs or Ubuntu Foundation Bugs (like pcre3) 
to this package.
  https://bugs.launchpad.net/ubuntu/+source/pcre2
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pcre2
  
  Upstream tests are run during the build but there is no autopkgtest
  
  Does not have 3.0 (quilt) set
  
  Dependencies
  
  Only build-dependencies are dpkg and debhelper. No other added dependencies.
  
  Standards compliance
  
  3.9.6
  
  Maintenance
  ===
  - Actively developed upstream
  http://pcre.org/
  
  Background information
  ==
  As the package description states, the older version of this library is 
confusingly named pcre3 in Debian/Ubuntu. pcre3 is already in Ubuntu main.
+ 
+ Other Info
+ ==
+ In the original release of pcre2 in Jan 2015, the author says this is not 
just a drastic update to the original pcre but a "new project". He felt free to 
change names and options.
+ https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html
+ 
+ pcre3 has gotten some bugfix releases since then (from 8.36 to 8.40
+ released Jan 2017)
+ 
+ Some discussion of how it's different:
+ http://www.regular-expressions.info/pcre2.html

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

Title:
  [MIR] pcre2

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in pcre2 package in Ubuntu:
  Incomplete
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Availability
  
  Synced with Debian. Built for all supported architectures.

  Rationale
  =
  Required by gnome-terminal 3.22+ and vte2.91 0.46+

  Security
  
  At least one open security issue, affecting Ubuntu 16.04 LTS
  https://people.canonical.com/~ubuntu-security/cve/pkg/pcre2.html
  https://security-tracker.debian.org/tracker/source-package/pcre2
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pcre

  Quality assurance
  =
  - Please subscribe Ubuntu Desktop Bugs or Ubuntu Foundation Bugs (like pcre3) 
to this package.
  https://bugs.launchpad.net/ubuntu/+source/pcre2
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pcre2

  Upstream tests are run during the build but there is no autopkgtest

  Does not have 3.0 (quilt) set

  Dependencies
  
  Only build-dependencies are dpkg and debhelper. No other added dependencies.

  Standards compliance
  
  3.9.6

  Maintenance
  ===
  - Actively developed upstream
  http://pcre.org/

  Background information
  ==
  As the package description states, the older version of this library is 
confusingly named pcre3 in Debian/Ubuntu. pcre3 is already in Ubuntu main.

  Other Info
  ==
  In the original release of pcre2 in Jan 2015, the author says this is not 
just a drastic update to the original pcre but a "new project". He felt free to 
change names and options.
  https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html

  pcre3 has gotten some bugfix releases since then (from 8.36 to 8.40
  released Jan 2017)

  Some discussion of how it's different:
  http://www.regular-expressions.info/pcre2.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/163/+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 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes

Oops, sorry, this is only a duplicate of bug 1511604 if it's using Xmir.
It looks like the above apps will be native GTK instead.

** Package changed: unity8 (Ubuntu) => gtk+3.0 (Ubuntu)

** Tags added: gtk-mir

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

Title:
  [unity8] child windows don't have a minimum size, you can resize the
  windows to ludicrous sizes

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  unitu 17.04 unity8 deb session
  [unity8] child windows don't have a minimum size, you can resize the windows 
to ludicrous sizes 

  open a random app, open a child window (help>about or whatever),
  resize the window as small as it's allowed. see attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666469/+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 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes

Sorry again, this is also not a GTK bug. The windows you mention
correctly implement resize constraints and I can confirm this on Unity8
17.04.

So I can't reproduce the bug...

Is Xmir running on your system?

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

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

** Tags added: unity8-desktop

** Tags added: resizing

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

Title:
  [unity8] child windows don't have a minimum size, you can resize the
  windows to ludicrous sizes

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  unitu 17.04 unity8 deb session
  [unity8] child windows don't have a minimum size, you can resize the windows 
to ludicrous sizes 

  open a random app, open a child window (help>about or whatever),
  resize the window as small as it's allowed. see attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666469/+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 1666676] Re: Enable tracker by default for Unity too

2017-02-21 Thread Khurshid Alam

What about zeitgeist. Other things integrated with zeitgeist. So we run
tracker indexing service only to recursive search in nautilus?

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

Title:
  Enable tracker by default for Unity too

Status in nautilus package in Ubuntu:
  New

Bug description:
  For Nautilus' built-in search to not be very slow, Nautilus needs to
  use tracker for search.

  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
  the removal of that feature by Nautilus years ago. (LP: #181)

  To not cripple Ubuntu GNOME, it was decided to let Nautilus build
  against tracker but not use that functionality on Unity. See this
  patch:

  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+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 1666771] [NEW] Nvidia 378.13 (Patched) + Kernel 4.10(RC8)

2017-02-21 Thread dexter74

Public bug reported:

(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/cyrillic".
[   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/100dpi/".
[   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/75dpi/".
[   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/100dpi".
[   243.735] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/75dpi".
[   243.735] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 
'vmmouse' will be disabled.
[   243.735] (WW) Disabling Keyboard0
[   243.735] (WW) Disabling Mouse0
[   243.834] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[   243.834] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[   243.995] (WW) Falling back to old probe method for fbdev
[   243.996] (WW) Falling back to old probe method for vesa
[   243.997] (WW) Warning, couldn't open module glamoregl
[   244.578] (WW) evdev: E-Signal/A-One USB Gaming Mouse: ignoring absolute 
axes.


01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1c03] 
(rev a1) (prog-if 00 [VGA controller])
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at fd00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [128] Power Budgeting 
Capabilities: [420] Advanced Error Reporting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 

Capabilities: [900] #19
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia


name of display: :0
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".

Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
marc@Drthrax-Fixe:~$ glxgears 
Xlib:  extension "GLX" missing on display ":0".
Error: couldn't get an RGB, Double-buffered visual

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.10.0-041000rc8-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Feb 22 07:02:00 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: nvidia, 378.13, 4.10.0-041000rc8-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard: NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA 
controller])
InstallationDate: Installed on 2017-02-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000rc8-generic 
root=UUID=af0ea833-acc7-4f5d-89b5-646908b7ed3a ro quiet splash vt.handoff=7
SourcePackage: xorg
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1708
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99X EVO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:

[Desktop-packages] [Bug 1648992] Re: [SRU] Update gnome-calculator to 3.22.2

2017-02-21 Thread FanJun Kong - ( BH1SCW )

I did some test too, I think it is no problem,
click on expression, it will replace and click on result it will append. It is 
designed as this.

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

Title:
  [SRU] Update gnome-calculator to 3.22.2

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

Bug description:
  Impact
  ==
  This update includes the new upstream bugfix 3.22.1 and 3.22.2 releases.

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

  Overview of changes in gnome-calculator 3.22.2:

  Fix reusing results from the history stack #766155
  Ctrl+Backspace should deletes only last number, not everything (bgo#725114)
  Fixed possible errors on currency conversion (bgo#750672)
  Fixed first expression with parentheses (bgo#700617)
  Fixed conversion unit switch, fixes #748732.

  Test Case
  =
  *Fix reusing results from the history stack #766155
   - A click on the equation would replace the current expression
   - A click on the result would append it to the current expression
  * Ctrl+Backspace should deletes only last number, not everything (bgo#725114)
   - input some expression, press Ctrl+Backspace it will delete last number 
instead of clear everything.
  * Fixed possible errors on currency conversion (bgo#750672)
   - gnome-calculator --solve '1500 EUR in USD' you will get just result, no 
more spamming stderr
  * Fixed first expression with parentheses (bgo#700617)
   - 3(7) you will get result: 21
  * Fixed conversion unit switch, fixes #748732
   - Be in Financial mode, choose "Botswana Pula" on the left side and 
"Algerian Dinar" on the right side
  2. Type 1
  3. Click Switch conversation units
  the displayed number will change correctly as long as the currencies switched

  Regression Potential
  
  The uploads are happening under the GNOME Micro Release Exception.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1648992/+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 1656399] Re: Returning to existing session is unreliable and can leave on blank screen

@ Robert - grabbed from -proposed.

Locking from desktop appears to work as expected.

Unlocking from suspend - I get hiccups if I'm a bit quick entering
password (bug 1666803)

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

Title:
  Returning to existing session is unreliable and can leave on blank
  screen

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Xenial:
  Triaged
Status in lightdm source package in Yakkety:
  Triaged

Bug description:
  [Impact]
  Due to a logic bug LightDM returning to an existing session from a greeter 
can be unreliable. This case is common in systems which use the greeter as a 
lock screen.

  The bug was introduced in revision 1954 to fix bug 1296276. The race
  condition seems to have been made more likely to the change in
  revision 2437 to fix bug 1637758.

  [Test Case]
  1. Log into a session
  2. Switch to the greeter (e.g. dm-tool switch-to-greeter)
  3. Log in again

  Expected result
  Returned to existing session

  Observed result
  Not always returned, can end up on blank screen. Since this is a race 
condition this may not occur on some systems.

  [Regression Potential]
  Low, the fix is to correct a logic bug that made LightDM think it hadn't 
stopped a session correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1656399/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-21 Thread monte

Seems it works for my Lenovo x230t. Thanks for your effort!

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

2017-02-21 Thread Alberto Milone

Reopening, as the problem can still be reproduced.

** Description changed:

  SRU Request:
  
  [Impact]
  
  Upgrading from the upstream fglrx driver packages to the packages in the
  Ubuntu repository fails because the /etc/ati directory is a real
  directory instead of being a link (which was common in the Ubuntu
  packages).
  
  [Test Case]
  1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages 
from the AMD installer 
  2. Upgrade the package to the current ubuntu release.
  3. Check the apt-get output 
  
  Expected results: the fglrx module should be updated correctly.
  
  Actual results:
  The update fails as described below.
  
  [Regression Potential]
  Low. The change only affects a migration from a specific release.
  
  
  __
  Note that the fglrx 14.502 package name is 
fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from 
Ubuntu repository.
  
  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  
  (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
  
  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for install-info (5.2.0.dfsg.1-2) ...
  Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ...
  
  (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
  
  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for doc-base (0.10.5) ...
  Processing 1 changed doc-base file...
  Errors were encountered while processing:
   /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb
  Log ended: 2015-10-22 05:31:11
+ 
+ X-HWE-Bug: Bug #1664810

** Changed in: fglrx-installer (Ubuntu Trusty)
   Status: Fix Released => In Progress

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

Title:
  Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Trusty:
  In Progress
Status in fglrx-installer-updates source package in Trusty:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  Upgrading from the upstream fglrx driver packages to the packages in
  the Ubuntu repository fails because the /etc/ati directory is a real
  directory instead of being a link (which was common in the Ubuntu
  packages).

  [Test Case]
  1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages 
from the AMD installer 
  2. Upgrade the package to the current ubuntu release.
  3. Check the apt-get output 

  Expected results: the fglrx module should be updated correctly.

  Actual results:
  The update fails as described below.

  [Regression Potential]
  Low. The change only affects a migration from a specific release.

  
  __
  Note that the fglrx 14.502 package name is 
fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from 
Ubuntu repository.

  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for install-info (5.2.0.dfsg.1-2) ...
  Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ...

  (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot

[Desktop-packages] [Bug 1666635] Re: gvfsd-smb-browse crashed with SIGABRT in _talloc_free()

2017-02-21 Thread Apport retracing service

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

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 #1546463, 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/135/+attachment/4823570/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-smb-browse crashed with SIGABRT in _talloc_free()

Status in gvfs package in Ubuntu:
  New

Bug description:
  gvfsd-smb-browse crashed with SIGABRT in _talloc_free()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gvfs-backends 1.30.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Feb 21 20:11:02 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2017-02-16 (5 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.6 
/org/gtk/gvfs/exec_spaw/13
  ProcEnviron:
   LANG=de_AT.UTF-8
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   _talloc_free () from /usr/lib/x86_64-linux-gnu/libtalloc.so.2
   smbc_free_context () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0
   ?? ()
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gvfsd-smb-browse crashed with SIGABRT in _talloc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/135/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"

2017-02-21 Thread Russ Phillips

** Attachment added: "Screenshot at 2017-02-21 19:52:24.png"
   
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1657092/+attachment/4823780/+files/Screenshot%20at%202017-02-21%2019%3A52%3A24.png

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

Title:
  deja-dup refers to "Files" instead of "Caja"

Status in Déjà Dup:
  In Progress
Status in deja-dup package in Ubuntu:
  In Progress

Bug description:
  The Backups application's Overview screen says "You can restore the
  entire backup with the Restore... button or use Files"

  It should say "or use Caja", since the file manager in Mate has been
  renamed Caja.

  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1654546] Re: brltty.service: Failed at step SECCOMP spawning /bin/sh: Invalid argument

2017-02-21 Thread sam tygier

Still an issue with the 4.4.38-v7+ kernel that recently arrived in
Ubuntu MATE 16.04

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

Title:
  brltty.service: Failed at step SECCOMP spawning /bin/sh: Invalid
  argument

Status in Ubuntu Pi Flavour Maker:
  New
Status in brltty package in Ubuntu:
  New

Bug description:
  I get this logged in the journal every 30 seconds. Running Ubuntu Mate
  16.04 on a raspberr pi2.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: brltty 5.3.1-2ubuntu2.1
  Uname: Linux 4.1.19-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Fri Jan  6 12:13:12 2017
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pi-flavour-maker/+bug/1654546/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"

2017-02-21 Thread Russ Phillips

I originally posted this bug in Mate, since I thought they maintained a
forked version of Nautilus and Deja Dup, and this would be something
they'd want to include in that.

I'll attach a screenshot to confirm that the file manager is listed as
"Caja" in the application menu.

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

Title:
  deja-dup refers to "Files" instead of "Caja"

Status in Déjà Dup:
  In Progress
Status in deja-dup package in Ubuntu:
  In Progress

Bug description:
  The Backups application's Overview screen says "You can restore the
  entire backup with the Restore... button or use Files"

  It should say "or use Caja", since the file manager in Mate has been
  renamed Caja.

  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1576228] Re: Black borders around all windows

2017-02-21 Thread John Smith

** Description changed:

  While using the nvidia proprietary drivers in 14.04 - 16.04, my Dell XPS
  L501X resumes from suspend, but displays wide black borders around all
  windows with close/minimize/maximize buttons blacked out as per attached
  screenshot. It occurs inconsistently, as it doesn't happen every time
  the computer resumes.
  
  Also there seems to be certain amount of performance degradation as if
  the graphics driver was running at half-strength. The "nVidia X Server
  Settings" app suggests its in maximum performance mode.
  
- Adhoc Workaround: switch display layout (I have an external monitor/TV
+ Adhoc WORKAROUND: switch display layout (I have an external monitor/TV
  attached to HDMI port) changing anything such as arrangement or
  resolution of the displays, etc. corrects the black border issue.
+ 
+ See comment :https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
+ drivers-361/+bug/1576228/comments/4
  
  WORKAROUND: Use nouveau.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
  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 Apr 28 18:43:37 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e]
  InstallationDate: Installed on 2016-04-23 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS L501X
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic 
root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J1VR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn0J1VR3:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS L501X
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 28 17:09:49 2016
  xserver.configfile: default
  xserver.errors:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
  
  xserver.version: 2:1.18.3-1ubuntu2

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

Title:
  Black borders around all windows

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

Bug description:
  While using the nvidia

[Desktop-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.

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

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.21
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.18
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.20
   Importance: Undecided
   Status: New

** No longer affects: lightdm/1.21

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: light-locker (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: light-locker (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

** Also affects: light-locker (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Returning to existing session is unreliable and can leave on blank
  screen

Status in Light Display Manager:
  New
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.18 series:
  New
Status in Light Display Manager 1.20 series:
  New
Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress
Status in light-locker source package in Trusty:
  New
Status in lightdm source package in Trusty:
  New
Status in light-locker source package in Xenial:
  New
Status in lightdm source package in Xenial:
  New
Status in light-locker source package in Yakkety:
  New
Status in lightdm source package in Yakkety:
  New

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1656399/+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 1656399] Re: Returning to existing session is unreliable and can leave on blank screen

** Description changed:

- Unable to unlock Xubuntu XFCE session after suspend. I'm presented with
- unlock screen, and entering credentials will redirect to a black screen
- with "This session is locked", and "you will be redirected to unlock
- screen".
+ [Impact]
+ Due to a logic bug LightDM returning to an existing session from a greeter 
can be unreliable. This case is common in systems which use the greeter as a 
lock screen.
+ 
+ The bug was introduced in revision 1954 to fix bug 1296276. The race
+ condition seems to have been made more likely to the change in revision
+ 2437 to fix bug 1637758.
+ 
+ [Test Case]
+ 1. Log into a session
+ 2. Switch to the greeter (e.g. dm-tool switch-to-greeter)
+ 3. Log in again
+ 
+ Expected result
+ Returned to existing session
+ 
+ Observed result
+ Not always returned, can end up on blank screen.
+ 
+ [Regression Potential]
+ Low, the fix is to correct a logic bug that made LightDM think it hadn't 
stopped a session correctly.

** Changed in: lightdm/1.20
   Status: New => Fix Committed

** Changed in: lightdm/1.18
   Importance: Undecided => High

** Changed in: lightdm/1.18
   Status: New => Fix Committed

** Changed in: lightdm/1.10
   Importance: Undecided => High

** Changed in: lightdm/1.10
   Status: New => Fix Committed

** Description changed:

  [Impact]
  Due to a logic bug LightDM returning to an existing session from a greeter 
can be unreliable. This case is common in systems which use the greeter as a 
lock screen.
  
  The bug was introduced in revision 1954 to fix bug 1296276. The race
  condition seems to have been made more likely to the change in revision
  2437 to fix bug 1637758.
  
  [Test Case]
  1. Log into a session
  2. Switch to the greeter (e.g. dm-tool switch-to-greeter)
  3. Log in again
  
  Expected result
  Returned to existing session
  
  Observed result
- Not always returned, can end up on blank screen.
+ Not always returned, can end up on blank screen. Since this is a race 
condition this may not occur on some systems.
  
  [Regression Potential]
  Low, the fix is to correct a logic bug that made LightDM think it hadn't 
stopped a session correctly.

** Changed in: lightdm/1.20
   Importance: Undecided => High

** Changed in: lightdm/1.10
Milestone: None => 1.10.7

** Changed in: lightdm/1.18
Milestone: None => 1.18.4

** Changed in: lightdm/1.20
Milestone: None => 1.20.1

** Changed in: lightdm
   Importance: Undecided => High

** Changed in: lightdm
   Status: New => Fix Committed

** Changed in: lightdm
Milestone: None => 1.21.5

** No longer affects: light-locker (Ubuntu)

** No longer affects: light-locker (Ubuntu Trusty)

** No longer affects: light-locker (Ubuntu Yakkety)

** No longer affects: light-locker (Ubuntu Xenial)

** Changed in: lightdm
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm/1.10
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm/1.18
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm/1.20
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

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

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

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

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

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

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

Title:
  Returning to existing session is unreliable and can leave on blank
  screen

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Xenial:
  Triaged
Status in lightdm source package in Yakkety:
  Triaged

Bug description:
  [Impact]
  Due to a logic bug LightDM returning to an existing session from a greeter 
can be unreliable. This case is common in systems which use the greeter as a 
lock screen.

  The bug was introduced in revision 1954 to fix bug 1296276. The race
  condition seems to have been made more likely to the change in
  revision 2437 to fix bug 1637758.

  [Test Case]
  1. Log into a session
  2. Switch to the greeter (e.g. dm-tool switch-to-greeter)
  3. Log in again

  Expected result
  Returned to existing session

  Observed result
  Not always returned, can end up on blank screen. Since this is a race 
condition this may not occur on some systems.

  [Regression Potential]
  Low, the

[Desktop-packages] [Bug 1666724] [NEW] /usr/lib/NetworkManager/nm-dhcp-helper:5:g_thread_new:_g_dbus_shared_thread_ref:_g_dbus_worker_new:initable_init:g_initable_new_valist

2017-02-21 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: wily xenial yakkety

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

Title:
  /usr/lib/NetworkManager/nm-dhcp-
  
helper:5:g_thread_new:_g_dbus_shared_thread_ref:_g_dbus_worker_new:initable_init:g_initable_new_valist

Status in network-manager package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1666724/+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 1656399] Re: Returning to existing session is unreliable and can leave on blank screen

The change fixes the issue for me, though of course it may not be the
only issue affecting screen locking with light-locker (as per the
original bug description). If you continue to have problems please
comment here an open a new bug and we'll tackle further issues there.
Thanks for all the great feedback in this bug!

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

Title:
  Returning to existing session is unreliable and can leave on blank
  screen

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Xenial:
  Triaged
Status in lightdm source package in Yakkety:
  Triaged

Bug description:
  [Impact]
  Due to a logic bug LightDM returning to an existing session from a greeter 
can be unreliable. This case is common in systems which use the greeter as a 
lock screen.

  The bug was introduced in revision 1954 to fix bug 1296276. The race
  condition seems to have been made more likely to the change in
  revision 2437 to fix bug 1637758.

  [Test Case]
  1. Log into a session
  2. Switch to the greeter (e.g. dm-tool switch-to-greeter)
  3. Log in again

  Expected result
  Returned to existing session

  Observed result
  Not always returned, can end up on blank screen. Since this is a race 
condition this may not occur on some systems.

  [Regression Potential]
  Low, the fix is to correct a logic bug that made LightDM think it hadn't 
stopped a session correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1656399/+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 1656399] Re: Returning to existing session is unreliable and can leave on blank screen

Uploaded to zesty as 1.21.5-0ubuntu1.

** Changed in: lightdm
   Status: Fix Committed => Fix Released

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

Title:
  Returning to existing session is unreliable and can leave on blank
  screen

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.18 series:
  Fix Committed
Status in Light Display Manager 1.20 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  In Progress
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Xenial:
  Triaged
Status in lightdm source package in Yakkety:
  Triaged

Bug description:
  [Impact]
  Due to a logic bug LightDM returning to an existing session from a greeter 
can be unreliable. This case is common in systems which use the greeter as a 
lock screen.

  The bug was introduced in revision 1954 to fix bug 1296276. The race
  condition seems to have been made more likely to the change in
  revision 2437 to fix bug 1637758.

  [Test Case]
  1. Log into a session
  2. Switch to the greeter (e.g. dm-tool switch-to-greeter)
  3. Log in again

  Expected result
  Returned to existing session

  Observed result
  Not always returned, can end up on blank screen. Since this is a race 
condition this may not occur on some systems.

  [Regression Potential]
  Low, the fix is to correct a logic bug that made LightDM think it hadn't 
stopped a session correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1656399/+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 1557581] Re: Xorg crashed with SIGABRT in OsAbort()

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

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

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

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I couldn't log on the desktop and had to delete .XAuthority.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Mar 15 10:39:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1457682482
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: NVIDIA Corporation G96 [GeForce 9400 GT] [10de:0641] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2015-01-12 (427 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcCwd: /
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=ebb2347f-b7d8-4b1b-a1b8-dda5904995ae ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0211
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0211:bd05/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMEPU:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Mar 15 14:59:49 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1557581/+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 1625283] Re: Xorg crashed with SIGABRT in OsAbort()

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

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

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

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  crashes repeatedly

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  BootLog: tito-root: clean, 1313859/15114240 files, 51881669/60448000 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep 19 18:43:20 2016
  DistUpgraded: 2016-09-19 18:24:27,589 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.4.0-38-generic, x86_64: installed
   acpi-call, 1.1.0, 4.4.0-9136-generic, x86_64: installed
   virtualbox, 5.1.6, 4.4.0-38-generic, x86_64: installed
   virtualbox, 5.1.6, 4.4.0-9136-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2014-08-08 (773 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS13 9333
  ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=8a50e235-2691-4a4a-b587-3bb79f18c59c ro splash quiet vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to yakkety on 2016-09-19 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 08/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  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-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.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-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1625283/+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 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

Unfortunately, upstream for gnome-terminal and vte doesn't care to
provide NEWS files.

I said that gnome-terminal and vte hadn't changed much in the 3.24 cycle but 
there were changes in the 3.22 (0.46) cycle
- Add systemd user service
- Add Detach Terminal action to tab context menu (this is important because the 
ability to drag a tab out of a window was dropped in a 3.20 bug fix update but 
because of string freeze, this wasn't added until 3.22)
- Add "gnome-terminal --preferences" to allow changing preferences if you 
somehow managed to break something in settings so that you can't launch 
gnome-terminal normally
- a crash fix in the gnome-shell search provider 
https://git.gnome.org/browse/gnome-terminal/commit/?id=777e66d
- Various appstream metadata updates

3.24, vte 0.48
- async spawning https://git.gnome.org/browse/gnome-terminal/commit/?id=d4e25a57
- There's this GNOME initiative to use "fancy quotes", even for command line 
output so some strings were changed for that.

Here's the new vte symbols for 0.46 and 0.48
https://developer.gnome.org/vte/unstable/api-index-0-46.html
https://developer.gnome.org/vte/unstable/api-index-0-48.html

 vte_pty_spawn_async@Base 0.47.90
 vte_pty_spawn_finish@Base 0.47.90
 vte_regex_error_get_type@Base 0.45.90
 vte_regex_error_quark@Base 0.45.90
 vte_regex_get_type@Base 0.45.90
 vte_regex_jit@Base 0.45.90
 vte_regex_new_for_match@Base 0.45.90
 vte_regex_new_for_search@Base 0.45.90
 vte_regex_ref@Base 0.45.90
 vte_regex_unref@Base 0.45.90
 vte_terminal_event_check_regex_simple@Base 0.45.90
 vte_terminal_match_add_regex@Base 0.45.90
 vte_terminal_search_get_regex@Base 0.45.90
 vte_terminal_search_set_regex@Base 0.45.90

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+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 1666741] Re: Thinkpad X1 + OneLink+ dock - audio not available after docking

** Attachment added: "Output of pactl list after dock, after fix-audio script"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666741/+attachment/4823871/+files/pactl.docked-fixed

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

Title:
  Thinkpad X1 + OneLink+ dock - audio not available after docking

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After docking my X1 Carbon (4th gen) with the OneLink+ dock, neither
  the headphone jack on my laptop, nor on the dock work--only the laptop
  speakers work. As a workaround I created a script to reset the audio
  preferences after I dock (attached: fix-audio). This moves all active
  inputs to the dock and sets the dock as a default, but seems to be a
  bit heavy-handed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1666741/+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 1659834] Re: HDMI port not working

2017-02-21 Thread marijn

I had the same issue. Completely shutting down the machine (not just
rebooting) fixed it.

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

Title:
  HDMI port not working

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Kernel version: 4.4.0-59-generic
  Laptop is MacBookPro11,4
  Graphics card: VGA compatible controller [0300]: Intel Corporation Crystal 
Well Integrated Graphics Controller [8086:0d26] (rev 08)

  Connecting an external monitor using HDMI works fine when booting up
  on macOS but not in ubuntu 16.04, kernel 4.4.0-59-generic, using same
  cable and monitor. It was working fine as recently as yesterday, not
  sure what happened... Tried booting up in previous kernel version
  (4.4.0-53-generic) but also didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-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: Fri Jan 27 14:02:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.6.3-4.4.0, 1, 4.4.0-21-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-57-generic, x86_64: installed
   i915-4.6.3-4.4.0, 1, 4.4.0-59-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Crystal Well Integrated Graphics Controller 
[106b:0147]
  InstallationDate: Installed on 2016-04-26 (276 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro11,4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=bba094b5-a045-4054-b44b-3024e2585537 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B09.1602151732
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B09.1602151732:bd02/15/2016:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple 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.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  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 Jan 27 12:29:24 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41006
   vendor APP
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659834/+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 1666435] [NEW] GTK apps have wrong font/thickness/hinting under Unity8

Public bug reported:

GTK apps have wrong font/thickness/hinting under Unity8 (compared to
Unity7 where they look much better).

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: unity8-desktop-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gtk-mir unity8-desktop visual-quality

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

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity8-desktop-session (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GTK apps have wrong font/thickness/hinting under Unity8

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  New

Bug description:
  GTK apps have wrong font/thickness/hinting under Unity8 (compared to
  Unity7 where they look much better).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666435/+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 1666435] Re: GTK apps have wrong font/thickness/hinting under Unity8

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

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

Title:
  GTK apps have wrong font/thickness/hinting under Unity8

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  New

Bug description:
  GTK apps have wrong font/thickness/hinting under Unity8 (compared to
  Unity7 where they look much better).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666435/+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 1666441] [NEW] Topbar interferes with VMware workstation in fullscreen mode

2017-02-21 Thread Vaclav Cermak

Public bug reported:

When I run VMware workstation (player in my case) in fullscreen mode,
top bar is hidden, but it still takes mouse events and I cannot click to
undelying VMware window. This happens randomly.

Seems like it is the same like in this expired bug:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314780.

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: Tue Feb 21 09:12:08 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GM200 [GeForce GTX TITAN X] [10de:17c2] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: NVIDIA Corporation GM200 [GeForce GTX TITAN X] [10de:1132]
InstallationDate: Installed on 2016-06-14 (251 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=615648ea-b585-4a04-9853-0a98eaa41577 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/22/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BAP6710H.86A.0079.2012.0622.1722
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DP67DE
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10217-204
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBAP6710H.86A.0079.2012.0622.1722:bd06/22/2012:svn:pn:pvr:rvnIntelCorporation:rnDP67DE:rvrAAG10217-204:cvn:ct3:cvr:
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.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: Mon Feb 20 09:32:11 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Performance MX MOUSE, id 8
 inputLogitech M510MOUSE, id 9
 inputLogitech K340KEYBOARD, id 10
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  Topbar interferes with VMware workstation in fullscreen mode

Status in xorg package in Ubuntu:
  New

Bug description:
  When I run VMware workstation (player in my case) in fullscreen mode,
  top bar is hidden, but it still takes mouse events and I cannot click
  to undelying VMware window. This happens randomly.

  Seems like it is the same like in this expired bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314780.

  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:

[Desktop-packages] [Bug 1639896] Re: Backport support for AMD Polaris

2017-02-21 Thread ethan.hsieh

I have verified xserver-xorg-video-amdgpu (1.1.2) and mesa (12.0.6)

Test result:
1. glxgears: Pass
2. glmark2: Pass
3. S3 Test: Pass
(sudo fwts s3 --s3-multiple=30 --s3-min-delay=30 --s3-max-delay=30)

Test Environment
1. Kernel: 4.4.0-49-generic
2. VGA compatible controller [AMD/ATI] Device [1002:67df], Kernel driver in 
use: amdgpu
3. Installed packages:
amdgpu-pro-dkms (16.60-377537)
xserver-xorg-video-amdgpu (1.1.2-0ubuntu0.16.04.1)
libegl1-mesa-drivers:amd64 (12.0.6-0ubuntu0.16.04.1)
libgbm1:amd64 (12.0.6-0ubuntu0.16.04.1)
libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1)
libglapi-mesa:amd64 (12.0.6-0ubuntu0.16.04.1)
libgles1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1)
libgles2-mesa:amd64 (12.0.6-0ubuntu0.16.04.1)
libosmesa6:amd64 (12.0.6-0ubuntu0.16.04.1)
libxatracker2:amd64 (12.0.6-0ubuntu0.16.04.1)
libegl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1)
libgl1-mesa-glx:amd64 (12.0.6-0ubuntu0.16.04.1)
libwayland-egl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1)

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

Title:
  Backport support for AMD Polaris

Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs.

  Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6
  backported instead

  [Test case]
  Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration

  [Regression potential]
  This is a stable upstream release, and 16.10 ships the same versions so 
regression potential should be minimal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1314780] Re: Full screen between xorg and VMWare-Workstation

2017-02-21 Thread Vaclav Cermak

OK, done.

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

Title:
Full screen between xorg and VMWare-Workstation

Status in xorg package in Ubuntu:
Expired

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

Attached are screenshots as the process happens.

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

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

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

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

[Desktop-packages] [Bug 1666696] [NEW] [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card

2017-02-21 Thread Jason Black

Public bug reported:

No sound when play video, music or clips in the internet. In audio
setting it's shown as dummy device

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-5.7+IntelAtom-linuxium 4.10.0-rc6
Uname: Linux 4.10.0-5-linuxium x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jason  2541 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Wed Feb 22 00:52:54 2017
InstallationDate: Installed on 2017-02-19 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" Linuxium - Alpha  (20170127)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: bytcr-rt5651 - bytcr-rt5651
Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2016
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: IRBIS.WI310D.NWNNRBN01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name
dmi.board.vendor: Type2 - Board Manufacturer
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrIRBIS.WI310D.NWNNRBN01:bd11/04/2016:svnIRBIS:pnNB20:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: NB20
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: IRBIS

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


** Tags: amd64 apport-bug zesty

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

Title:
  [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect
  card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound when play video, music or clips in the internet. In audio
  setting it's shown as dummy device

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-5.7+IntelAtom-linuxium 4.10.0-rc6
  Uname: Linux 4.10.0-5-linuxium x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  2541 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 00:52:54 2017
  InstallationDate: Installed on 2017-02-19 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" Linuxium - Alpha  (20170127)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: bytcr-rt5651 - bytcr-rt5651
  Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: IRBIS.WI310D.NWNNRBN01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name
  dmi.board.vendor: Type2 - Board Manufacturer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrIRBIS.WI310D.NWNNRBN01:bd11/04/2016:svnIRBIS:pnNB20:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NB20
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: IRBIS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/196/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"

2017-02-21 Thread Michael Terry

Reproducing what I wrote in the mailing list:

==
In reality, we only really support what we can easily handle. 
Officially, we've always targeted both GNOME and whatever Ubuntu's UI
happens to be (used to be simply GNOME, but has diverged a bit).

I'd prefer to keep tight integration and avoid supporting every
environment under the sun (per our mission statement [1]).  But where
it's easy to support another desktop environment, I don't mind.

If it's a simple "if getenv(AM_IN_MATE) == 1, then Caja else Files", I
think that's trivial enough to merge.  But I'd prefer to avoid a
slippery slope of more and more integration points.

Seem reasonable?
==

I'm also interested in confirming whether the menus call Caja "Files" or
"Caja" though.  That might render this all moot.

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

Title:
  deja-dup refers to "Files" instead of "Caja"

Status in Déjà Dup:
  In Progress
Status in deja-dup package in Ubuntu:
  In Progress

Bug description:
  The Backups application's Overview screen says "You can restore the
  entire backup with the Restore... button or use Files"

  It should say "or use Caja", since the file manager in Mate has been
  renamed Caja.

  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

2017-02-21 Thread Stéphane Graber

I'm not seeing a compelling reason to switch to 3.24 and the newer vte
other than the version bump.

If your argument is that after this revert, both gnome-terminal and vte
are effectively identical feature-wise as what we have in the archive
right now, then you're not introducing or removing features, in which
case you don't need a Feature Freeze Exception in the first place.

If this change does introduce/remove features to gnome-terminal and vte,
please list them in a readable format (not an upstream git log/diff).


I think the pcre2 MIR could do with an API diff between pcre3 and pcre2. Your 
massive patch suggests that the two APIs are very much different and that it's 
not something we can do as a typical transition, making the need for both of 
them to live in main together much clearer.

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  gnome-terminal and vte are still at their 3.20 (and 0.44) versions
  because they now hard-depend on pcre2, but the pcre2 MIR (LP:
  #163) has stalled because there is already one version of pcre in
  main and it would be a major task to convert all of main to use pcre2.

  So I reverted 3 commits for gnome-terminal and 5 for vte to make that
  MIR less urgent. I am concerned about the long-term maintainability of
  this approach - the vte patch is over 1600 lines.

  gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3
  Staging PPA for yakkety and zesty for months. I am not aware of any
  issues from that. This is slightly different since I haven't tested
  those versions without pcre2 until this weekend.

  The development cycle for gnome-terminal and vte has been fairly quiet
  so I believe it's safe to go ahead and update gnome-terminal to
  3.23.90 and vte to 0.47.90.

  https://git.gnome.org/browse/gnome-terminal/log
  https://git.gnome.org/browse/vte/log

  The packages are currently available for testing at

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+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 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

2017-02-21 Thread Alberto Milone

** Changed in: fglrx-installer-updates (Ubuntu Trusty)
   Status: Fix Released => In Progress

** Changed in: fglrx-installer-updates (Ubuntu Trusty)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Trusty:
  In Progress
Status in fglrx-installer-updates source package in Trusty:
  In Progress

Bug description:
  SRU Request:

  [Impact]

  Upgrading from the upstream fglrx driver packages to the packages in
  the Ubuntu repository fails because the /etc/ati directory is a real
  directory instead of being a link (which was common in the Ubuntu
  packages).

  [Test Case]
  1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages 
from the AMD installer 
  2. Upgrade the package to the current ubuntu release.
  3. Check the apt-get output 

  Expected results: the fglrx module should be updated correctly.

  Actual results:
  The update fails as described below.

  [Regression Potential]
  Low. The change only affects a migration from a specific release.

  
  __
  Note that the fglrx 14.502 package name is 
fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from 
Ubuntu repository.

  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for install-info (5.2.0.dfsg.1-2) ...
  Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ...

  (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for doc-base (0.10.5) ...
  Processing 1 changed doc-base file...
  Errors were encountered while processing:
   /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb
  Log ended: 2015-10-22 05:31:11

  X-HWE-Bug: Bug #1664810

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+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 1666334] Re: deb package python3-zope.interface somehow breaks pip

2017-02-21 Thread Hans Joachim Desserud

** Tags removed: crash pip python3 undefined
** Tags added: yakkety

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

Title:
  deb package python3-zope.interface somehow breaks pip

Status in zope.interface package in Ubuntu:
  New

Bug description:
  When it's installed pip crashes with the following error

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in 
vendored
  __import__(vendored_name, globals(), locals(), level=0)
  ImportError: No module named 'pip._vendor.pkg_resources'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3.5/runpy.py", line 183, in _run_module_as_main
  mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "/usr/lib/python3.5/runpy.py", line 142, in _get_module_details
  return _get_module_details(pkg_main_name, error)
File "/usr/lib/python3.5/runpy.py", line 109, in _get_module_details
  __import__(pkg_name)
File "/usr/lib/python3/dist-packages/pip/__init__.py", line 21, in 
  from pip._vendor.requests.packages.urllib3.exceptions import 
DependencyWarning
File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 75, in 

  vendored("pkg_resources")
File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 36, in 
vendored
  __import__(modulename, globals(), locals(), level=0)
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 664, in _load_unlocked
File "", line 634, in _load_backward_compatible
File 
"/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/__init__.py",
 line 2976, in 
File 
"/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/__init__.py",
 line 2962, in _call_aside
File 
"/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/__init__.py",
 line 3004, in _initialize_master_working_set
File 
"/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/__init__.py",
 line 2535, in activate
File 
"/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/__init__.py",
 line 2109, in declare_namespace
File 
"/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/__init__.py",
 line 2058, in _handle_ns
File 
"/usr/share/python-wheels/pkg_resources-0.0.0-py2.py3-none-any.whl/pkg_resources/__init__.py",
 line 2078, in _rebuild_mod_path
  AttributeError: '_NamespacePath' object has no attribute 'sort'

  The distro is yakkety.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zope.interface/+bug/1666334/+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 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.

** Attachment added: "x-0_x-1.log"
   
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4823520/+files/x-0_x-1.log

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

Title:
  Unable to unlock session after suspend using lightdm-gtk-greeter.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+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 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.

In my used and abused installation I see similar behaviour.

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

Title:
  Unable to unlock session after suspend using lightdm-gtk-greeter.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+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 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.

** Attachment added: "seat0-greeter.log"
   
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4823519/+files/seat0-greeter.log

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

Title:
  Unable to unlock session after suspend using lightdm-gtk-greeter.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+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 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.

@robert - I've seen reports from xubuntu testers where it was sometimes
working. So I tried more on a completely brand new installation.

Lock - unlock fails - this continued for 3 attempts at which point I reached 
desktop.
Lock and unlock cycle next time took 2 attempts.
Lock and unlock cycle next time took 1 attempt.

I was then able to lock and unlock at will.

Attached all /var/log/lightdm logs from that session.

** Attachment added: "lightdm.log"
   
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+attachment/4823518/+files/lightdm.log

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

Title:
  Unable to unlock session after suspend using lightdm-gtk-greeter.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-02-21 Thread Rik Shaw

The fix from the fourdollars ppa is also working for me: Lenovo x230.

I ran the stress test before applying the fix and confirmed that wifi
was non-functioning after the 30 suspend / wake cycles and needed the
"sudo wpa_cli scan" to activate it again.

I then added the ppa and applied the update to network-manager and then
rebooted. Then I ran the stress test again and after the 30 suspend /
wake cycles wifi was still functioning correctly! This is using Ubuntu
16.04.

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

Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fix it.

Status in OEM Priority Project:
Triaged
Status in OEM Priority Project xenial series:
Triaged
Status in network-manager package in Ubuntu:
Confirmed

Bug description:
HOW TO REPRODUCE:
1. Install fwts by `sudo apt-get install fwts`.
2. Run the suspend & resume stress test.
sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5
--s3-delay-delta=5

RESULT:
The WiFi can not connect to any access point and we have to execute `sudo
wpa_cli scan` manually to make it work again.

WORKAROUND:

(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

SYSTEM INFO:
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
Packages:
libnm-glib-vpn1:amd64 1.2.2-0ubuntu2
libnm-glib4:amd64 1.2.2-0ubuntu2
libnm-util2:amd64 1.2.2-0ubuntu2
libnm0:amd641.2.2-0ubuntu2
network-manager 1.2.2-0ubuntu2

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

[Desktop-packages] [Bug 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.

2017-02-21 Thread Henk Terhell

Same experience on my updated Lubuntu 17.04.

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

Title:
  Unable to unlock session after suspend using lightdm-gtk-greeter.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+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 1661371] Re: [zesty] doesn't offer a window to install missing gstreamer codecs

2017-02-21 Thread Pojar Gheorghe–Ioan

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

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

Title:
  [zesty] doesn't offer a window to install missing gstreamer codecs

Status in PackageKit:
  Won't Fix
Status in Session Installer:
  New
Status in gnome-software package in Ubuntu:
  New
Status in packagekit package in Ubuntu:
  Invalid
Status in sessioninstaller package in Ubuntu:
  New

Bug description:
  Attempting to play a mp3 file with Rhythmbox on the latest Zesty daily
  build

  Rhythmbox opens but no playback start.
  On the terminal I got this:

  Rhythmbox-Message: Missing plugin: gstreamer|1.0|rhythmbox-metadata|MPEG-1 
Layer 3 (MP3) decoder|decoder-audio/mpeg, mpegversion=(int)1, 
mpegaudioversion=(int)1, layer=(int)3
  /usr/lib/python3/dist-packages/sessioninstaller/core.py:47: PyGIWarning: Gst 
was imported without specifying a version first. Use gi.require_version('Gst', 
'1.0') before import to ensure that the right version gets loaded.
    from gi.repository import Gst
  /usr/lib/python3/dist-packages/sessioninstaller/core.py:48: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
    from gi.repository import Gtk
  Falling back to package information
  Rhythmbox-Message: Missing plugins installed. Updating plugin registry ...

  But the wizard to install the missing codec actually fails to launch.

  Please see https://bugzilla.gnome.org/show_bug.cgi?id=770620

To manage notifications about this bug go to:
https://bugs.launchpad.net/packagekit/+bug/1661371/+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 1666677] [NEW] [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all

2017-02-21 Thread Cecil Harper

Public bug reported:

I have checked all the basic things like making sure mute is off and
what not.  So far no sound whatsoever.  Any help is much appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   charper2065 F...m pulseaudio
 /dev/snd/controlC1:  charper2065 F pulseaudio
 /dev/snd/controlC0:  charper2065 F pulseaudio
CurrentDesktop: Unity
Date: Tue Feb 21 12:41:57 2017
InstallationDate: Installed on 2017-02-21 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   charper2065 F...m pulseaudio
 /dev/snd/controlC1:  charper2065 F pulseaudio
 /dev/snd/controlC0:  charper2065 F pulseaudio
Symptom_Jack: Speaker, ATAPI
Symptom_Type: No sound at all
Title: [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/28/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.40
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: VG10AD
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.40:bd01/28/2014:svnTOSHIBA:pnSatelliteS55D-A:pvrPSKKSU-00K006:rvnAMD:rnVG10AD:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite S55D-A
dmi.product.version: PSKKSU-00K006
dmi.sys.vendor: TOSHIBA

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have checked all the basic things like making sure mute is off and
  what not.  So far no sound whatsoever.  Any help is much appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   charper2065 F...m pulseaudio
   /dev/snd/controlC1:  charper2065 F pulseaudio
   /dev/snd/controlC0:  charper2065 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 21 12:41:57 2017
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   charper2065 F...m pulseaudio
   /dev/snd/controlC1:  charper2065 F pulseaudio
   /dev/snd/controlC0:  charper2065 F pulseaudio
  Symptom_Jack: Speaker, ATAPI
  Symptom_Type: No sound at all
  Title: [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: VG10AD
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.40:bd01/28/2014:svnTOSHIBA:pnSatelliteS55D-A:pvrPSKKSU-00K006:rvnAMD:rnVG10AD:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S55D-A
  dmi.product.version: PSKKSU-00K006
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/177/+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 1666681] [NEW] Drop interactive_search.patch (type-ahead search)

Public bug reported:

Nautilus dropped the popular type-ahead search feature years ago. Ubuntu
has been carrying a patch to revert that change. See bug 1164016 for the
original LP bug and patch proposal.

Nautilus is now under very active development. During the 3.22 cycle,
that patch needed to be rebased. I tried to do it and what I came up
with caused a crash (it didn't really crash for me, but ricotz and some
others experienced it) and the first letter typed activated type-ahead
search but the first letter was dropped. In other words, you would need
to type "ddow" to activate the Downloads folder instead of just "dow"
like in previous releases.

I did that rebase in October 2016 and no one has stepped up then to
improve the patch.

The Nautilus maintainer csoriano has said that the slots and views
changed significantly during 3.22 and will likely be refactored more in
the future.

If there's no one available to maintain the patch, unfortunately, we'll
eventually have to drop the patch to not be stuck on an ancient version
of Nautilus.

I am proposing that we do this at the start of the 17.10 development
cycle. This gives 6 months for a developer to step up and try to fix the
patch and 12 months before 18.04 LTS.


Other Items
===
- For better performance with the built-in search, we need to reconsider 
avoiding tracker in Unity (LP: #176)

- There is an option in Preferences for users to disable searching in
subfolders. I don't think we want to do that by default but maybe it can
help some people.

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

** Description changed:

  Nautilus dropped the popular type-ahead search feature years ago. Ubuntu
  has been carrying a patch to revert that change. See bug 1164016 for the
  original LP bug and patch proposal.
  
  Nautilus is now under very active development. During the 3.22 cycle,
  that patch needed to be rebased. I tried to do it and what I came up
  with caused a crash (it didn't really crash for me, but ricotz and some
  others experienced it) and the first letter typed activated type-ahead
  search but the first letter was dropped. In other words, you would need
  to type "ddow" to activate the Downloads folder instead of just "dow"
  like in previous releases.
  
  I did that rebase in October 2016 and no one has stepped up then to
  improve the patch.
  
  The Nautilus maintainer csoriano has said that the slots and views
  changed significantly during 3.22 and will likely be refactored more in
  the future.
  
  If there's no one available to maintain the patch, unfortunately, we'll
  eventually have to drop the patch to not be stuck on an ancient version
  of Nautilus.
  
  I am proposing that we do this at the start of the 17.10 development
  cycle. This gives 6 months for a developer to step up and try to fix the
  patch and 12 months before 18.04 LTS.
+ 
+ 
+ Other Items
+ ===
+ - For better performance with the built-in search, we need to reconsider 
avoiding tracker in Unity (LP: #176)
+ 
+ - There is an option in Preferences for users to disable searching in
+ subfolders. I don't think we want to do that by default but maybe it can
+ help some people.

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

Title:
  Drop interactive_search.patch (type-ahead search)

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus dropped the popular type-ahead search feature years ago.
  Ubuntu has been carrying a patch to revert that change. See bug
  1164016 for the original LP bug and patch proposal.

  Nautilus is now under very active development. During the 3.22 cycle,
  that patch needed to be rebased. I tried to do it and what I came up
  with caused a crash (it didn't really crash for me, but ricotz and
  some others experienced it) and the first letter typed activated type-
  ahead search but the first letter was dropped. In other words, you
  would need to type "ddow" to activate the Downloads folder instead of
  just "dow" like in previous releases.

  I did that rebase in October 2016 and no one has stepped up then to
  improve the patch.

  The Nautilus maintainer csoriano has said that the slots and views
  changed significantly during 3.22 and will likely be refactored more
  in the future.

  If there's no one available to maintain the patch, unfortunately,
  we'll eventually have to drop the patch to not be stuck on an ancient
  version of Nautilus.

  I am proposing that we do this at the start of the 17.10 development
  cycle. This gives 6 months for a developer to step up and try to fix
  the patch and 12 months before 18.04 LTS.

  
  Other Items
  ===
  - For better performance with the built-in search, we need to reconsider 
avoiding tracker in Unity (LP: #176)

  - There is an option in Preferences for users to disable searching in

[Desktop-packages] [Bug 1666676] Re: Enable tracker by default for Unity too

** Description changed:

  For Nautilus' built-in search to not be very slow, Nautilus needs to use
  tracker for search.
  
  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
- the removal of that feature by Nautilus years ago.
+ the removal of that feature by Nautilus years ago. (LP: #181)
  
  To not cripple Ubuntu GNOME, it was decided to let Nautilus build
  against tracker but not use that functionality on Unity. See this patch:
  
  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch

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

Title:
  Enable tracker by default for Unity too

Status in nautilus package in Ubuntu:
  New

Bug description:
  For Nautilus' built-in search to not be very slow, Nautilus needs to
  use tracker for search.

  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
  the removal of that feature by Nautilus years ago. (LP: #181)

  To not cripple Ubuntu GNOME, it was decided to let Nautilus build
  against tracker but not use that functionality on Unity. See this
  patch:

  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+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 1664164] Re: [Zesty] Package won't build

2017-02-21 Thread Till Kamppeter

Committed fix to the Debian GIT repository of the HPLIP package.

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

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

Title:
  [Zesty] Package won't build

Status in hplip package in Ubuntu:
  In Progress

Bug description:
  Trying to build the Zesty package hplip-3.16.11+repack0 under Xenial
  gives me the following error:

  dh_makeshlibs -plibsane-hpaio --no-scripts
  dh_makeshlibs: unknown option; aborting
  debian/rules:260: recipe for target 'override_dh_makeshlibs' failed

  I think the problem is that "--no-scripts" should be "--noscripts" -
  certainly that seems to fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1664164/+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 1666675] [NEW] package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: Paket bamfdaemon ist nicht bereit zur Konfiguration kann nicht konfiguriert wer

2017-02-21 Thread Sibylle

Public bug reported:

It is coming up by registration and logon to a new portal of my renter -
I think so...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Feb 21 21:00:24 2017
ErrorMessage: Paket bamfdaemon ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
InstallationDate: Installed on 2017-01-28 (24 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: bamf
Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to 
install/upgrade: Paket bamfdaemon ist nicht bereit zur Konfiguration  kann 
nicht konfiguriert werden (momentaner Status »half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to
  install/upgrade: Paket bamfdaemon ist nicht bereit zur Konfiguration
  kann nicht konfiguriert werden (momentaner Status »half-installed«)

Status in bamf package in Ubuntu:
  New

Bug description:
  It is coming up by registration and logon to a new portal of my renter
  - I think so...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Feb 21 21:00:24 2017
  ErrorMessage: Paket bamfdaemon ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-01-28 (24 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to 
install/upgrade: Paket bamfdaemon ist nicht bereit zur Konfiguration  kann 
nicht konfiguriert werden (momentaner Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/175/+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 1666676] [NEW] Enable tracker by default for Unity too

Public bug reported:

For Nautilus' built-in search to not be very slow, Nautilus needs to use
tracker for search.

This is especially important since it's being seriously proposed for
Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
the removal of that feature by Nautilus years ago. (LP: #181)

To not cripple Ubuntu GNOME, it was decided to let Nautilus build
against tracker but not use that functionality on Unity. See this patch:

https://bazaar.launchpad.net/~ubuntu-
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch

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

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

Title:
  Enable tracker by default for Unity too

Status in nautilus package in Ubuntu:
  New

Bug description:
  For Nautilus' built-in search to not be very slow, Nautilus needs to
  use tracker for search.

  This is especially important since it's being seriously proposed for
  Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted
  the removal of that feature by Nautilus years ago. (LP: #181)

  To not cripple Ubuntu GNOME, it was decided to let Nautilus build
  against tracker but not use that functionality on Unity. See this
  patch:

  https://bazaar.launchpad.net/~ubuntu-
  
desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+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 1666681] Re: Drop interactive_search.patch (type-ahead search)