date:20170124

[Desktop-packages] [Bug 1659191] [NEW] package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also

2017-01-24 Thread Saurabh Kumar Singh

Public bug reported:

No idea

ProblemType: Package
DistroRelease: Kali 2016.2
Package: gconf-service 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Jan 25 11:58:29 2017
DpkgTerminalLog:
 Preparing to unpack .../gconf-service_3.2.6-4_amd64.deb ...
 Unpacking gconf-service (3.2.6-4) over (3.2.6-3ubuntu6) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/gconf-service_3.2.6-4_amd64.deb (--unpack):
  trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
RelatedPackageVersions:
 dpkg 1.18.15kali1
 apt  1.4~beta3
SourcePackage: gconf
Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', 
which is also in package gconf-service-backend 3.2.6-3ubuntu6
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying
  to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-
  evoldap.so', which is also in package gconf-service-backend
  3.2.6-3ubuntu6

Status in gconf package in Ubuntu:
  New

Bug description:
  No idea

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gconf-service 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jan 25 11:58:29 2017
  DpkgTerminalLog:
   Preparing to unpack .../gconf-service_3.2.6-4_amd64.deb ...
   Unpacking gconf-service (3.2.6-4) over (3.2.6-3ubuntu6) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/gconf-service_3.2.6-4_amd64.deb (--unpack):
trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.4~beta3
  SourcePackage: gconf
  Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', 
which is also in package gconf-service-backend 3.2.6-3ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

2017-01-24 Thread Martin

Is there a way to write a script that can switch to HSP/HFP, attempt to
switch to a2dp, disconnect bluetooth and reconnect the bluetooth and
then connect to a2dp? That would be a decent work around so we could
save ourselves time when we do this every day.

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

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

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

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

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

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

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

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

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 393811] Re: [needs-packaging] Request to package: hunspell-en-ca

2017-01-24 Thread Bug Watch Updater

** Changed in: openoffice.org-dictionaries (Debian)
   Status: Unknown => Fix Released

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

Title:
  [needs-packaging] Request to package: hunspell-en-ca

Status in openoffice.org-dictionaries package in Ubuntu:
  Fix Released
Status in openoffice.org-dictionaries package in Debian:
  Fix Released

Bug description:
  This package exists in Debian sid.

  It is traditional to say that Canadians use either British or American
  spelling conventions.

  This is really not correct. A specific Canadian blend has developed
  and has been adopted by, among others, the Government of Canada.

  As a student of translation in Canada, it would be useful to have this
  package.

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

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

[Desktop-packages] [Bug 121205] Re: no spellcheck in default install

2017-01-24 Thread Mathew Hodson

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

** This bug is no longer a duplicate of bug 44100
   [needs-packaging] Package myspell-en-ca for OOo spellcheck
** This bug has been marked a duplicate of bug 393811
   [needs-packaging] Request to package: hunspell-en-ca

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

Title:
  no spellcheck in default install

Status in openoffice.org package in Ubuntu:
  New

Bug description:
  Binary package hint: openoffice.org2

  Ubuntu 7.04 - the Feisty Fawn  Openoffice 2.2.0
  Spellcheckng doesn't work under the default install,
  English Canadian for language  .
  Spellchecking works in firefox.
  Thesaurus is non function to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/121205/+subscriptions

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

[Desktop-packages] [Bug 158629] Re: gutsy openoffice.org 2.3 spell checker does not work

2017-01-24 Thread Mathew Hodson

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

** This bug is no longer a duplicate of bug 44100
   [needs-packaging] Package myspell-en-ca for OOo spellcheck
** This bug has been marked a duplicate of bug 393811
   [needs-packaging] Request to package: hunspell-en-ca

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

Title:
  gutsy openoffice.org 2.3 spell checker does not work

Status in openoffice.org package in Ubuntu:
  New

Bug description:
  It just pops up a dialog saying "Spellcheck is complete" with an ok
  button, even when there are obviously misspelled words in the
  document, and disappears.  Am I doing something wrong?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/158629/+subscriptions

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

[Desktop-packages] [Bug 393811] Re: [needs-packaging] Request to package: hunspell-en-ca

2017-01-24 Thread Mathew Hodson

openoffice.org-dictionaries (1:3.1.0~ooo310m5-1) experimental;
urgency=low

  * new upstream snapshot
- includes en_CA dictionary - new package: hunspell-en-ca
  (closes: #478113, #419095)
- other new packages: {hunspell,openoffice.org-hyphenation}-{sr,sh}

 -- Rene Engelhard   Thu, 12 Mar 2009 18:01:13 +0100

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

** Also affects: openoffice.org-dictionaries (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419095
   Importance: Unknown
   Status: Unknown

** No longer affects: openoffice.org-dictionaries (Debian)

** Also affects: openoffice.org-dictionaries (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419095
   Importance: Unknown
   Status: Unknown

** Package changed: ubuntu => openoffice.org-dictionaries (Ubuntu)

** Changed in: openoffice.org-dictionaries (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [needs-packaging] Request to package: hunspell-en-ca

Status in openoffice.org-dictionaries package in Ubuntu:
  Fix Released
Status in openoffice.org-dictionaries package in Debian:
  Unknown

Bug description:
  This package exists in Debian sid.

  It is traditional to say that Canadians use either British or American
  spelling conventions.

  This is really not correct. A specific Canadian blend has developed
  and has been adopted by, among others, the Government of Canada.

  As a student of translation in Canada, it would be useful to have this
  package.

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

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

[Desktop-packages] [Bug 393811] [NEW] [needs-packaging] Request to package: hunspell-en-ca

2017-01-24 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

This package exists in Debian sid.

It is traditional to say that Canadians use either British or American
spelling conventions.

This is really not correct. A specific Canadian blend has developed and
has been adopted by, among others, the Government of Canada.

As a student of translation in Canada, it would be useful to have this
package.

** Affects: openoffice.org-dictionaries (Ubuntu)
 Importance: Wishlist
 Status: Fix Released

** Affects: openoffice.org-dictionaries (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: needs-packaging
-- 
[needs-packaging] Request to package: hunspell-en-ca
https://bugs.launchpad.net/bugs/393811
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to openoffice.org-dictionaries 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 1659183] Re: English (Canada) input source is missing the left backslash key

2017-01-24 Thread Mathew Hodson

Attached a picture showing the backslash key next to the left shift.

** Attachment added: "Left backslash.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1659183/+attachment/4808799/+files/Left%20backslash.jpg

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

Title:
  English (Canada) input source is missing the left backslash key

Status in ibus package in Ubuntu:
  New

Bug description:
  In Canada, many keyboards are bilingual and have a slightly different
  layout from US keyboards. They have an additional backslash key next
  to the left shift key.

  In Text Entry, when I select English (Canada) as the input source, the
  layout is wrong. Instead of a backslash, the layout shows a less-than
  symbol, and that is what input when I press the key.

  Attached a screenshot of the incorrect layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 24 22:49:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-22 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170115)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1659183] [NEW] English (Canada) input source is missing the left backslash key

2017-01-24 Thread Mathew Hodson

Public bug reported:

In Canada, many keyboards are bilingual and have a slightly different
layout from US keyboards. They have an additional backslash key next to
the left shift key.

In Text Entry, when I select English (Canada) as the input source, the
layout is wrong. Instead of a backslash, the layout shows a less-than
symbol, and that is what input when I press the key.

Attached a screenshot of the incorrect layout.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ibus 1.5.14-2ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
Uname: Linux 4.9.0-12-generic x86_64
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 24 22:49:41 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-01-22 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170115)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

** Attachment added: "Incorrect layout.png"
   
https://bugs.launchpad.net/bugs/1659183/+attachment/4808795/+files/Incorrect%20layout.png

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

Title:
  English (Canada) input source is missing the left backslash key

Status in ibus package in Ubuntu:
  New

Bug description:
  In Canada, many keyboards are bilingual and have a slightly different
  layout from US keyboards. They have an additional backslash key next
  to the left shift key.

  In Text Entry, when I select English (Canada) as the input source, the
  layout is wrong. Instead of a backslash, the layout shows a less-than
  symbol, and that is what input when I press the key.

  Attached a screenshot of the incorrect layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 24 22:49:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-22 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170115)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1659130] Re: Battery indicator doesn't change the status when I plug the charger

2017-01-24 Thread Paul White

** Package changed: evince (Ubuntu) => upower (Ubuntu)

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

Title:
  Battery indicator doesn't change the status when I plug the charger

Status in upower package in Ubuntu:
  New

Bug description:
  When I plug the charger, the battery indicator doesn't change to
  "charging" until the battery increase at least one level.

  --
  You can try plugin and unplugging your charger.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.22.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 24 23:23:00 2017
  InstallationDate: Installed on 2017-01-08 (16 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

2017-01-24 Thread Steve Langasek

Hello Timo, or anyone else affected,

Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.70-1~ubuntu16.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: libdrm (Ubuntu Xenial)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  Since the xserver is already at 1.18.4, the full stack from 16.10 will
  not be backported as a renamed set of packages. Instead, only the
  drivers with bugfix releases will be backported, plus the libraries
  and mesa that complement the set.

  [Test case]

  Run a desktop session, see that things still work

  [Regression potential]

  libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

  mesa:
  included here just to keep the necessary backport bits in the same bug, the 
actual update testing will be handled on bug #1641017. That said:
  - Intel validates new upstream releases on all their hw
  - AMD probably does the same, though it's unverified
  - this release was already tested by cert team on a handful of intel/amd 
machines

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

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

[Desktop-packages] [Bug 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%

2017-01-24 Thread AceLan Kao

** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Won't Fix

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

Title:
  Backlight sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Won't Fix
Status in xorg source package in Vivid:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in xorg source package in Xenial:
  Invalid

Bug description:
  Back-light sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

  Issue is interment in occurrence. Will be reproducible with the
  command "sudo pm-suspend" & or close/reopen laptop lid for a period of
  time days or hours, then go a period of time, days or hours without
  being able to trigger it again.

  This is irrespective of running "apt-get update && apt-get upgrade -y"
  and has continued to be intermittent on last 3 versions of 3.19
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-74-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec  1 10:06:43 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06e5]
  InstallationDate: Installed on 2016-11-22 (8 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed 
root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.14
  dmi.board.name: 0W7V82
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec  1 09:14:43 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1.1

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

-- 
Mailing list: https://launchpad.net/~desktop-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)

2017-01-24 Thread Daniel van Vugt

Fortunately that's already the case. An app in Unity8 is always asking
Unity8 to ask USC to turn the screen off. Unity8 already has the option
of rejecting it, in theory.

-- 
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:
  In Progress
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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-01-24 Thread Tony Espy

@taiebot65

Thanks. I'll take a look.

Regarding this bug, it turns out that when I was testing my version of
NM with the dropped 'ScanDone' patch (wifi-Signal-on-the-wifi-
device...), I'd been doing so on top of the newly re-based 1.2.6, and it
turns out there was an actual fix in 1.2.6 which seems to fix the bug:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2=b749f7d31b7e5f57f18026a14b6a444e59a488cf

This new version of NM hasn't yet been SRU'd for xenial, as version
1.2.4-0ubuntu0.16.04.1 is still in -proposed. I'll see if maybe we can
expedite this landing and skip 1.2.4 altogether.

Note, I've managed to run 200 cycles of S3 on my Thinkpad without
hitting the bug. This included about 25 cycles of manual
suspend/resume, and 175 iterations using fwts.

--
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:
New
Status in OEM Priority Project xenial series:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed

Bug description:
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

Reproduce steps:
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

Expected result:
The WiFi still functioned.

Actual 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.

P.S. Ubuntu 16.04 also has the same issue.

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.

2017-01-24 Thread Tony Espy

** Changed in: oem-priority/xenial
   Status: New => Confirmed

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

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

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

Bug description:
  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

  Reproduce steps:
  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

  Expected result:
  The WiFi still functioned.

  Actual 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.

  P.S. Ubuntu 16.04 also has the same issue.

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 1659140] [NEW] x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)

2017-01-24 Thread My name

Public bug reported:

Observed behavior:

When I get an alternate tty, or whatever it's called, with cntrl-alt-FN,
where N is any digit, 2-6, inclusive; log in as the same user on the
console; do stuff; and then log out with "exit":

I'm suddenly back in tty1 and X has crashed. There is no x on any
console. I can start it again with startx.

Expected behavior:

As it does in 14.04, I should just get a login prompt and stay in the
same console. X running in tty1 should be unaffected, like x in tty7
would be unaffected in Trusty.


This is 64 bit Xenial with a minimalist Openbox environment, built from the 
mini.iso. I start X with "startx".

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

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

Title:
  x crashes when I log in and back out of a tty (console, cntrl-alt-F2
  thing, whatever)

Status in xorg package in Ubuntu:
  New

Bug description:
  Observed behavior:

  When I get an alternate tty, or whatever it's called, with cntrl-alt-
  FN, where N is any digit, 2-6, inclusive; log in as the same user on
  the console; do stuff; and then log out with "exit":

  I'm suddenly back in tty1 and X has crashed. There is no x on any
  console. I can start it again with startx.

  Expected behavior:

  As it does in 14.04, I should just get a login prompt and stay in the
  same console. X running in tty1 should be unaffected, like x in tty7
  would be unaffected in Trusty.

  
  This is 64 bit Xenial with a minimalist Openbox environment, built from the 
mini.iso. I start X with "startx".

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

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

[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2017-01-24 Thread dualshock3nerd

I found a more viable workaround based on comment #18 by Anthony that
still lets you use your headphone jack provided you have an unused front
microphone jack.

Install alsa-tools-gui
Run hdajackretask
Override "Green Headphone, Front side" to "Not connected"
Override "Pink Mic, Front side" to "Headphone"
Click "Apply now"
Click "Install boot override" to make this permanent

>From now on, just plug your headphones in the front microphone jack instead of
>the front headphone jack and you're golden. Speakers still get automatically
>muted when you plug in your headphones.
This is much more viable to me as I just use a USB microphone anyway.
I tested this for a few days and this bug never reappeared.

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

Title:
Volume notification keeps popping up constantly(the notifyosd bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 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:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

[Desktop-packages] [Bug 1659130] [NEW] Battery indicator doesn't change the status when I plug the charger

2017-01-24 Thread José Carlos

Public bug reported:

When I plug the charger, the battery indicator doesn't change to
"charging" until the battery increase at least one level.

--
You can try plugin and unplugging your charger.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: evince 3.22.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 24 23:23:00 2017
InstallationDate: Installed on 2017-01-08 (16 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apparmor apport-bug zesty

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

Title:
  Battery indicator doesn't change the status when I plug the charger

Status in evince package in Ubuntu:
  New

Bug description:
  When I plug the charger, the battery indicator doesn't change to
  "charging" until the battery increase at least one level.

  --
  You can try plugin and unplugging your charger.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.22.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 24 23:23:00 2017
  InstallationDate: Installed on 2017-01-08 (16 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff

2017-01-24 Thread Launchpad Bug Tracker

This bug was fixed in the package gtk+3.0 - 3.22.7-1ubuntu2

---
gtk+3.0 (3.22.7-1ubuntu2) zesty; urgency=medium

  * Restore gtksocket-unscale-before-sending-configurenotify.patch:
- Accidentally dropped in 3.22.6-1ubuntu1 (LP: #1572331)

 -- Jeremy Bicha   Mon, 23 Jan 2017 09:44:28 -0500

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  GtkPlug scaled to half the expected size on HiDPI screens + zesty
  debdiff

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
  package shipping currently in the development version of Ubuntu zesty.
  You will find the corresponding debdiff attached to this bug thread.

  Marmuta performed tests with org.gnome.desktop.interface scaling-
  factor = 2 , where few issues are left for Onboard on hidpi screens,
  that are not related to gtk, but rather to unity-greeter or gnome-
  screensaver. He did not notice any issue with scaling-factor = 1.

  Can a sponsor please review the debdiff?

  Thanks in advance.

  Francesco

  =
  Original description:

  See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
  Source code below.

  What I expect to happen is that the GtkPlug has the same size as the 
GtkSocket.
  What actually happens is that GtkPlug only covers a quarter of the area of 
the GtkSocket.

  Impact: Onboard on HiDPI displays is near unusable at login and lock
  screen, aka unity-greeter and gnome-screensaver. Original bug report
  here: https://bugs.launchpad.net/bugs/1562734.

  Steps to reproduce:
  - build plug and socket samples from below
  - set display scaling factor to 2
    System Settings -> Display -> Scale for menu and title bars = 2
  - run  ./socket $(head -1 <(./plug))
  -> blue GtkPlug is too small, it should cover all the black

  - resize the window
  -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's 
wrong again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 01:48:50 2016
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1646574] Re: Mouse cursor invisible or does not move

2017-01-24 Thread Brad Figg

** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux
(Ubuntu)

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

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

Title:
  Mouse cursor invisible or does not move

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  New

Bug description:
  When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed 
in left upper corner or sometimes disappear. I actually can click or hover 
everywhere on the screen, I just don't know where the mouse is pointer at the 
moment.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04]
  InstallationDate: Installed on 2016-11-26 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID ffc0:0040  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_67RSRP
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags:  yakkety ubuntu
  Uname: Linux 4.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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

[Desktop-packages] [Bug 1646574] Re: Mouse cursor invisible or does not move

2017-01-24 Thread David Jordan

This bug affects a number of different systems with Nvidia 10 Series
(Pascal) GPUs.  When using Nouveau, the cursor is drawn in the top left
corner of the screen and appears to be stuck there despite the user
being able to move around and click anywhere.

While it's possible to work around this bug by installing the
proprietary Nvidia driver, this bug is a huge hassle when installing
from the standard iso.  (Also when the proprietary driver breaks or is
removed for some reason)

The Nouveau developers report that this is fixed in Kernel 4.10 and pointed to 
this commit as solving the issue:
https://github.com/skeggsb/nouveau/commit/b94985176af536ab752a63baecdee263ffcce63f
With the two preceding commits being needed as well:
https://github.com/skeggsb/nouveau/commit/0d874f550816a6d7038658c3ec78c992e40c132f
https://github.com/skeggsb/nouveau/commit/88a1b714678ad1f5bda441052383e70a9d52f100

Still need to test these commits, but they look promising.

With 16.04.2 bringing in the 4.8 kernel, which is affected by this bug,
it would be nice to have these cherry picked to make sure the ISO works
with modern NVIDIA GPUs.

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

Title:
  Mouse cursor invisible or does not move

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed 
in left upper corner or sometimes disappear. I actually can click or hover 
everywhere on the screen, I just don't know where the mouse is pointer at the 
moment.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04]
  InstallationDate: Installed on 2016-11-26 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID ffc0:0040  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_67RSRP
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags:  yakkety ubuntu
  Uname: Linux 4.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1646574/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-01-24 Thread Andre Mack

For me the same error: the internal microphone is not recognized. I have
an Acer Aspire VN7-572G-56VP with ALS255.

An external headset works when I write in the file: 
'/etc/modprobe.d/alsa-base.conf' the following entries: 
'options snd-hda-intel model = dell-headset-multi'

-- 
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 1659117] Re: package libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1 failed to install/upgrade: package libharfbuzz-icu0:amd64 is not ready for configuration cannot configure (current

2017-01-24 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 harfbuzz in Ubuntu.
https://bugs.launchpad.net/bugs/1659117

Title:
  package libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1 failed to
  install/upgrade: package libharfbuzz-icu0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  this issue also occured while installing ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jan 25 07:56:36 2017
  DuplicateSignature:
   package:libharfbuzz-icu0:amd64:1.0.1-1ubuntu0.1
   Processing triggers for libc-bin (2.23-0ubuntu5) ...
   dpkg: error processing package libharfbuzz-icu0:amd64 (--configure):
package libharfbuzz-icu0:amd64 is not ready for configuration
  ErrorMessage: package libharfbuzz-icu0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-01-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: harfbuzz
  Title: package libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1 failed to 
install/upgrade: package libharfbuzz-icu0:amd64 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/harfbuzz/+bug/1659117/+subscriptions

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

[Desktop-packages] [Bug 1659117] [NEW] package libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1 failed to install/upgrade: package libharfbuzz-icu0:amd64 is not ready for configuration cannot configure (curren

2017-01-24 Thread hemant kumar

Public bug reported:

this issue also occured while installing ubuntu

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Jan 25 07:56:36 2017
DuplicateSignature:
 package:libharfbuzz-icu0:amd64:1.0.1-1ubuntu0.1
 Processing triggers for libc-bin (2.23-0ubuntu5) ...
 dpkg: error processing package libharfbuzz-icu0:amd64 (--configure):
  package libharfbuzz-icu0:amd64 is not ready for configuration
ErrorMessage: package libharfbuzz-icu0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2017-01-24 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: harfbuzz
Title: package libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1 failed to 
install/upgrade: package libharfbuzz-icu0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1 failed to
  install/upgrade: package libharfbuzz-icu0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  this issue also occured while installing ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jan 25 07:56:36 2017
  DuplicateSignature:
   package:libharfbuzz-icu0:amd64:1.0.1-1ubuntu0.1
   Processing triggers for libc-bin (2.23-0ubuntu5) ...
   dpkg: error processing package libharfbuzz-icu0:amd64 (--configure):
package libharfbuzz-icu0:amd64 is not ready for configuration
  ErrorMessage: package libharfbuzz-icu0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-01-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: harfbuzz
  Title: package libharfbuzz-icu0:amd64 1.0.1-1ubuntu0.1 failed to 
install/upgrade: package libharfbuzz-icu0:amd64 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/harfbuzz/+bug/1659117/+subscriptions

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

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

2017-01-24 Thread Genma

I have this problem with my Jabra halo smart, a2dp.py is a good
workaround at the moment. But this need to be fixed.

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

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

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

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

  Ubuntu Xenial 16.04 LTS

  The log below:

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


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

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

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

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

76 matches

Mail list logo