date:20170523

I have moved the debdiff into bug 1582213, which seems to be a more
sure-fire-definitely-fixed bug when compared to this more vague ongoing
issue.

** Patch removed: "xenial-a2dp-fixes-may2017.debdiff"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1438510/+attachment/4882273/+files/xenial-a2dp-fixes-may2017.debdiff

** Description changed:

[Impact]
Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode).
A2DP is the high quality profile used for Bluetooth speakers and music in
general.

[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Go to Sound settings and check the device's current "Mode".
3. If the current Mode is not yet A2DP then try to set it to A2DP
Expected: The mode is either A2DP by default or can be set to it.

[Regression Potential]
Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main
area affected. A combination of related A2DP bugs in pulseaudio in xenial means
it is difficult to get working at all without this patch. So highly unlikely
Bluetooth audio support could get worse. Since pulseaudio itself is being
modified there is always a regression potential in support for other audio
devices, but several audio devices have been tested and all continue to work
well with the patch.

[Other notes]
- Related to bug 1283003 and bug 1582213. Possibly others too.
+ Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff
which fixes this is attached to bug 1582213.

The patch was authored by Luke Yelavich with help from Konrad
Zapałowicz. And it has received further testing over the past two months
by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
only changes the changelog wording from Luke's original PPA.

[Original 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.

--
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 audio no longer supports A2DP (stuck in HSP/HFP
mode)

Status in PulseAudio:
Confirmed
Status in bluez package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
In Progress
Status in bluez source package in Vivid:
Won't Fix
Status in pulseaudio source package in Vivid:
Won't Fix

Bug description:
[Impact]
Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode).
A2DP is the high quality profile used for Bluetooth speakers and music in
general.

[Other notes]
Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff
which fixes this is attached to bug 1582213.

The patch was authored by Luke Yelavich with help from Konrad
Zapałowicz. And it has received further testing over the past two
months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
here only changes the changelog wording from Luke's original PPA.

[Desktop-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

** Description changed:

  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
- Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1438510.
+ Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two months
  by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
  only changes the changelog wording from Luke's original PPA.
  
  [Original Description]
  Hi,
  
  I found a bug in Ubuntu 14.04 !
  
  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the audio
  preferences.
  
  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.
  
  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

Attached debdiff for updating xenial to pulseaudio 1:8.0-0ubuntu3.3, in
order to address a few problems with Bluetooth audio (A2DP).

** Patch added: "xenial-a2dp-fixes-may2017.debdiff"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1582213/+attachment/4882311/+files/xenial-a2dp-fixes-may2017.debdiff

** Description changed:

[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Verify in Sound settings you have it set to A2DP mode.
3. Turn off and then on the Bluetooth device.
4. Verify the device has reconnected and if not, force it to in the Bluetooth
indicator menu.
5. Open Sound settings again, select the device and verify it's reappeared in
A2DP mode.
6. Click 'Test Sound'.
Expected: Sound can be heard from the Bluetooth device.

[Other notes]
- Related to bug 1283003 and bug 1438510. Possibly others too. The debdiff
which fixes this is attached to bug 1438510.
+ Related to bug 1283003 and bug 1438510. Possibly others too.

[Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback device
on `pavucontrol`, but there is no sound.

A functional workaround is to, after having connected it, to go the
`Configuration` tab, and in the `Profile` dropdown, to choose `...
HSP/HFP`, which will make them play as expected (but in low quality),
then switch to `... A2DP Sink` (they will play in high quality).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: myuser2936 F pulseaudio
/dev/snd/controlC2: myuser2936 F pulseaudio
/dev/snd/controlC0: myuser2936 F pulseaudio
Date: Mon May 16 14:18:58 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-11 (66 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XN-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first

Status in bluez package in

[Desktop-packages] [Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

** Description changed:

  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
+ The SRU was authored by Luke Yelavich with help from Konrad Zapałowicz.
+ And it has received further testing over the past two months by Konrad,
+ Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes
+ the changelog wording from Luke's original PPA.
+ 
  [Original 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.

** Description changed:

  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
- The SRU was authored by Luke Yelavich with help from Konrad Zapałowicz.
- And it has received further testing over the past two months by Konrad,
- Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes
- the changelog wording from Luke's original PPA.
+ The patch was authored by Luke Yelavich with help from Konrad
+ Zapałowicz. And it has received further testing over the past two months
+ by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
+ only changes the changelog wording from Luke's original PPA.
  
  [Original 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.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to

[Desktop-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

** Description changed:

  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1438510.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
+ The patch was authored by Luke Yelavich with help from Konrad
+ Zapałowicz. And it has received further testing over the past two months
+ by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
+ only changes the changelog wording from Luke's original PPA.
+ 
  [Original Description]
  Hi,
  
  I found a bug in Ubuntu 14.04 !
  
  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the audio
  preferences.
  
  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.
  
  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

** Description changed:

[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Other notes]
Related to bug 1283003 and bug 1438510. Possibly others too. The debdiff
which fixes this is attached to bug 1438510.

Please note that Bluetooth and Bluetooth audio support in xenial is
still not perfect. This SRU only aims to address a few of the most
troublesome issues. Please consider the fact that this is an incremental
improvement and some people are still likely to experience some bugs
related to pulseaudio and Bluetooth, even after this SRU.
+
+ The patch was authored by Luke Yelavich with help from Konrad
+ Zapałowicz. And it has received further testing over the past two months
+ by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
+ only changes the changelog wording from Luke's original PPA.

[Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback device
on `pavucontrol`, but there is no sound.

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

Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first

Status in bluez package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
In Progress

Bug description:
[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Verify in Sound settings you have it set to

[Desktop-packages] [Bug 1693099] [NEW] Firefox address bar not working

2017-05-23 Thread Parag

Public bug reported:

Firefox does not search for site in the address bar in the default tab
after launch, not even the bookmarks or recent sites list on the local
computer. It however fucntions normally when the same search is typed
into another (newly opened)  tab's address bar . After this is done, the
address bar in the original (first) tab also works normally.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 53.0.2+build1-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
Uname: Linux 3.13.0-119-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  parag  2298 F pulseaudio
 /dev/snd/controlC0:  parag  2298 F pulseaudio
BuildID: 20170509210304
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed May 24 10:24:47 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 #auto eth0
 #iface eth0 inet dhcp
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2015-09-27 (604 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
IpRoute:
 default via 192.168.1.41 dev eth0  proto static 
 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.18  metric 1
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=53.0.2/20170509210304 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to trusty on 2017-05-03 (20 days ago)
dmi.bios.date: 10/16/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Q550LF.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Q550LF
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ550LF.211:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnQ550LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ550LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: Q550LF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  Firefox address bar not working

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox does not search for site in the address bar in the default tab
  after launch, not even the bookmarks or recent sites list on the local
  computer. It however fucntions normally when the same search is typed
  into another (newly opened)  tab's address bar . After this is done,
  the address bar in the original (first) tab also works normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 53.0.2+build1-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-119-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  parag  2298 F pulseaudio
   /dev/snd/controlC0:  parag  2298 F pulseaudio
  BuildID: 20170509210304
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Wed May 24 10:24:47 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #auto eth0
   #iface eth0 inet dhcp
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-09-27 (604 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.1.41 dev eth0  proto static 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.18  metric 1
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=53.0.2/20170509210304 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes:

[Desktop-packages] [Bug 1643134] Re: Switch gnome-software to use PackageKit backend

Iain raised two issues via email:

There's two things I'm already aware of.

  - It came up last cycle that when PK is built, gnome-software claims
the PackageKit session interface on the bus. This is used for
example to install missing GStreamer codecs but it turned out to be
broken, so we disabled it. We should make sure to track that and get
it working. Not sure what will be needed - maybe some aptcc work.

  - I talked to Richard about this and he isn't interested in supporting
it - probably fairly - but maybe we want to turn off updates in the
PackageKit plugin as long as we have update-manager. I'm not sure it
was the best idea for us to support upgrades in the apt plugin, but
PK inside gnome-software doesn't do UPDATABLE_LIVE (online) updates
at the minute. It would be work to enable those and I think we might
want to punt on this until we get agreement to get rid of
update-manager, presumably not in this cycle. That conversation was
what led Richard to work on release EOL support inside
gnome-software though, which was nice. :)

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

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

Title:
  Switch gnome-software to use PackageKit backend

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  This is a tracking bug to switch gnome-software from the Ubuntu-
  specific apt backend to the PackageKit backend used by other distros.
  In particular this is the backend used by Debian.

  To build, just uncomment the commented-out packagekit line in gnome-
  software's debian/rules and remove libapt-pkg-dev from Build-Depends.
  (You can also drop aptdaemon from Depends.)

  Changes
  ===
  - It fixes some annoying bugs lingering in Ubuntu 16.04 LTS: LP: #1551599.

  - It may also allow us to drop sessioninstaller (LP: #1661371)

  - On an individual app page, Source is listed as something like
  'ubuntu-zesty-universe' or ubuntu-yakkety-updates-main' or 'lp-ppa-
  gnome3-team-gnome3-staging-yakkety-main' instead of just 'Ubuntu'

  - On an individual app page, apps from multiverse or restricted will
  show License as 'Proprietary' (example: VirtualBox or Devede ). This
  also happens for locally installed apps (i.e. not matching what's in
  your apt sources). I don't think it happens for PPAs since everything
  in a PPA is in 'main'.

  - If you install an app using GNOME Software (or I assume another
  PackageKit app), it lists the date it was last installed or updated on
  the individual app page with a link to see its update history. (But
  the problem here is that update-manager doesn't use PK nor does apt on
  the command line.)

  - Any update, no matter how small, is only permitted as an offline
  update. The button says "Restart & Install". It does seem to work fine
  though.

  - Another bug is that installing or Removing an app inside GNOME
  Software is enough for it to "forget" about available Updates and
  think that everything is "up to date".

  (It looks like gnome-software 3.24 will let us completely disable
  gnome-software's update mechanism and the Updates tab by default so
  these previous two differences may be irrelevant then.)

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

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

[Desktop-packages] [Bug 1302614] Re: light theme windows have dark elements

2017-05-23 Thread Treviño

** Changed in: light-themes (Ubuntu)
   Status: New => Fix Released

** Changed in: light-themes (Ubuntu Precise)
   Status: New => Fix Released

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

Title:
  light theme windows have dark elements

Status in light-themes package in Ubuntu:
  Fix Released
Status in light-themes source package in Precise:
  Fix Released

Bug description:
  When using the light theme in Ubuntu 12.04, I notice that elements of the 
dark theme are present in the light theme as well.
  Attached is a screenshot that shows the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.9.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Apr  4 08:53:10 2014
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130128)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1302614/+subscriptions

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

[Desktop-packages] [Bug 1040259] Re: FFE: libmessaging-menu transitions for quantal

** Changed in: quassel (Ubuntu)
   Status: New => Won't Fix

** Changed in: kdenetwork (Ubuntu)
   Status: New => Won't Fix

** Changed in: gm-notify (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: kdepim (Ubuntu)
   Status: New => Won't Fix

** Changed in: libdbusmenu-qt (Ubuntu)
   Status: New => Won't Fix

** Changed in: openfetion (Ubuntu)
   Status: New => Won't Fix

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

Title:
  FFE: libmessaging-menu transitions for quantal

Status in Gmail Watcher:
  Triaged
Status in Lightread:
  Triaged
Status in Quassel:
  New
Status in skype-wrapper:
  In Progress
Status in evolution-indicator package in Ubuntu:
  Fix Released
Status in gm-notify package in Ubuntu:
  Won't Fix
Status in guayadeque package in Ubuntu:
  Fix Released
Status in gwibber package in Ubuntu:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in kdenetwork package in Ubuntu:
  Won't Fix
Status in kdepim package in Ubuntu:
  Won't Fix
Status in libdbusmenu-qt package in Ubuntu:
  Won't Fix
Status in libunity-webapps package in Ubuntu:
  Fix Released
Status in liferea package in Ubuntu:
  Fix Released
Status in openfetion package in Ubuntu:
  Won't Fix
Status in pidgin package in Ubuntu:
  Fix Released
Status in pidgin-libnotify package in Ubuntu:
  Fix Released
Status in quassel package in Ubuntu:
  Won't Fix
Status in smuxi package in Ubuntu:
  Fix Released
Status in telepathy-indicator package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in unity-mail package in Ubuntu:
  Fix Released
Status in xchat-indicator package in Ubuntu:
  Fix Released
Status in gm-notify source package in Quantal:
  Won't Fix
Status in guayadeque source package in Quantal:
  Won't Fix
Status in gwibber source package in Quantal:
  Fix Released
Status in indicator-messages source package in Quantal:
  Fix Released
Status in kdenetwork source package in Quantal:
  Won't Fix
Status in kdepim source package in Quantal:
  Won't Fix
Status in libdbusmenu-qt source package in Quantal:
  Won't Fix
Status in libunity-webapps source package in Quantal:
  Fix Released
Status in liferea source package in Quantal:
  Invalid
Status in openfetion source package in Quantal:
  Won't Fix
Status in pidgin source package in Quantal:
  Won't Fix
Status in pidgin-libnotify source package in Quantal:
  Won't Fix
Status in quassel source package in Quantal:
  Won't Fix
Status in smuxi source package in Quantal:
  Fix Released
Status in telepathy-indicator source package in Quantal:
  Fix Released
Status in thunderbird source package in Quantal:
  Fix Released
Status in unity-mail source package in Quantal:
  Fix Released
Status in xchat-indicator source package in Quantal:
  Fix Released

Bug description:
  indicator-messages got updated, introducing a new libmessaging-menu
  api (deprecating the old libindicate library) which should make
  application developper's life easier.

  The indicator work is done and the library is ready and we started
  porting applications

  The current stack is being tested in https://launchpad.net/~ubuntu-
  desktop/+archive/ppa/

  It includes
  - indicator-messages
  - gwibber
  - indicator-telepathy
  - thunderbird (soon, work is being finished)

  which is what we consider the minimal set for landing the feature

  for quantal we will add those soon:
  - pidgin
  - xchat-indicator
  - evolution-indicator

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

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

[Desktop-packages] [Bug 1675273] Re: Can't add online account

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

** Changed in: account-plugins (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can't add online account

Status in account-plugins package in Ubuntu:
  Expired

Bug description:
  'add account' does nothing, it's a dead button.

  Ubuntu 16.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1675273/+subscriptions

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

[Desktop-packages] [Bug 1675445] Re: Cannot login to install snaps

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

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cannot login to install snaps

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  I'm unable to login to gnome software on an up to date 16.04 system (a
  clean brand new dell xps laptop which has been dist-upgraded to latest
  packages in xenial)

  Currently have version 3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1
  installed.

  When I try to login it just claims my password is wrong. This sounds
  like bug 1616943 which is apparently fixed.

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

-- 
Mailing list: https://launchpad.net/~desktop-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 audio no longer supports A2DP (stuck in HSP/HFP mode)

Attached debdiff for updating xenial to pulseaudio 1:8.0-0ubuntu3.3, in
order to address a few problems with Bluetooth audio (A2DP).

** Patch added: "xenial-a2dp-fixes-may2017.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1438510/+attachment/4882273/+files/xenial-a2dp-fixes-may2017.debdiff

-- 
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 audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  [Original 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 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

** Description changed:

+ [Impact]
+ Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.
+ 
+ [Test Case]
+ 1. Pair a Bluetooth audio device with Ubuntu.
+ 2. Go to Sound settings and try to select the device.
+ Expected: The Bluetooth audio device is selectable (is usable).
+ 
+ [Regression Potential]
+ Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
+ 
+ [Other notes]
+ Related to bug 1438510 and bug 1582213. Possibly others too.
+ 
+ Please note that Bluetooth and Bluetooth audio support in xenial is
+ still not perfect. This SRU only aims to address a few of the most
+ troublesome issues. Please consider the fact that this is an incremental
+ improvement and some people are still likely to experience some bugs
+ related to pulseaudio and Bluetooth, even after this SRU.
+ 
+ [Original Description]
  Hi,
  
  I found a bug in Ubuntu 14.04 !
  
  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the audio
  preferences.
  
  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.
  
  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

** Description changed:

  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
- Related to bug 1438510 and bug 1582213. Possibly others too.
+ Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1438510.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
  [Original Description]
  Hi,
  
  I found a bug in Ubuntu 14.04 !
  
  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the audio
  preferences.
  
  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.
  
  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support

[Desktop-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

** Description changed:

- Bluetooth device doesn't play any sound in A2DP mode unless set to
- HSP/HFP first
+ [Impact]
+ Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

- ---
+ [Test Case]
+ 1. Pair a Bluetooth audio device with Ubuntu.
+ 2. Verify in Sound settings you have it set to A2DP mode.
+ 3. Turn off and then on the Bluetooth device.
+ 4. Verify the device has reconnected and if not, force it to in the Bluetooth
indicator menu.
+ 5. Open Sound settings again, select the device and verify it's reappeared in
A2DP mode.
+ 6. Click 'Test Sound'.
+ Expected: Sound can be heard from the Bluetooth device.

+ [Regression Potential]
+ Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main
area affected. A combination of related A2DP bugs in pulseaudio in xenial means
it is difficult to get working at all without this patch. So highly unlikely
Bluetooth audio support could get worse. Since pulseaudio itself is being
modified there is always a regression potential in support for other audio
devices, but several audio devices have been tested and all continue to work
well with the patch.
+
+ [Other notes]
+ Related to bug 1283003 and bug 1438510. Possibly others too.
+
+ Please note that Bluetooth and Bluetooth audio support in xenial is
+ still not perfect. This SRU only aims to address a few of the most
+ troublesome issues. Please consider the fact that this is an incremental
+ improvement and some people are still likely to experience some bugs
+ related to pulseaudio and Bluetooth, even after this SRU.
+
+ [Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback device
on `pavucontrol`, but there is no sound.

** Description changed:

[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Desktop-packages] [Bug 1693089] Re: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS

** Description changed:

  Note to Sponsors
  
  Since Precise is still partially open, let's see if the Release/SRU Teams are 
willing to accept this SRU for Precise ecause of the Impact there.
  
  Impact
  --
  Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.
  
  This is a problem because the very popular Travis service for continuous
  integration (CI) on platforms like Github still uses 12.04 LTS. Travis
  does not offer a 16.04 platform and the 14.04 platform is still only in
  beta. This caused this pull request to fail its CI check:
  
  https://travis-ci.org/zdohnal/system-config-printer/builds/222023750
  https://github.com/zdohnal/system-config-printer/pull/41
+ 
+ This SRU adds these Desktop Environments to the recognized list for
+ 14.04 LTS: Cinnamon, EDE, LXQt.
+ 
+ If accepted, 12.04 LTS will also add TDE.
  
  Test Case
  -
  1. Save the following lines in a file named calc.desktop
  
  [Desktop Entry]
  Name=Calculator
  Exec=gnome-calculator
  Icon=accessories-calculator
  Type=Application
  OnlyShowIn=Cinnamon;LXQt;EDE;
  Categories=GNOME;GTK;Utility;Calculator;
  
  2. Run
  desktop-file-validate calc.desktop
  
  The command should complete with no error message.
  
  A failure would look something like:
  calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"
  
  Regression Potential
  -
  This only adds a few entries to the list of registered desktop environments.
  
  This change is backported from desktop-file-utils 0.23 which is in
  Ubuntu 16.04 LTS.

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

Title:
  Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04
  LTS

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Precise:
  Triaged
Status in desktop-file-utils source package in Trusty:
  Triaged

Bug description:
  Note to Sponsors
  
  Since Precise is still partially open, let's see if the Release/SRU Teams are 
willing to accept this SRU for Precise ecause of the Impact there.

  Impact
  --
  Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.

  This is a problem because the very popular Travis service for
  continuous integration (CI) on platforms like Github still uses 12.04
  LTS. Travis does not offer a 16.04 platform and the 14.04 platform is
  still only in beta. This caused this pull request to fail its CI
  check:

  https://travis-ci.org/zdohnal/system-config-printer/builds/222023750
  https://github.com/zdohnal/system-config-printer/pull/41

  This SRU adds these Desktop Environments to the recognized list for
  14.04 LTS: Cinnamon, EDE, LXQt.

  If accepted, 12.04 LTS will also add TDE.

  Test Case
  -
  1. Save the following lines in a file named calc.desktop

  [Desktop Entry]
  Name=Calculator
  Exec=gnome-calculator
  Icon=accessories-calculator
  Type=Application
  OnlyShowIn=Cinnamon;LXQt;EDE;
  Categories=GNOME;GTK;Utility;Calculator;

  2. Run
  desktop-file-validate calc.desktop

  The command should complete with no error message.

  A failure would look something like:
  calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"

  Regression Potential
  -
  This only adds a few entries to the list of registered desktop environments.

  This change is backported from desktop-file-utils 0.23 which is in
  Ubuntu 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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 audio no longer supports A2DP (stuck in HSP/HFP mode)

** Description changed:

+ [Impact]
+ Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.
+ 
+ [Test Case]
+ 1. Pair a Bluetooth audio device with Ubuntu.
+ 2. Go to Sound settings and check the device's current "Mode".
+ 3. If the current Mode is not yet A2DP then try to set it to A2DP
+ Expected: The mode is either A2DP by default or can be set to it.
+ 
+ [Regression Potential]
+ Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
+ 
+ [Other notes]
+ Related to bug 1283003 and bug 1582213. Possibly others too.
+ 
+ Please note that Bluetooth and Bluetooth audio support in xenial is
+ still not perfect. This SRU only aims to address a few of the most
+ troublesome issues. Please consider the fact that this is an incremental
+ improvement and some people are still likely to experience some bugs
+ related to pulseaudio and Bluetooth, even after this SRU.
+ 
+ [Original 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.

-- 
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 audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  [Original 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 1693094] Re: package lightdm 1.22.0-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

** Tags removed: need-duplicate-check

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

Title:
  package lightdm 1.22.0-0ubuntu2.1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in lightdm package in Ubuntu:
  New

Bug description:
  It always happens with the normal update. Sometimes notebook hangs up
  with the Uddate. This problem has existed since the upgrade from 16.10
  to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed May 24 05:29:57 2017
  DuplicateSignature:
   package:lightdm:1.22.0-0ubuntu2.1
   Processing triggers for systemd (232-21ubuntu3) ...
   dpkg: error processing package lightdm (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-29 (206 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmConfig:
   [Seat:*]
   autologin-user=
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: lightdm
  Title: package lightdm 1.22.0-0ubuntu2.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (34 days ago)

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

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

[Desktop-packages] [Bug 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->sta

Crash reports on errors.ubuntu.com:
https://errors.ubuntu.com/problem/8b9ed48be6c32a738c54fc1fc36cccf2058be60b

I couldn't find any reports with crashes using the updated libsane, but
this was just a random selection. I don't know of a method to get all
these reports easily and check the libsane dependency?

The small number of 17.04 reports gives me hope this is really fixed...

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

Title:
  colord-sane assert failure: colord-sane: simple-watch.c:454:
  avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT ||
  s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Trusty:
  Triaged
Status in sane-backends source package in Xenial:
  Fix Committed
Status in sane-backends source package in Yakkety:
  Fix Committed
Status in sane-backends source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  A bug in the SANE Kodak driver can cause a SANE device scan to crash the 
client that is using it (e.g. colord, simple-scan).

  [Test Case]
  1. Run a SANE client on a system that is failing Avahi scans (exact cause not 
determined).

  Expected result:
  Client works without crashing.

  Observed result:
  Client crashes.

  [Regression Potential]
  Code fix could cause a change in behaviour of successful Avahi scans for 
Kodak devices, though the fix matches the Avahi documentation for correct usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286/+subscriptions

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

[Desktop-packages] [Bug 1693089] Re: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS

** Patch added: "desktop-file-utils-lp1693089-precise.patch"
   
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+attachment/4882254/+files/desktop-file-utils-lp1693089-precise.patch

** Tags added: patch precise

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

Title:
  Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04
  LTS

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Precise:
  Triaged
Status in desktop-file-utils source package in Trusty:
  Triaged

Bug description:
  Note to Sponsors
  
  Since Precise is still partially open, let's see if the Release/SRU Teams are 
willing to accept this SRU for Precise ecause of the Impact there.

  Impact
  --
  Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.

  This is a problem because the very popular Travis service for
  continuous integration (CI) on platforms like Github still uses 12.04
  LTS. Travis does not offer a 16.04 platform and the 14.04 platform is
  still only in beta. This caused this pull request to fail its CI
  check:

  https://travis-ci.org/zdohnal/system-config-printer/builds/222023750
  https://github.com/zdohnal/system-config-printer/pull/41

  Test Case
  -
  1. Save the following lines in a file named calc.desktop

  [Desktop Entry]
  Name=Calculator
  Exec=gnome-calculator
  Icon=accessories-calculator
  Type=Application
  OnlyShowIn=Cinnamon;LXQt;EDE;
  Categories=GNOME;GTK;Utility;Calculator;

  2. Run
  desktop-file-validate calc.desktop

  The command should complete with no error message.

  A failure would look something like:
  calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"

  Regression Potential
  -
  This only adds a few entries to the list of registered desktop environments.

  This change is backported from desktop-file-utils 0.23 which is in
  Ubuntu 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+subscriptions

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

[Desktop-packages] [Bug 1693089] Re: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS

** Patch added: "desktop-file-utils-lp1693089-trusty.patch"
   
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+attachment/4882255/+files/desktop-file-utils-lp1693089-trusty.patch

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

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

** Changed in: desktop-file-utils (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: desktop-file-utils (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: desktop-file-utils (Ubuntu Precise)
   Status: New => Triaged

** Changed in: desktop-file-utils (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: desktop-file-utils (Ubuntu Trusty)
   Status: New => Triaged

** Description changed:

+ Note to Sponsors
+ 
+ Since Precise is still partially open, let's see if the Release/SRU Teams are 
willing to accept this SRU for Precise ecause of the Impact there.
+ 
  Impact
  --
  Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.
  
  This is a problem because the very popular Travis service for continuous
  integration (CI) on platforms like Github still uses 12.04 LTS. Travis
- offers a beta for 14.04 LTS. This caused this pull request to fail its
- CI check:
+ does not offer a 16.04 platform and the 14.04 platform is still only in
+ beta. This caused this pull request to fail its CI check:
  
  https://travis-ci.org/zdohnal/system-config-printer/builds/222023750
+ https://github.com/zdohnal/system-config-printer/pull/41
  
  Test Case
  -
  1. Save the following lines in a file named calc.desktop
  
  [Desktop Entry]
  Name=Calculator
  Exec=gnome-calculator
  Icon=accessories-calculator
  Type=Application
  OnlyShowIn=Cinnamon;LXQt;EDE;
  Categories=GNOME;GTK;Utility;Calculator;
  
  2. Run
  desktop-file-validate calc.desktop
  
  The command should complete with no error message.
  
  A failure would look something like:
  calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"
  
  Regression Potential
  -
  This only adds a few entries to the list of registered desktop environments.
  
  This change is backported from desktop-file-utils 0.23 which is in
  Ubuntu 16.04 LTS.

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

Title:
  Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04
  LTS

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Precise:
  Triaged
Status in desktop-file-utils source package in Trusty:
  Triaged

Bug description:
  Note to Sponsors
  
  Since Precise is still partially open, let's see if the Release/SRU Teams are 
willing to accept this SRU for Precise ecause of the Impact there.

  Impact
  --
  Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.

  This is a problem because the very popular Travis service for
  continuous integration (CI) on platforms like Github still uses 12.04
  LTS. Travis does not offer a 16.04 platform and the 14.04 platform is
  still only in beta. This caused this pull request to fail its CI
  check:

  https://travis-ci.org/zdohnal/system-config-printer/builds/222023750
  https://github.com/zdohnal/system-config-printer/pull/41

  Test Case
  -
  1. Save the following lines in a file named calc.desktop

  [Desktop Entry]
  Name=Calculator
  Exec=gnome-calculator
  Icon=accessories-calculator
  Type=Application
  OnlyShowIn=Cinnamon;LXQt;EDE;
  Categories=GNOME;GTK;Utility;Calculator;

  2. Run
  desktop-file-validate calc.desktop

  The command should complete with no error message.

  A failure would look something like:
  calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"

  Regression Potential
  -
  This only adds a few entries to the list of registered desktop environments.

  This change is backported from desktop-file-utils 0.23 which is in
  Ubuntu 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+subscriptions

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

[Desktop-packages] [Bug 1693094] [NEW] package lightdm 1.22.0-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

2017-05-23 Thread Wilhelm Hatje

Public bug reported:

It always happens with the normal update. Sometimes notebook hangs up
with the Uddate. This problem has existed since the upgrade from 16.10
to 17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: lightdm 1.22.0-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Wed May 24 05:29:57 2017
DuplicateSignature:
 package:lightdm:1.22.0-0ubuntu2.1
 Processing triggers for systemd (232-21ubuntu3) ...
 dpkg: error processing package lightdm (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-10-29 (206 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
LightdmConfig:
 [Seat:*]
 autologin-user=
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: lightdm
Title: package lightdm 1.22.0-0ubuntu2.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to zesty on 2017-04-19 (34 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package lightdm 1.22.0-0ubuntu2.1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in lightdm package in Ubuntu:
  New

Bug description:
  It always happens with the normal update. Sometimes notebook hangs up
  with the Uddate. This problem has existed since the upgrade from 16.10
  to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed May 24 05:29:57 2017
  DuplicateSignature:
   package:lightdm:1.22.0-0ubuntu2.1
   Processing triggers for systemd (232-21ubuntu3) ...
   dpkg: error processing package lightdm (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-29 (206 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmConfig:
   [Seat:*]
   autologin-user=
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: lightdm
  Title: package lightdm 1.22.0-0ubuntu2.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (34 days ago)

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

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

[Desktop-packages] [Bug 1693089] Re: Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS

** Description changed:

  Impact
  --
+ Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.
  
+ This is a problem because the very popular Travis service for continuous
+ integration (CI) on platforms like Github still uses 12.04 LTS. Travis
+ offers a beta for 14.04 LTS. This caused this pull request to fail its
+ CI check:
  
+ https://travis-ci.org/zdohnal/system-config-printer/builds/222023750
  
  Test Case
  -
+ 1. Save the following lines in a file named calc.desktop
+ 
+ [Desktop Entry]
+ Name=Calculator
+ Exec=gnome-calculator
+ Icon=accessories-calculator
+ Type=Application
+ OnlyShowIn=Cinnamon;LXQt;EDE;
+ Categories=GNOME;GTK;Utility;Calculator;
+ 
+ 2. Run
+ desktop-file-validate calc.desktop
+ 
+ The command should complete with no error message.
+ 
+ A failure would look something like:
+ calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"
  
  Regression Potential
  -
+ This only adds a few entries to the list of registered desktop environments.
+ 
+ This change is backported from desktop-file-utils 0.23 which is in
+ Ubuntu 16.04 LTS.

** Changed in: desktop-file-utils (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04
  LTS

Status in gnome-desktop3 package in Ubuntu:
  Triaged
Status in gnome-desktop3 source package in Precise:
  New

Bug description:
  Impact
  --
  Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.

  This is a problem because the very popular Travis service for
  continuous integration (CI) on platforms like Github still uses 12.04
  LTS. Travis offers a beta for 14.04 LTS. This caused this pull request
  to fail its CI check:

  https://travis-ci.org/zdohnal/system-config-printer/builds/222023750

  Test Case
  -
  1. Save the following lines in a file named calc.desktop

  [Desktop Entry]
  Name=Calculator
  Exec=gnome-calculator
  Icon=accessories-calculator
  Type=Application
  OnlyShowIn=Cinnamon;LXQt;EDE;
  Categories=GNOME;GTK;Utility;Calculator;

  2. Run
  desktop-file-validate calc.desktop

  The command should complete with no error message.

  A failure would look something like:
  calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"

  Regression Potential
  -
  This only adds a few entries to the list of registered desktop environments.

  This change is backported from desktop-file-utils 0.23 which is in
  Ubuntu 16.04 LTS.

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

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

[Desktop-packages] [Bug 1693089] [NEW] Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04 LTS

Public bug reported:

Impact
--
Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.

This is a problem because the very popular Travis service for continuous
integration (CI) on platforms like Github still uses 12.04 LTS. Travis
offers a beta for 14.04 LTS. This caused this pull request to fail its
CI check:

https://travis-ci.org/zdohnal/system-config-printer/builds/222023750

Test Case
-
1. Save the following lines in a file named calc.desktop

[Desktop Entry]
Name=Calculator
Exec=gnome-calculator
Icon=accessories-calculator
Type=Application
OnlyShowIn=Cinnamon;LXQt;EDE;
Categories=GNOME;GTK;Utility;Calculator;

2. Run
desktop-file-validate calc.desktop

The command should complete with no error message.

A failure would look something like:
calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"

Regression Potential
-
This only adds a few entries to the list of registered desktop environments.

This change is backported from desktop-file-utils 0.23 which is in
Ubuntu 16.04 LTS.

** Affects: desktop-file-utils (Ubuntu)
 Importance: Undecided
 Status: Fix Released


** Tags: trusty

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

Title:
  Cinnamon is not a recognized Desktop Environment before Ubuntu 16.04
  LTS

Status in desktop-file-utils package in Ubuntu:
  Fix Released

Bug description:
  Impact
  --
  Cinnamon (and the less popular EDE and LXQt) desktops are not recognized by 
desktop-file-validate in Ubuntu 12.04 LTS or 14.04 LTS.

  This is a problem because the very popular Travis service for
  continuous integration (CI) on platforms like Github still uses 12.04
  LTS. Travis offers a beta for 14.04 LTS. This caused this pull request
  to fail its CI check:

  https://travis-ci.org/zdohnal/system-config-printer/builds/222023750

  Test Case
  -
  1. Save the following lines in a file named calc.desktop

  [Desktop Entry]
  Name=Calculator
  Exec=gnome-calculator
  Icon=accessories-calculator
  Type=Application
  OnlyShowIn=Cinnamon;LXQt;EDE;
  Categories=GNOME;GTK;Utility;Calculator;

  2. Run
  desktop-file-validate calc.desktop

  The command should complete with no error message.

  A failure would look something like:
  calc.desktop: error: value "Cinnamon;LXQt;EDE;" for key "OnlyShowIn" in group 
"Desktop Entry" contains an unregistered value "Cinnamon"; values extending the 
format should start with "X-"

  Regression Potential
  -
  This only adds a few entries to the list of registered desktop environments.

  This change is backported from desktop-file-utils 0.23 which is in
  Ubuntu 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1693089/+subscriptions

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

[Desktop-packages] [Bug 1690131] Re: display adapter not working with vmware

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

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

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

Title:
  display adapter not working with vmware

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The virtual machine colors are corrupted when logged in to virtual
  host.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 11 13:00:48 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2017-03-20 (51 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B250M-D3H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic.efi.signed 
root=UUID=fbf200a7-baa7-408b-8b60-06c06081cfce ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M-D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd11/03/2016:svnGigabyteTechnologyCo.,Ltd.:pnB250M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB250M-D3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: B250M-D3H
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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 May 11 10:36:10 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputSleep Button KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputDP-1
DP-2  HDMI-1  HDMI-2  HDMI-3
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1693033] Re: Please merge system-config-printer with Debian 1.5.9

Thanks, but there were some other changes in the Debian package besides
the new version:

https://tracker.debian.org/media/packages/s/system-config-
printer/changelog-1.5.9-1

Switching to dh in particular seems very helpful. For instance, it
provides dh_auto_test to automatically run the package's build tests.

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

Title:
  Please merge system-config-printer with Debian 1.5.9

Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  system-config-printer is now being maintained (hopefully?) at
  https://github.com/zdohnal/system-config-printer

  Debian packaged the latest version from there, but it was done too
  late for Ubuntu 17.04. We should do this merge for 17.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1693033/+subscriptions

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

[Desktop-packages] [Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

** Summary changed:

- [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of 
updates
+ Bluetooth headset/speakers listed but not selectable in Sound settings

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => High

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Desktop-packages] [Bug 1362313] Re: PulseAudio can't find Bluetooth device after reconnecting

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

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

Title:
  PulseAudio can't find Bluetooth device after reconnecting

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  What happens?
  1. connct a2dp device
  2. start playback
  3. reconnect a2dp device from remote
  4. ubuntu reports device is connected
  5. a2dp device does not show up in pulseaudio nor does music playback work 
(via a2dp device). sometimes there are "timeout" error messages in kde.
  6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio 
daemon. it all does not help.
  7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then 
connect the device (if not already auto-connected)

  After step 3, there is the following error message in syslog (no other
  errors in syslog or dmesg):

  pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release
  transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method
  "Release" with signature "s" on interface "org.bluez.MediaTransport"
  doesn't exist

  What I expected to happen?
  After the device reconnect, the music playback switches playback back to the 
bluetooth device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bluetooth 4.101-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Wed Aug 27 21:41:34 2014
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  SourcePackage: bluez
  UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: B85 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CC:E6:D5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:100536 acl:18 sco:0 events:14179 errors:0
TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0
  syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: 
/org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready

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

-- 
Mailing list: https://launchpad.net/~desktop-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 audio no longer supports A2DP (stuck in HSP/HFP mode)

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => In Progress

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

-- 
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 audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Bluetooth device doesn't play any sound in A2DP mode unless set to
  HSP/HFP first

  ---

  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-05-23 Thread Zhanglei Mao

** Attachment added: "sosreport at 24 May 2017"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4882242/+files/sosreport-ubuntu.d05-20170524102121.tar.xz

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Desktop-packages] [Bug 1693071] Re: package libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2 failed to install/upgrade: package libp11-kit-gnome-keyring:i386 is not ready for configuration cannot config

** 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/1693071

Title:
  package libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2 failed to
  install/upgrade: package libp11-kit-gnome-keyring:i386 is not ready
  for configuration  cannot configure (current status 'half-installed')

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  funktioniert nicht

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   wine: Install
   fonts-horai-umefont: Configure
   libp11-kit-gnome-keyring: Configure
   wine: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 24 04:26:29 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:i386:3.18.3-0ubuntu2
   Unpacking wine (1:1.8.0-0ubuntu1~ubuntu15.10.1~ppa1) over 
(1:1.6.2-0ubuntu14.2) ...
   dpkg: error processing package fonts-horai-umefont (--configure):
package fonts-horai-umefont is not ready for configuration
  ErrorMessage: package libp11-kit-gnome-keyring:i386 is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-08 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2 failed to 
install/upgrade: package libp11-kit-gnome-keyring:i386 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/gnome-keyring/+bug/1693071/+subscriptions

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

[Desktop-packages] [Bug 1693071] [NEW] package libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2 failed to install/upgrade: package libp11-kit-gnome-keyring:i386 is not ready for configuration cannot conf

2017-05-23 Thread Jens Nitschke

Public bug reported:

funktioniert nicht

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 wine: Install
 fonts-horai-umefont: Configure
 libp11-kit-gnome-keyring: Configure
 wine: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed May 24 04:26:29 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu7
DuplicateSignature:
 package:libp11-kit-gnome-keyring:i386:3.18.3-0ubuntu2
 Unpacking wine (1:1.8.0-0ubuntu1~ubuntu15.10.1~ppa1) over 
(1:1.6.2-0ubuntu14.2) ...
 dpkg: error processing package fonts-horai-umefont (--configure):
  package fonts-horai-umefont is not ready for configuration
ErrorMessage: package libp11-kit-gnome-keyring:i386 is not ready for 
configuration  cannot configure (current status 'half-installed')
InstallationDate: Installed on 2017-05-08 (15 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gnome-keyring
Title: package libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2 failed to 
install/upgrade: package libp11-kit-gnome-keyring:i386 is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2 failed to
  install/upgrade: package libp11-kit-gnome-keyring:i386 is not ready
  for configuration  cannot configure (current status 'half-installed')

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  funktioniert nicht

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   wine: Install
   fonts-horai-umefont: Configure
   libp11-kit-gnome-keyring: Configure
   wine: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed May 24 04:26:29 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:i386:3.18.3-0ubuntu2
   Unpacking wine (1:1.8.0-0ubuntu1~ubuntu15.10.1~ppa1) over 
(1:1.6.2-0ubuntu14.2) ...
   dpkg: error processing package fonts-horai-umefont (--configure):
package fonts-horai-umefont is not ready for configuration
  ErrorMessage: package libp11-kit-gnome-keyring:i386 is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-08 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring:i386 3.18.3-0ubuntu2 failed to 
install/upgrade: package libp11-kit-gnome-keyring:i386 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/gnome-keyring/+bug/1693071/+subscriptions

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

[Desktop-packages] [Bug 1693033] Re: Please merge system-config-printer with Debian 1.5.9

2017-05-23 Thread Till Kamppeter

s-c-p package updated to current GIT snapshot.

Thank you for the hint.


** Changed in: system-config-printer (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please merge system-config-printer with Debian 1.5.9

Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  system-config-printer is now being maintained (hopefully?) at
  https://github.com/zdohnal/system-config-printer

  Debian packaged the latest version from there, but it was done too
  late for Ubuntu 17.04. We should do this merge for 17.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1693033/+subscriptions

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

[Desktop-packages] [Bug 1693066] [NEW] PCI/internal sound card not detected

2017-05-23 Thread NeuroFox

Public bug reported:

Description:Ubuntu 16.04.2 LTS
Release:16.04

apt-cache policy pkgname
Unable to locate package pkgname

I'm new to Ubuntu.
On the start all was good with sound. 
Wanted to install my original sound driver.
After trying to install realtek hd driver the Dummy audio appeared on my audio 
settings.
No sound. Then i tried to reinstall original driver - still no result. I have 0 
sound card modules, and don't know how to return sound..
https://help.ubuntu.com/community/SoundTroubleshooting
Tried this guide but still, even after purge, it is not working.
Maybe its not a bug, just wrong settings, but still.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Wed May 24 04:06:12 2017
InstallationDate: Installed on 2017-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CC.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-05-24T03:38:38.603132

** 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/1693066

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  apt-cache policy pkgname
  Unable to locate package pkgname

  I'm new to Ubuntu.
  On the start all was good with sound. 
  Wanted to install my original sound driver.
  After trying to install realtek hd driver the Dummy audio appeared on my 
audio settings.
  No sound. Then i tried to reinstall original driver - still no result. I have 
0 sound card modules, and don't know how to return sound..
  https://help.ubuntu.com/community/SoundTroubleshooting
  Tried this guide but still, even after purge, it is not working.
  Maybe its not a bug, just wrong settings, but still.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed May 24 04:06:12 2017
  InstallationDate: Installed on 2017-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CC.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550CC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-05-24T03:38:38.603132

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1693066/+subscriptions

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

[Desktop-packages] [Bug 1641889] Re: The network indicator shows the wrong status

2017-05-23 Thread Shih-Yuan Lee

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

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

Title:
  The network indicator shows the wrong status

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

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , disconnect wireless connection
  Note : the issue can't be reproduced with wifi connected
  2.Enable/disable wifi function by pressing hotkey then check network manager 
status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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

[Desktop-packages] [Bug 1643134] Re: Switch gnome-software to use PackageKit backend

We can drop the dpkg plugin in gnome-software master once this is complete:
https://mail.gnome.org/archives/gnome-software-list/2017-May/msg6.html

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

Title:
  Switch gnome-software to use PackageKit backend

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  This is a tracking bug to switch gnome-software from the Ubuntu-
  specific apt backend to the PackageKit backend used by other distros.
  In particular this is the backend used by Debian.

  To build, just uncomment the commented-out packagekit line in gnome-
  software's debian/rules and remove libapt-pkg-dev from Build-Depends.
  (You can also drop aptdaemon from Depends.)

  Changes
  ===
  - It fixes some annoying bugs lingering in Ubuntu 16.04 LTS: LP: #1551599.

  - It may also allow us to drop sessioninstaller (LP: #1661371)

  - On an individual app page, Source is listed as something like
  'ubuntu-zesty-universe' or ubuntu-yakkety-updates-main' or 'lp-ppa-
  gnome3-team-gnome3-staging-yakkety-main' instead of just 'Ubuntu'

  - On an individual app page, apps from multiverse or restricted will
  show License as 'Proprietary' (example: VirtualBox or Devede ). This
  also happens for locally installed apps (i.e. not matching what's in
  your apt sources). I don't think it happens for PPAs since everything
  in a PPA is in 'main'.

  - If you install an app using GNOME Software (or I assume another
  PackageKit app), it lists the date it was last installed or updated on
  the individual app page with a link to see its update history. (But
  the problem here is that update-manager doesn't use PK nor does apt on
  the command line.)

  - Any update, no matter how small, is only permitted as an offline
  update. The button says "Restart & Install". It does seem to work fine
  though.

  - Another bug is that installing or Removing an app inside GNOME
  Software is enough for it to "forget" about available Updates and
  think that everything is "up to date".

  (It looks like gnome-software 3.24 will let us completely disable
  gnome-software's update mechanism and the Updates tab by default so
  these previous two differences may be irrelevant then.)

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

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

[Desktop-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2017-05-23 Thread nekojira

there was some improvement with 4.4.0-78 but still is ongoing - Ubuntu
can't wake a suspended monitor, doesn't remember monitors positions

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

See
https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f
for error reports.

** Description changed:

- = Test Case =
- 1. Download the debian package of Chrome from google
- 2. Open nautilus and double-click on the file to launch ubuntu software
- 3. Install the package and proceed with the installation
+ [Impact]
+ Some packages stall on installing. These are packages that generate multiple 
debconf prompts (the prompts may be empty and so not user visible, e.g. 
gconf2-common).
  
- = Expected result =
- Chrome installs correctly
+ [Test Case]
+ 1. Download the debian package of Chrome from www.google.com/chrome.
+ 2. Install the package (browser will prompt, or double click on package in 
Nautilus).
  
- = Actual result =
- The installation hangs on the following command in gconf2-common.postinst
+ Expected result:
+ Chrome installs correctly.
  
- ucf /usr/share/gconf/default.path /etc/gconf/2/path
+ Observed result:
+ The installation hangs on 51%.
  
- 
- Record on errors.ubuntu.com
- https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f
- 
- = Original Report =
- I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
- This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
- The same file was successfully installed with gdebi.
- 
- ProblemType: Package
- DistroRelease: Ubuntu 17.04
- Package: gconf2-common 3.2.6-3ubuntu7
- ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
- Uname: Linux 4.10.0-20-generic x86_64
- ApportVersion: 2.20.4-0ubuntu4
- AptOrdering:
-  gconf2-common:amd64: Install
-  libgconf-2-4:amd64: Install
-  gconf-service-backend:amd64: Install
-  gconf-service:amd64: Install
-  NULL: ConfigurePending
- Architecture: amd64
- Date: Sat May  6 13:56:26 2017
- ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
- InstallationDate: Installed on 2017-05-04 (1 days ago)
- InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
- PackageArchitecture: all
- RelatedPackageVersions:
-  dpkg 1.18.10ubuntu2
-  apt  1.4
- SourcePackage: gconf
- Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
- UpgradeStatus: No upgrade log present (probably fresh install)
+ [Regression Potential]
+ The debconf conde was modified to support multiple requests. This could 
expose other debconf issues or break other .deb install code.

** Description changed:

  [Impact]
  Some packages stall on installing. These are packages that generate multiple 
debconf prompts (the prompts may be empty and so not user visible, e.g. 
gconf2-common).
  
  [Test Case]
- 1. Download the debian package of Chrome from www.google.com/chrome.
- 2. Install the package (browser will prompt, or double click on package in 
Nautilus).
+ 1. Remove gconf2-common (warning, may uninstall packages like gnome-terminal):
+ $ sudo apt purge gconf2-common
+ 2. Download the debian package of Chrome from www.google.com/chrome.
+ 3. Install the package (browser will prompt, or double click on package in 
Nautilus).
  
  Expected result:
  Chrome installs correctly.
  
  Observed result:
  The installation hangs on 51%.
  
  [Regression Potential]
  The debconf conde was modified to support multiple requests. This could 
expose other debconf issues or break other .deb install code.

** Summary changed:

- package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128
+ Packages that trigger multiple debconf prompts fail to install

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

Title:
  Packages that trigger multiple debconf prompts fail to install

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

Bug description:
  [Impact]
  Some packages stall on installing. These are packages that generate multiple 
debconf prompts (the prompts may be empty and so not user visible, e.g. 
gconf2-common).

  [Test Case]
  1. Remove gconf2-common (warning, may uninstall packages like gnome-terminal):
  $ sudo apt purge gconf2-common
  2. Download the debian package of Chrome from www.google.com/chrome.
  3. Install the package (browser will prompt, or double click on package in 
Nautilus).

  Expected result:
  Chrome installs correctly.

  Observed result:
  The installation

[Desktop-packages] [Bug 1692398] Re: Input error can lead to continuous searches

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

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

** Description changed:

  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.
  
  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'
  
  Expected result:
- Searches stop after a reasonable time.
+ Searches stop after a the search field hits the character limit.
  
  Observed result:
- Searches are continuously generated for each key press.
+ Searches are continuously generated for each key press (there is no limit). 
+ 
+ NOTE: Searches are shown in syslog (snapd debug message).
  
  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

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

Title:
  Input error can lead to continuous searches

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

Bug description:
  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.

  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'

  Expected result:
  Searches stop after a the search field hits the character limit.

  Observed result:
  Searches are continuously generated for each key press (there is no limit). 

  NOTE: Searches are shown in syslog (snapd debug message).

  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

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

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

[Desktop-packages] [Bug 1641889] Re: The network indicator shows the wrong status

This bug was fixed in the package network-manager-applet -
1.2.6-0ubuntu0.16.04.3

---
network-manager-applet (1.2.6-0ubuntu0.16.04.3) xenial-proposed; urgency=medium

  * debian/patches/git_fix_wrong_status_for_wireless_toggle.patch
* Fix wrong status for wireless toggle (LP: #1641889)

 -- Ken VanDine   Tue, 09 May 2017 09:52:11
-0400

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

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

Title:
  The network indicator shows the wrong status

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

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , disconnect wireless connection
  Note : the issue can't be reproduced with wifi connected
  2.Enable/disable wifi function by pressing hotkey then check network manager 
status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

Bug description:
  [Impact]
  Some packages stall on installing. These are packages that generate multiple 
debconf prompts (the prompts may be empty and so not user visible, e.g. 
gconf2-common).

  [Test Case]
  1. Remove gconf2-common (warning, may uninstall packages like gnome-terminal):
  $ sudo apt purge gconf2-common
  2. Download the debian package of Chrome from www.google.com/chrome.
  3. Install the package (browser will prompt, or double click on package in 
Nautilus).

  Expected result:
  Chrome installs correctly.

  Observed result:
  The installation hangs on 51%.

  [Regression Potential]
  The debconf conde was modified to support multiple requests. This could 
expose other debconf issues or break other .deb install code.

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

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

[Desktop-packages] [Bug 1692398] Re: Input error can lead to continuous searches

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  Input error can lead to continuous searches

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

Bug description:
  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.

  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'

  Expected result:
  Searches stop after a the search field hits the character limit.

  Observed result:
  Searches are continuously generated for each key press (there is no limit). 

  NOTE: Searches are shown in syslog (snapd debug message).

  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

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

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

[Desktop-packages] [Bug 1607663] Update Released

2017-05-23 Thread Chris Halse Rogers

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

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

Title:
  vino-server does not autostart on Ubuntu-GNOME

Status in Ubuntu GNOME:
  Fix Committed
Status in vino package in Ubuntu:
  Fix Released
Status in vino source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  The Desktop Sharing option in GNOME's Settings apps silently doesn't work.

  Test Case
  =
  On the host computer:
  1. In Ubuntu GNOME, open the Settings app.
  2. Open the Sharing panel.
  3. In the headerbar, turn on Sharing.
  4. Click Screen Sharing. Turn it On. (If it was already On, turn it off then 
On.)

  On the guest computer:
  5. From a different computer connected to the same local network, attempt to 
connect to the host computer.

  For this, you can install Vinagre. Click Connect. Use Protocol: VNC
  and enter the IP address for the test computer in the Host: field.
  Click Connect.

  On the host computer:
  6. You probably need to approve a popup message to allow the remote user to 
connect.

  Regression Potential
  
  This only adds a symlinked NoDisplay=true .desktop to
  /usr/share/applications/

  Other Info
  ==
  The fix for Ubuntu 16.10 is a bit different. There we can just backport the 
systemd service file added to vino 3.22 since gnome-settings-daemon 3.22 
handles sharing services via systemd user services.

  I verified that the extra .service file does not affect the way vino-
  preferences works in Unity 16.10. It's just ignored and manually
  trying to start the service in Unity doesn't work either which is
  fine. For 17.04+ we should look at having Unity use the systemd user
  service too.

  Original Bug Report with Workaround
  ===
  Running gnome-settings-daemon -r --debug shows that it tries to locate 
vino-server.desktop which it cannot find and therefore fails to start. Looking 
at the debian package, a confirmed and working fix for Ubuntu 16.04 is: sudo ln 
-s /etc/xdg/autostart/vino-server.desktop 
/usr/share/applications/vino-server.desktop or only shipping that file in 
/usr/share/application

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

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

[Desktop-packages] [Bug 1607663] Re: vino-server does not autostart on Ubuntu-GNOME

This bug was fixed in the package vino - 3.8.1-0ubuntu9.2

---
vino (3.8.1-0ubuntu9.2) xenial; urgency=medium

  * Add debian/links to symlink the hidden vino autostart .desktop to
/usr/share/applications/ which is needed for the Desktop Sharing feature
in GNOME's Settings app to work. Thanks Florian Apolloner for the bug
report and suggested fix. (LP: #1607663)

 -- Jeremy Bicha   Sat, 01 Oct 2016 22:57:04 -0400

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

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

Title:
  vino-server does not autostart on Ubuntu-GNOME

Status in Ubuntu GNOME:
  Fix Committed
Status in vino package in Ubuntu:
  Fix Released
Status in vino source package in Xenial:
  Fix Released

Bug description:
  Impact
  ==
  The Desktop Sharing option in GNOME's Settings apps silently doesn't work.

  Test Case
  =
  On the host computer:
  1. In Ubuntu GNOME, open the Settings app.
  2. Open the Sharing panel.
  3. In the headerbar, turn on Sharing.
  4. Click Screen Sharing. Turn it On. (If it was already On, turn it off then 
On.)

  On the guest computer:
  5. From a different computer connected to the same local network, attempt to 
connect to the host computer.

  For this, you can install Vinagre. Click Connect. Use Protocol: VNC
  and enter the IP address for the test computer in the Host: field.
  Click Connect.

  On the host computer:
  6. You probably need to approve a popup message to allow the remote user to 
connect.

  Regression Potential
  
  This only adds a symlinked NoDisplay=true .desktop to
  /usr/share/applications/

  Other Info
  ==
  The fix for Ubuntu 16.10 is a bit different. There we can just backport the 
systemd service file added to vino 3.22 since gnome-settings-daemon 3.22 
handles sharing services via systemd user services.

  I verified that the extra .service file does not affect the way vino-
  preferences works in Unity 16.10. It's just ignored and manually
  trying to start the service in Unity doesn't work either which is
  fine. For 17.04+ we should look at having Unity use the systemd user
  service too.

  Original Bug Report with Workaround
  ===
  Running gnome-settings-daemon -r --debug shows that it tries to locate 
vino-server.desktop which it cannot find and therefore fails to start. Looking 
at the debian package, a confirmed and working fix for Ubuntu 16.04 is: sudo ln 
-s /etc/xdg/autostart/vino-server.desktop 
/usr/share/applications/vino-server.desktop or only shipping that file in 
/usr/share/application

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-05-23 Thread Shawn B

I experience the same issue on 16.04 but it ends up breaking DNS
responses entirely because traffic is forced through the OpenVPN tunnel
where the DNS resides and the local DNS is no longer accessible.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1691996] Re: DNS and search domain is not pushed to systemd-resolved sometimes

2017-05-23 Thread Jonathan Harker

The DNS for the tun0 of my OpenVPN connection completely fails. There's nothing 
in systemd-resolve --status or /var/run/resolv.conf or /etc or any of the other 
usual places; I don't have time to go digging so I shove stuff in /etc/hosts 
for now.
Pretty useless state of affairs, all told...

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

Title:
  DNS and search domain is not pushed to systemd-resolved sometimes

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have an OpenVPN connection with statically configured DNS server
  address and the search domain. When this connection is established,
  there is a high chance that the DNS address and the search domain are
  not pushed to systemd-resolved for this connection. The problem does
  not reproduce reliably, sometimes the parameters are pushed. When the
  parameters are not pushed, 'systemd-resolve --status' reports no DNS
  servers or DNS domain for the VPN connection, and name resolution does
  not work.

  This bug has been reportedly fixed upstream in NetworkManager 1.8. The
  upstream bug reports are:

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

  Please, update NetworkManager shipped with Ubuntu or backport the fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May 19 13:35:42 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-01 (748 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-05-11T15:26:12.449289
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   virbr0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/2  
virbr0  a80bff56-e5d6-4fa4-b544-89cb3c389e3b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  44a70bab-e44e-3942-8259-e96eb6f3fe5b  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   virbr0-nic  tun   unmanaged  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1691996] Re: DNS and search domain is not pushed to systemd-resolved sometimes

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  DNS and search domain is not pushed to systemd-resolved sometimes

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have an OpenVPN connection with statically configured DNS server
  address and the search domain. When this connection is established,
  there is a high chance that the DNS address and the search domain are
  not pushed to systemd-resolved for this connection. The problem does
  not reproduce reliably, sometimes the parameters are pushed. When the
  parameters are not pushed, 'systemd-resolve --status' reports no DNS
  servers or DNS domain for the VPN connection, and name resolution does
  not work.

  This bug has been reportedly fixed upstream in NetworkManager 1.8. The
  upstream bug reports are:

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

  Please, update NetworkManager shipped with Ubuntu or backport the fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May 19 13:35:42 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-01 (748 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-05-11T15:26:12.449289
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   virbr0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/2  
virbr0  a80bff56-e5d6-4fa4-b544-89cb3c389e3b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  44a70bab-e44e-3942-8259-e96eb6f3fe5b  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   virbr0-nic  tun   unmanaged  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-05-23 Thread Mathieu Trudel-Lapierre

I don't know what your "DNS leak test" is, but we can't give much weight
to that unless we also know a lot more about your config for the VPN and
how the test is set up, what it looks for, etc.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1693006] Re: package gconf2-common (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

** Tags removed: need-duplicate-check

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

Title:
  package gconf2-common (not installed) failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  New

Bug description:
  o desktop fecha e rinicia toda hora

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue May 23 15:43:17 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-23 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common (not installed) 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/debconf/+bug/1693006/+subscriptions

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

[Desktop-packages] [Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys

2017-05-23 Thread Steven Danneman

I'm running 16.04 and attempting to use the builtin Backup program which
is a wrapper around deja-dup. I'm trying to target an SSH server for
backups, as it will use rsync block comparisons and be the most
efficient. However, the SSH server has disabled RSA public key
authentication and only supports ecdsa and ed25519.

Backup is using gnome-keyring by default, so it refuses to connect to
SSH.  From /var/log/auth.log:

May 23 15:10:42 hollywood gnome-keyring-daemon[1599]: Unsupported or
unknown SSH key algorithm: ssh-ed25519

Thus, this bug is making other builtin tools less useful as well.

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

Title:
  gnome-keyring doesn't support ecdsa or ed25519 keys

Status in GNOME Keyring:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in gnome-keyring package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-keyring

  I'm not sure I have described it correctly in the summary, but this is what 
happens:
  I run ssh-add in a new terminal and enter my passphrase, which is the same 
for my DSA and ECDSA key: the DSA identity is added, but the ECDSA gets the 
"Error reading response length from authentication socket. Could not add 
identity: /home/claudio/.ssh/id_ecdsa" error.
  I run ssh-agent, copy and paste the output in the terminal and re-run 
ssh-add. Both identities are correctly added:
  
  claudio@Chuck:~$ ssh-add 
  Enter passphrase for /home/claudio/.ssh/id_dsa: 
  Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa)
  Error reading response length from authentication socket.
  Could not add identity: /home/claudio/.ssh/id_ecdsa
  claudio@Chuck:~$ ssh-agent 
  SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK;
  SSH_AGENT_PID=3917; export SSH_AGENT_PID;
  echo Agent pid 3917;
  claudio@Chuck:~$ SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export 
SSH_AUTH_SOCK;
  claudio@Chuck:~$ SSH_AGENT_PID=3917; export SSH_AGENT_PID;
  claudio@Chuck:~$ echo Agent pid 3917;
  Agent pid 3917
  claudio@Chuck:~$ ssh-add 
  Enter passphrase for /home/claudio/.ssh/id_dsa: 
  Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa)
  Identity added: /home/claudio/.ssh/id_ecdsa (/home/claudio/.ssh/id_ecdsa)
  
  Here is the content of my ~/.ssh/

  claudio@Chuck:~$ ls -l .ssh
  total 32
  -rw-r--r-- 1 claudio claudio  726 2011-04-15 23:34 config
  -r 1 claudio claudio  751 2011-04-05 10:35 id_dsa
  -rw-r--r-- 1 claudio claudio  603 2011-04-05 10:34 id_dsa.pub
  -r 1 claudio claudio  444 2011-04-05 10:29 id_ecdsa
  -rw-r--r-- 1 claudio claudio  267 2011-04-05 10:23 id_ecdsa.pub
  -rw--- 1 claudio claudio 6402 2011-04-19 18:04 known_hosts
  -rw-r--r-- 1 claudio claudio 2760 2011-04-06 17:05 known_hosts.old

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Apr 26 16:27:02 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to natty on 2011-04-03 (23 days ago)

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

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

[Desktop-packages] [Bug 1693006] Re: package gconf2-common (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-23 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

** Information type changed from Private Security to Public

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

Title:
  package gconf2-common (not installed) failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  New

Bug description:
  o desktop fecha e rinicia toda hora

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue May 23 15:43:17 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-23 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common (not installed) 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/debconf/+bug/1693006/+subscriptions

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-yakkety

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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-software/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1692398] Re: Input error can lead to continuous searches

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-yakkety

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

Title:
  Input error can lead to continuous searches

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

Bug description:
  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.

  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'

  Expected result:
  Searches stop after a reasonable time.

  Observed result:
  Searches are continuously generated for each key press.

  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

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

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

[Desktop-packages] [Bug 1692298] Re: firefox hangs using 100% cpu

2017-05-23 Thread Christian Nassau

In my case, the "No Script" add-on might be to blame; disabling it seems
to fix the problem for me.

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

Title:
   firefox hangs using 100% cpu

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox is hanging with no special pattern. It can be loading a saved
  tab, open a new page, using an already opened page. It simply starts
  using 100% cpu and becomes unusable, never coming back (>100 minutes).
  This is random, happening a lot, but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 53.0.2+build1-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ferdez 4504 F pulseaudio
  BuildID: 20170509205820
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun May 21 09:52:36 2017
  DefaultProfileIncompatibleExtensions:
   Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources:
   prefs.js
   user.js
   [Profile]/extensions/inspec...@mozilla.org/defaults/preferences/inspector.js
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-16 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.254 dev wlp13s0  proto static  metric 600 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp13s0  proto kernel  scope link  src 192.168.1.113  
metric 600 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  MostRecentCrashID: bp-964d1e04-1a6d-4531-9dc1-65b032150721
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins: iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=53.0.2/20170509205820 (In use)
   Profile1 - LastVersion=40.0.3/20150826185640 (Out of date)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to yakkety on 2016-10-29 (203 days ago)
  dmi.bios.date: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - 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.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUEE-00C008EP
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

2017-05-23 Thread Matija “hook” Šuklje

I installed 1.8.0 (latest upstream stable) from Debian Sid .deb packages on my 
Kubuntu 17.04 and it solved this issue for me.
 
It might be worth a try if a simple upgrade to 1.8.0 would fix this.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1692398] Re: Input error can lead to continuous searches

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

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

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

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

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

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

Title:
  Input error can lead to continuous searches

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

Bug description:
  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.

  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'

  Expected result:
  Searches stop after a reasonable time.

  Observed result:
  Searches are continuously generated for each key press.

  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

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

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

[Desktop-packages] [Bug 1692398] Re: Input error can lead to continuous searches

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  Input error can lead to continuous searches

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.

  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'

  Expected result:
  Searches stop after a reasonable time.

  Observed result:
  Searches are continuously generated for each key press.

  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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-software/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1692398] Re: Input error can lead to continuous searches

** Changed in: gnome-software (Ubuntu Artful)
   Status: Triaged => Fix Released

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

Title:
  Input error can lead to continuous searches

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  An input error (e.g. a key being continuously pressed) in the gnome-software 
search field can lead to continuous searches being sent via snapd. This is 
beuause there is no limit in this search field.

  [Test Case]
  1. Open GNOME Software
  2. Click search button
  3. Continuously press and release 't'

  Expected result:
  Searches stop after a reasonable time.

  Observed result:
  Searches are continuously generated for each key press.

  [Regression potential]
  Low. The field is now limited to 100 characters and searches stop after this 
limit.

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

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

[Desktop-packages] [Bug 1354800] Re: Please merge package names and descriptions from Debian

This merge was done for Ubuntu 17.04.

** Changed in: system-config-printer (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please merge package names and descriptions from Debian

Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  kdeadmin (4:4.9.80-0ubuntu1) raring; urgency=low

    * Drop the system-config-printer-kde package, does not exist anymore

   -- Jonathan Riddell    Mon, 19 Nov 2012 15:50:48
  +

  Source: system-config-printer
  Version: 1.5.0+20140805-0ubuntu3

  system-config-printer-kde no longer exist so there is no need anymore
  for system-config-printer-common and system-config-printer-gnome
  binary packages, please simply use system-config-printer as binary
  package name to be in sync with Debian. Also the package description
  and dependencies should be merged from Debian.

  Thanks,
  Pascal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1354800/+subscriptions

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

[Desktop-packages] [Bug 1693024] Re: can't start JACK with real-time scheduling even when in audio group

2017-05-23 Thread Adam Dingle

This may also be relevant:

https://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime/

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

Title:
  can't start JACK with real-time scheduling even when in audio group

Status in jackd2 package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.04.  I've installed jack2 and have added myself
  to the 'audio' group as suggested at

    http://jackaudio.org/faq/linux_rt_config.html

  But when I start JACK it reports

  Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: 
Operation not permitted)
  Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error

  I am in the 'audio' group in /etc/group:

  adam:~$ grep audio /etc/group
  audio:x:29:pulse,adam
  adam:~$

  (I restarted the machine after adding myself to this group.)

  'ulimit' isn't showing real-time priority privileges for me:

  adam:~$ ulimit -a | grep real
  real-time priority  (-r) 0
  adam:~$

  The file /etc/security/limits.d/audio.conf looks like this:

  ===

  # Provided by the jackd package.
  #
  # Changes to this file will be preserved.
  #
  # If you want to enable/disable realtime permissions, run
  #
  #dpkg-reconfigure -p high jackd

  @audio   -  rtprio 95
  @audio   -  memlockunlimited
  #@audio   -  nice  -19

  ===

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

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

[Desktop-packages] [Bug 1693024] Re: can't start JACK with real-time scheduling even when in audio group

2017-05-23 Thread Adam Dingle

I believe this problem may have to with Ubuntu's recent transition to
systemd.  Apparently systemd completely ignores /etc/security/limits*.


** Description changed:

  I'm running Ubuntu 17.04.  I've installed jack2 and have added myself to
  the 'audio' group as suggested at
  
-   http://jackaudio.org/faq/linux_rt_config.html
+   http://jackaudio.org/faq/linux_rt_config.html
  
  But when I start JACK it reports
  
  Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: 
Operation not permitted)
  Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error
  
  I am in the 'audio' group in /etc/group:
  
  adam:~$ grep audio /etc/group
  audio:x:29:pulse,adam
  adam:~$
  
  (I restarted the machine after adding myself to this group.)
  
  'ulimit' isn't showing real-time priority privileges for me:
  
  adam:~$ ulimit -a | grep real
  real-time priority  (-r) 0
- adam:~$ 
+ adam:~$
  
- The file /etc/security/limits.d looks like this:
+ The file /etc/security/limits.d/audio.conf looks like this:
  
  ===
  
  # Provided by the jackd package.
  #
  # Changes to this file will be preserved.
  #
  # If you want to enable/disable realtime permissions, run
  #
  #dpkg-reconfigure -p high jackd
  
  @audio   -  rtprio 95
  @audio   -  memlockunlimited
  #@audio   -  nice  -19
  
  ===

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

Title:
  can't start JACK with real-time scheduling even when in audio group

Status in jackd2 package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.04.  I've installed jack2 and have added myself
  to the 'audio' group as suggested at

    http://jackaudio.org/faq/linux_rt_config.html

  But when I start JACK it reports

  Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: 
Operation not permitted)
  Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error

  I am in the 'audio' group in /etc/group:

  adam:~$ grep audio /etc/group
  audio:x:29:pulse,adam
  adam:~$

  (I restarted the machine after adding myself to this group.)

  'ulimit' isn't showing real-time priority privileges for me:

  adam:~$ ulimit -a | grep real
  real-time priority  (-r) 0
  adam:~$

  The file /etc/security/limits.d/audio.conf looks like this:

  ===

  # Provided by the jackd package.
  #
  # Changes to this file will be preserved.
  #
  # If you want to enable/disable realtime permissions, run
  #
  #dpkg-reconfigure -p high jackd

  @audio   -  rtprio 95
  @audio   -  memlockunlimited
  #@audio   -  nice  -19

  ===

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

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

[Desktop-packages] [Bug 1693033] [NEW] Please merge system-config-printer with Debian 1.5.9

Public bug reported:

system-config-printer is now being maintained (hopefully?) at
https://github.com/zdohnal/system-config-printer

Debian packaged the latest version from there, but it was done too late
for Ubuntu 17.04. We should do this merge for 17.10.

** Affects: system-config-printer (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: artful upgrade-software-version

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

Title:
  Please merge system-config-printer with Debian 1.5.9

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  system-config-printer is now being maintained (hopefully?) at
  https://github.com/zdohnal/system-config-printer

  Debian packaged the latest version from there, but it was done too
  late for Ubuntu 17.04. We should do this merge for 17.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1693033/+subscriptions

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

[Desktop-packages] [Bug 1693024] [NEW] can't start JACK with real-time scheduling even when in audio group

2017-05-23 Thread Adam Dingle

Public bug reported:

I'm running Ubuntu 17.04.  I've installed jack2 and have added myself to
the 'audio' group as suggested at

  http://jackaudio.org/faq/linux_rt_config.html

But when I start JACK it reports

Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: 
Operation not permitted)
Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error

I am in the 'audio' group in /etc/group:

adam:~$ grep audio /etc/group
audio:x:29:pulse,adam
adam:~$

(I restarted the machine after adding myself to this group.)

'ulimit' isn't showing real-time priority privileges for me:

adam:~$ ulimit -a | grep real
real-time priority  (-r) 0
adam:~$ 

The file /etc/security/limits.d looks like this:

===

# Provided by the jackd package.
#
# Changes to this file will be preserved.
#
# If you want to enable/disable realtime permissions, run
#
#dpkg-reconfigure -p high jackd

@audio   -  rtprio 95
@audio   -  memlockunlimited
#@audio   -  nice  -19

===

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

** Summary changed:

- can't start JACK with real-time schedule even when in audio group
+ can't start JACK with real-time scheduling even when in audio group

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

Title:
  can't start JACK with real-time scheduling even when in audio group

Status in jackd2 package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.04.  I've installed jack2 and have added myself
  to the 'audio' group as suggested at

http://jackaudio.org/faq/linux_rt_config.html

  But when I start JACK it reports

  Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: 
Operation not permitted)
  Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error

  I am in the 'audio' group in /etc/group:

  adam:~$ grep audio /etc/group
  audio:x:29:pulse,adam
  adam:~$

  (I restarted the machine after adding myself to this group.)

  'ulimit' isn't showing real-time priority privileges for me:

  adam:~$ ulimit -a | grep real
  real-time priority  (-r) 0
  adam:~$ 

  The file /etc/security/limits.d looks like this:

  ===

  # Provided by the jackd package.
  #
  # Changes to this file will be preserved.
  #
  # If you want to enable/disable realtime permissions, run
  #
  #dpkg-reconfigure -p high jackd

  @audio   -  rtprio 95
  @audio   -  memlockunlimited
  #@audio   -  nice  -19

  ===

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

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

[Desktop-packages] [Bug 1693021] Re: Need two commits cherry-picked from Mesa main into 16.10

2017-05-23 Thread Sinclair Yeh

Sorry, the title should've been "one commit" rather than "two commits"

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

Title:
  Need two commits cherry-picked from Mesa main into 16.10

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,

  Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10?

  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296

  I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not
  there.

  thanks

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

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

[Desktop-packages] [Bug 1693021] [NEW] Need two commits cherry-picked from Mesa main into 16.10

2017-05-23 Thread Sinclair Yeh

Public bug reported:

Hi,

Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10?

https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296

I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not
there.

thanks

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

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

Title:
  Need two commits cherry-picked from Mesa main into 16.10

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,

  Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10?

  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296

  I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not
  there.

  thanks

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

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

[Desktop-packages] [Bug 1692298] Re: firefox hangs using 100% cpu

2017-05-23 Thread Christian Nassau

I'm seeing similar deadlocks of firefox with 100% cpu usage; this is
happening a lot. I have installed firefox-dbg and started firefox with
"-g" under gdb. When I hit Ctrl-C during a deadlock I get this
backtrace:

(gdb) where
#0  0x7fffe954c546 in js::irregexp::InterpretCode(JSContext*, unsigned char const*, unsigned char const*, unsigned long, 
unsigned long, js::MatchPairs*, unsigned long*) (cx=cx@entry=0x7fffe1b8d000, 
byteCode=byteCode@entry=0x7fff73838000 "\002", chars=0x7fff7bd12000 
";##[{\"type\":\"http://schema|org/WebPage\",\"properties\":{}},{\"type\":\"http://schema|org/Person\",\"properties\":{}},{\"type\":\"http://schema|org/Person\",\"properties\":{}},{\"type\":\"http://schema|org/NewsArticle\""...,
 current=2274, 
current@entry=0, length=length@entry=4327, matches=matches@entry=0x0, 
endIndex=0x7fff4fc0)
at 
/build/firefox-iUv61F/firefox-53.0.2+build1/js/src/irregexp/RegExpInterpreter.cpp:142
#1  0x7fffe93751f5 in js::RegExpShared::execute(JSContext*, 
JS::Handle, unsigned long, js::MatchPairs*, unsigned long*) 
(this=this@entry=0x7fff74bc8900, cx=cx@entry=0x7fffe1b8d000, 
input=input@entry=..., start=start@entry=0, matches=matches@entry=0x0, 
endIndex=endIndex@entry=0x7fff4fc0) at 
/build/firefox-iUv61F/firefox-53.0.2+build1/js/src/vm/RegExpObject.cpp:1175
#2  0x7fffe95b7a7c in ExecuteRegExpImpl (endIndex=0x7fff4fc0, 
matches=0x0, searchIndex=, input=..., re=..., 
res=0x7fffd142ab30, cx=0x7fffe1b8d000) at 
/build/firefox-iUv61F/firefox-53.0.2+build1/js/src/builtin/RegExp.cpp:127
#3  0x7fffe95b7a7c in ExecuteRegExp (staticsUpdate=js::UpdateRegExpStatics, 
endIndex=0x7fff4fc0, matches=0x0, lastIndex=, string=..., 
regexp=..., cx=0x7fffe1b8d000) at 
/build/firefox-iUv61F/firefox-53.0.2+build1/js/src/builtin/RegExp.cpp:971
#4  0x7fffe95b7a7c in js::RegExpTesterRaw(JSContext*, 
JS::Handle, JS::Handle, int, int*) (cx=0x7fffe1b8d000, 
regexp=..., input=..., lastIndex=, endIndex=0x7fff5094)
at 
/build/firefox-iUv61F/firefox-53.0.2+build1/js/src/builtin/RegExp.cpp:1197
#5  0x32f931aa347a in  ()
#6  0x7fffd9600560 in  ()
#7  0x7fff5094 in  ()
#8  0x7fffd1508680 in  ()
#9  0x7fffead51ae0 in js::jit::RegExpTesterRawInfo () at 
/usr/lib/firefox/libxul.so
#10 0x7fffd96718e0 in  ()
#11 0x32f931da5ab0 in  ()
#12 0x3820 in  ()
#13 0x7fffd1508680 in  ()
#14 0x7fff6df9fc40 in  ()
#15 0x in  ()

My guess is that firefox is stuck executing a pretty weird regular
expression:

(gdb) set print elements 0
(gdb) print chars
$5 = (const unsigned char *) 0x7fff7bd12000

[Desktop-packages] [Bug 1692298] Re: firefox hangs using 100% cpu

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

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

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

Title:
   firefox hangs using 100% cpu

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox is hanging with no special pattern. It can be loading a saved
  tab, open a new page, using an already opened page. It simply starts
  using 100% cpu and becomes unusable, never coming back (>100 minutes).
  This is random, happening a lot, but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 53.0.2+build1-0ubuntu0.16.10.2
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ferdez 4504 F pulseaudio
  BuildID: 20170509205820
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun May 21 09:52:36 2017
  DefaultProfileIncompatibleExtensions:
   Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/flashplugin-installer/libflashplayer.so
  DefaultProfilePrefSources:
   prefs.js
   user.js
   [Profile]/extensions/inspec...@mozilla.org/defaults/preferences/inspector.js
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-16 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.254 dev wlp13s0  proto static  metric 600 
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp13s0  proto kernel  scope link  src 192.168.1.113  
metric 600 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  MostRecentCrashID: bp-964d1e04-1a6d-4531-9dc1-65b032150721
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins: iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=53.0.2/20170509205820 (In use)
   Profile1 - LastVersion=40.0.3/20150826185640 (Out of date)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to yakkety on 2016-10-29 (203 days ago)
  dmi.bios.date: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - 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.20:bd10/08/2015:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUEE-00C008EP:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUEE-00C008EP
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1693008] [NEW] Failed update

2017-05-23 Thread JKMore

Public bug reported:

After upgrading to 17.04 I recently experience update failed when I run
the update. I also experience freezing when browsing the internet, It
also failed to send the report if you want to send the report. I can't
even view what the report issues are talkless of sending the report to
the community.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue May 23 14:15:29 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.10.0-19-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.10.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.10.0-21-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.8.0-48-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f840]
InstallationDate: Installed on 2016-10-29 (206 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
MachineType: TOSHIBA Satellite C55-C
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=b8a3138b-6fa7-4b9f-8ab7-1b1b1219e0eb ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2016
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 5.20
dmi.board.name: 06F2
dmi.board.vendor: FF50
dmi.board.version: Type2 - 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.:bvr5.20:bd01/11/2016:svnTOSHIBA:pnSatelliteC55-C:pvrPSCPJU-00R011:rvnFF50:rn06F2:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C55-C
dmi.product.version: PSCPJU-00R011
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.6-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.6-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Tue May 23 14:06:19 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug third-party-packages ubuntu zesty

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

Title:
  Failed update

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to 17.04 I recently experience update failed when I
  run the update. I also experience freezing when browsing the internet,
  It also failed to send the report if you want to send the report. I
  can't even view what the report issues are talkless of sending the
  report to the community.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May 23 14:15:29 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-19-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.8.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f840]
  InstallationDate: Installed on 2016-10-29 (206 days ago)
  InstallationMedia:

[Desktop-packages] [Bug 1660316] Re: apparmor denial of CUPS

2017-05-23 Thread Dag Bjerkeli

Meanwhile I've upgraded the computer to 17.04, but I have not checked
the presence of the bug after the upgrade. I will check tomorrow when I
get access to the computer.

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

Title:
  apparmor denial of CUPS

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printing is enabled when doing sudo aa-complain cupsd

  Here is an extract of /var/log/syslog:

  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
  Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
  Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
  Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
  Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
  Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 
audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 
audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-05-23 Thread Aron Bohl

I'm running on Ubuntu GNOME 17.04 and I'm still affected by this issue.
After connecting to VPN and running a DNS leak test, it still shows my
DNS as my usual ISP.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1660316] Re: apparmor denial of CUPS

2017-05-23 Thread Till Kamppeter

I do not exactly why lpadmin needs this capability, I even do not know
which actions are covered by net_admin. What I know about the LPD
backend is that it accesses the printer through port 515 and it is
possible that the backend accesses the printer via SNMP in addition.

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

Title:
  apparmor denial of CUPS

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printing is enabled when doing sudo aa-complain cupsd

  Here is an extract of /var/log/syslog:

  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
  Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
  Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
  Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
  Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service'
  Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
  Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
  Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
  Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
  Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
  Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
  Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
  Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 
comm="apparmor_parser"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 
audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"
  Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 
audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.2.0-2

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-05-23 Thread Mathieu Trudel-Lapierre

Has anyone tried to make their connections with an even newer version of
Ubuntu and network-manager, such as on 17.04? That would be a very good
test to do (in my experience, it works correctly).

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-05-23 Thread Mathieu Trudel-Lapierre

I don't know why bugs about "DNS on VPN" were being marked as duplicates
of suspend/resume issues in dnsmasq. It's /related/, but definitely not
the same thing at all. I can only apologize that this wasn't handled
correctly, and try to fix things.

One thing to keep in mind however, is that not all premises on this bug
report are correct: what DNS server to use is directly dependent on the
settings used in the VPN connection: whether it should use the VPN for
everything, or just for the network it provides as routed shipped from
the VPN server. Your observations may vary based on what that setting
is.

I think we have enough information already to start working on a
solution, so I'll mark this bug Triaged/In Progress and assign it to
myself. I'm also milestoning it to 17.06; so that it stays on my todo
list for this month and June -- but that doesn't mean that it *will* be
fixed by then, that will depend on how hard it is to fix and ship the
updates where appropriate.

I only have openvpn to work with now, but the actual type of VPN should
not matter. If it changes something, *that* would be another bug (and
then you should make a separate report). If things work for one VPN
plugin, it means NetworkManager is doing what it should.

As soon as there is a proposed fix for this, I'll make it available on a
PPA for testing, even before it lands in -proposed, so as to have more
certainty that the fix works. I'll comment back here when something is
ready.

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

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-17.06

** Also affects: network-manager (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu Yakkety)
   Importance: Undecided => High

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

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

** Changed in: network-manager (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network

[Desktop-packages] [Bug 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked

2017-05-23 Thread Naël

Awesome, thanks for weighting in Kenneth.

I've set the status to "Invalid" (not a bug) for deja-dup since the bug
was in duplicity.

** No longer affects: deja-dup

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  repeatedly asks for encryption password when backing up, even though
  "remember password" is ticked

Status in Duplicity:
  Fix Released
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  I've set deja-dup to back up automatically, and to encrypt files. But it 
never gets far: every few seconds, it brings up a "password needed" window 
somewhere out of sight (behind other windows; but that is another 
problem/feature), even though I've told it to remember the password.
   
  So using this backup software seems entirely impractical; it will never 
finish.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: deja-dup 20.1-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 27 09:50:47 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 883742] Re: Deja Dup keeps asking for password

2017-05-23 Thread Naël

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

** This bug has been marked a duplicate of bug 989750
   repeatedly asks for encryption password when backing up, even though 
"remember password" is ticked

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

Title:
  Deja Dup keeps asking for password

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.10

  The last 2 days whenever an automatic backup runs it asks me for my
  password, which I input. The GUI then says 'preparing backup', before
  asking for the password again. The password I am inputting is correct,
  so I am not sure why the backup is not running

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: deja-dup 20.1-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Oct 30 06:11:29 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/883742/+subscriptions

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

[Desktop-packages] [Bug 1691839] Re: nvidia-graphics-drivers-304 304.135-0ubuntu1 ADT test failure with linux 4.11.0-3.8

2017-05-23 Thread Alberto Milone

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu1 ADT test failure with
  linux 4.11.0-3.8

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/amd64/n/nvidia-graphics-drivers-304/20170517_172947_fd0b4@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/i386/n/nvidia-graphics-drivers-304/20170517_153741_fd0b4@/log.gz

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

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

[Desktop-packages] [Bug 1691841] Re: nvidia-graphics-drivers-340 340.102-0ubuntu3 ADT test failure with linux 4.11.0-3.8

2017-05-23 Thread Alberto Milone

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  nvidia-graphics-drivers-340 340.102-0ubuntu3 ADT test failure with
  linux 4.11.0-3.8

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/amd64/n/nvidia-graphics-drivers-340/20170517_172744_3d553@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/i386/n/nvidia-graphics-drivers-340/20170517_152615_3d553@/log.gz

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

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

[Desktop-packages] [Bug 1691946] Re: package emacs24 24.5+1-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-05-23 Thread Glenn Morris

The actual error is:

  oneliner.el:225:1:Error: Cannot open load file: no such file or directory, poe
  ERROR: install script from oneliner-el package failed

For more information, see

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754892

Try: sudo apt-get purge oneliner-el


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

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

Title:
  package emacs24 24.5+1-6ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in emacs24 package in Ubuntu:
  New

Bug description:
  Please provide the solution

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: emacs24 24.5+1-6ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 19 00:04:51 2017
  DpkgHistoryLog:
   Start-Date: 2017-05-19  00:04:39
   Commandline: apt-get install sysbench
   Requested-By: abhi (1000)
   Install: mysql-common:amd64 (5.7.18-0ubuntu0.16.04.1, automatic), 
libmysqlclient20:amd64 (5.7.18-0ubuntu0.16.04.1, automatic), sysbench:amd64 
(0.4.12-1.1ubuntu1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-22 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: emacs24
  Title: package emacs24 24.5+1-6ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1692915] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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 #1688721, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  >>lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  apt-cache policy slack
  slack:
Installed: 1:0.15.2-9
Candidate: 1:0.15.2-9
Version table:
   *** 1:0.15.2-9 500
  500 http://my.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://my.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
  100 /var/lib/dpkg/status
   
  installed with error

  The following NEW packages will be installed:
slack
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  5 not fully installed or removed.
  Need to get 31.4 kB of archives.
  After this operation, 120 kB of additional disk space will be used.
  Get:1 http://my.archive.ubuntu.com/ubuntu zesty/universe amd64 slack all 
1:0.15.2-9 [31.4 kB]
  Fetched 31.4 kB in 1s (30.6 kB/s)
  Selecting previously unselected package slack.
  (Reading database ... 212370 files and directories currently installed.)
  Preparing to unpack .../slack_1%3a0.15.2-9_all.deb ...
  Unpacking slack (1:0.15.2-9) ...
  Setting up gconf2-common (3.2.6-3ubuntu7) ...
  Setting up libgconf-2-4:amd64 (3.2.6-3ubuntu7) ...
  Processing triggers for man-db (2.7.6.1-2) ...
  Setting up slack (1:0.15.2-9) ...
  Setting up gconf-service (3.2.6-3ubuntu7) ...
  Setting up gconf-service-backend (3.2.6-3ubuntu7) ...
  Setting up gconf2 (3.2.6-3ubuntu7) ...
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  W: APT had planned for dpkg to do more than it reported back (17 vs 21).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue May 23 22:40:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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/gconf/+bug/1692915/+subscriptions

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

[Desktop-packages] [Bug 1692915] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-23 Thread norjuliana

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

Public bug reported:

>>lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

apt-cache policy slack
slack:
  Installed: 1:0.15.2-9
  Candidate: 1:0.15.2-9
  Version table:
 *** 1:0.15.2-9 500
500 http://my.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
500 http://my.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
100 /var/lib/dpkg/status
 
installed with error

The following NEW packages will be installed:
  slack
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
Need to get 31.4 kB of archives.
After this operation, 120 kB of additional disk space will be used.
Get:1 http://my.archive.ubuntu.com/ubuntu zesty/universe amd64 slack all 
1:0.15.2-9 [31.4 kB]
Fetched 31.4 kB in 1s (30.6 kB/s)
Selecting previously unselected package slack.
(Reading database ... 212370 files and directories currently installed.)
Preparing to unpack .../slack_1%3a0.15.2-9_all.deb ...
Unpacking slack (1:0.15.2-9) ...
Setting up gconf2-common (3.2.6-3ubuntu7) ...
Setting up libgconf-2-4:amd64 (3.2.6-3ubuntu7) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up slack (1:0.15.2-9) ...
Setting up gconf-service (3.2.6-3ubuntu7) ...
Setting up gconf-service-backend (3.2.6-3ubuntu7) ...
Setting up gconf2 (3.2.6-3ubuntu7) ...
Processing triggers for libc-bin (2.24-9ubuntu2) ...
W: APT had planned for dpkg to do more than it reported back (17 vs 21).

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Tue May 23 22:40:54 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-21 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  >>lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  apt-cache policy slack
  slack:
Installed: 1:0.15.2-9
Candidate: 1:0.15.2-9
Version table:
   *** 1:0.15.2-9 500
  500 http://my.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://my.archive.ubuntu.com/ubuntu zesty/universe i386 Packages
  100 /var/lib/dpkg/status
   
  installed with error

  The following NEW packages will be installed:
slack
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  5 not fully installed or removed.
  Need to get 31.4 kB of archives.
  After this operation, 120 kB of additional disk space will be used.
  Get:1 http://my.archive.ubuntu.com/ubuntu zesty/universe amd64 slack all 
1:0.15.2-9 [31.4 kB]
  Fetched 31.4 kB in 1s (30.6 kB/s)
  Selecting previously unselected package slack.
  (Reading database ... 212370 files and directories currently installed.)
  Preparing to unpack .../slack_1%3a0.15.2-9_all.deb ...
  Unpacking slack (1:0.15.2-9) ...
  Setting up gconf2-common (3.2.6-3ubuntu7) ...
  Setting up libgconf-2-4:amd64 (3.2.6-3ubuntu7) ...
  Processing triggers for man-db (2.7.6.1-2) ...
  Setting up slack (1:0.15.2-9) ...
  Setting up gconf-service (3.2.6-3ubuntu7) ...
  Setting up gconf-service-backend (3.2.6-3ubuntu7) ...
  Setting up gconf2 (3.2.6-3ubuntu7) ...
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  W: APT had planned for dpkg to do more than it reported back (17 vs 21).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue May 23 22:40:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common

[Desktop-packages] [Bug 1579557] Re: lightdm will not start

2017-05-23 Thread Thomas Schweikle

Same here. "dpkg-reconfigure lightdm" does not help out.
Lightdm seems to be started, but then is terminated because of "respawning to 
fast".

lightdm log:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.22.0, UID=0 PID=2079
[+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf
[+0.00s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from 
/etc/lightdm/lightdm.conf.d/10-xubuntu.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:*], please update this 
configuration
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:*], please update this 
configuration
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Creating display server of type x
[+0.02s] DEBUG: Using VT 7
[+0.02s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.02s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.02s] DEBUG: XServer 0: Writing X server authority to 
/var/run/lightdm/root/:0
[+0.02s] DEBUG: XServer 0: Launching X Server
[+0.02s] DEBUG: Launching process 2087: /usr/bin/X -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.02s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.02s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+0.02s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.73s] DEBUG: Got signal 10 from process 2087
[+0.73s] DEBUG: XServer 0: Got signal from X server :0
[+0.73s] DEBUG: XServer 0: Connecting to XServer :0
[+0.73s] DEBUG: Launching process 2215: /usr/share/lightdm_xrandr
[+0.75s] DEBUG: Process 2215 exited with return value 1
[+0.75s] DEBUG: Seat seat0: Exit status of /usr/share/lightdm_xrandr: 1
[+0.75s] DEBUG: Seat seat0: Stopping display server due to failed setup script
[+0.75s] DEBUG: Sending signal 15 to process 2087
[+1.17s] DEBUG: Process 2087 exited with return value 0
[+1.17s] DEBUG: XServer 0: X server stopped
[+1.17s] DEBUG: Releasing VT 7
[+1.17s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+1.17s] DEBUG: Seat seat0: Display server stopped
[+1.17s] DEBUG: Seat seat0: Stopping session
[+1.17s] DEBUG: Seat seat0: Session stopped
[+1.17s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+1.17s] DEBUG: Seat seat0: Stopping
[+1.17s] DEBUG: Seat seat0: Stopped
[+1.17s] DEBUG: Required seat has stopped
[+1.17s] DEBUG: Stopping display manager
[+1.17s] DEBUG: Display manager stopped
[+1.17s] DEBUG: Stopping daemon
[+1.17s] DEBUG: Exiting with return value 1


And x-0.log:
X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-70-generic x86_64 Ubuntu
Current Operating System: Linux nc404-muc 4.10.0-21-generic #23-Ubuntu SMP Fri 
Apr 28 16:14:22 UTC 2017 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
Build Date: 28 March 2017  06:16:52AM
xorg-server 2:1.19.3-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 23 16:25:05 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
VMware: No 3D enabled (0,

[Desktop-packages] [Bug 1692477] Re: Thunderbird 52.1.1 no longer able to see remotely mounted folders

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

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

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

Title:
  Thunderbird 52.1.1 no longer able to see remotely mounted folders

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Since the upgrade of Thunderbird to 52.1.1 remotely mounted folders no
  longer show up in the attach dialog window.

  
  - What is happening

  In nautilus mount a folder ("Connect to Server") from a remote server
  - smb:// or ssh:// are the two I have tried.

  Start a new email and go to attach a file from the remote folder.  The
  shared folder is not visible in the attach file dialog but is visible
  in nautilus

  
  - What should happen

  In nautilus mount a folder ("Connect to Server") from a remote server
  - smb:// or ssh:// are the two I have tried.

  Start a new email and go to attach a file from the remote folder.  I
  can see the remote folder from the attach file dialog.

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Codename: xenial

  
  $ apt-cache policy thunderbird
  thunderbird:
Installed: 1:52.1.1+build1-0ubuntu0.16.04.1
Candidate: 1:52.1.1+build1-0ubuntu0.16.04.1
Version table:
   *** 1:52.1.1+build1-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:38.6.0+build1-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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

[Desktop-packages] [Bug 971219] Re: Remmina Crashes with when connecting to some RDP hosts

2017-05-23 Thread philthynz

Same issue for me. But only crashing when remmina is a another
workspace. If remmina is running in the same workspace, it doesn't
crash. And I am using RDP under security.

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

Title:
  Remmina Crashes with when connecting to some RDP hosts

Status in freerdp package in Ubuntu:
  Confirmed

Bug description:
  When connecting to some RDP Hosts Remmina will crash every time they
  are 2008 server hosts but not all 2008 server hosts have the problem.

  [ 2375.493642] remmina[7647]: segfault at 10018 ip 7f0db307718c sp 
7f0da4c836f0 error 6 in libfreerdp-core.so.1.0.1[7f0db306+42000]
  [ 2509.507670] remmina[7727]: segfault at 10018 ip 7fe454b6b18c sp 
7fe4467b36f0 error 6 in libfreerdp-core.so.1.0.1[7fe454b54000+42000]

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: remmina 1.0.0-1ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Mon Apr  2 11:24:51 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1692878] [NEW] package libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2 failed to install/upgrade: Extrahierte Daten für »./usr/lib/libreoffice/program/libswlo.so« können nicht

2017-05-23 Thread Albo956

Public bug reported:

I constantly get an error message, i.e. system error and it points to
libreoffice-writer. Since I am new to this forum, I am not quite sure,
that this is really the problem.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu May 18 16:19:47 2017
ErrorMessage: Extrahierte Daten für »./usr/lib/libreoffice/program/libswlo.so« 
können nicht nach »/usr/lib/libreoffice/program/libswlo.so.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
InstallationDate: Installed on 2017-04-05 (48 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libreoffice
Title: package libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2 failed to 
install/upgrade: Extrahierte Daten für 
»./usr/lib/libreoffice/program/libswlo.so« können nicht nach 
»/usr/lib/libreoffice/program/libswlo.so.dpkg-new« kopiert werden: Unerwartetes 
Ende der Datei oder des Datenstroms
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2 failed to
  install/upgrade: Extrahierte Daten für
  »./usr/lib/libreoffice/program/libswlo.so« können nicht nach
  »/usr/lib/libreoffice/program/libswlo.so.dpkg-new« kopiert werden:
  Unerwartetes Ende der Datei oder des Datenstroms

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I constantly get an error message, i.e. system error and it points to
  libreoffice-writer. Since I am new to this forum, I am not quite sure,
  that this is really the problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 18 16:19:47 2017
  ErrorMessage: Extrahierte Daten für 
»./usr/lib/libreoffice/program/libswlo.so« können nicht nach 
»/usr/lib/libreoffice/program/libswlo.so.dpkg-new« kopiert werden: Unerwartetes 
Ende der Datei oder des Datenstroms
  InstallationDate: Installed on 2017-04-05 (48 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libreoffice
  Title: package libreoffice-writer 1:5.1.6~rc2-0ubuntu1~xenial2 failed to 
install/upgrade: Extrahierte Daten für 
»./usr/lib/libreoffice/program/libswlo.so« können nicht nach 
»/usr/lib/libreoffice/program/libswlo.so.dpkg-new« kopiert werden: Unerwartetes 
Ende der Datei oder des Datenstroms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1690706] Re: Tests are not being run

2017-05-23 Thread Iain Lane

It occurs to me that you might be able to do something like

  override_dh_auto_test:
  dbus-run-session -- xvfb-run -a sh -c 
'DBUS_SYSTEM_BUS_ADDRESS=$$DBUS_SESSION_BUS_ADDRESS 
XDG_RUNTIME_DIR=$(CURDIR)/debian/tmp-xdg-runtime-dir dh_auto_test'

That'll probably fail in the same was as it did for me above, but I
reckon you'd be able to get a build-time test going like that.

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

Title:
  Tests are not being run

Status in colord-gtk:
  New
Status in colord-gtk package in Ubuntu:
  New

Bug description:
  The issue of the tests not being run was raised at both MIRs for this
  package LP: #1282372 and LP: #1685411

  I tried to enable the test using dh_auto_test but I still couldn't get
  it to work. I'm attaching the patch I used for the packaging and the
  full build log.

  https://github.com/hughsie/colord-gtk/blob/master/libcolord-gtk/cd-
  self-test.c

  Build Log Excerpt
  =
  make[5]: Entering directory '/<>/libcolord-gtk'
  Activating service name='org.a11y.Bus'

  (process:11432): dconf-CRITICAL **: unable to create directory
  '/run/user/1000/dconf': Permission denied.  dconf will not work
  properly.

  (process:11432): dconf-CRITICAL **: unable to create directory
  '/run/user/1000/dconf': Permission denied.  dconf will not work
  properly.

  (process:11432): dconf-CRITICAL **: unable to create directory
  '/run/user/1000/dconf': Permission denied.  dconf will not work
  properly.

  (process:11432): dconf-CRITICAL **: unable to create directory
  '/run/user/1000/dconf': Permission denied.  dconf will not work
  properly.

  (process:11432): dconf-CRITICAL **: unable to create directory 
'/run/user/1000/dconf': Permission denied.  dconf will not work properly.
  Successfully activated service 'org.a11y.Bus'

  (process:11432): dconf-CRITICAL **: unable to create directory 
'/run/user/1000/dconf': Permission denied.  dconf will not work properly.
  Activating service name='org.a11y.atspi.Registry'
  Successfully activated service 'org.a11y.atspi.Registry'
  SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  ../test-driver: line 107: 11413 Aborted (core dumped) "$@" > 
$log_file 2>&1
  FAIL: cd-self-test
  =
     colord-gtk 0.1.26: libcolord-gtk/test-suite.log
  =

  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: cd-self-test
  ==

  /colord/window: Gtk-Message: GtkDialog mapped without a transient parent. 
This is discouraged.
  **
  libcolord-gtk:ERROR:cd-self-test.c:45:cd_window_get_profile_cb: assertion 
failed (error == NULL): failed to connect to colord: Could not connect: No such 
file or directory (cd_window_error, 0)
  FAIL cd-self-test (exit status: 134)

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

This bug was fixed in the package gnome-software - 3.24.3-0ubuntu3

---
gnome-software (3.24.3-0ubuntu3) artful; urgency=medium

  * debian/patches/0006-Add-an-APT-plugin.patch:
- Handle multiple debconf connections (LP: #1688721)

 -- Robert Ancell   Tue, 23 May 2017
21:28:12 +1200

** Changed in: gnome-software (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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-software/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

2017-05-23 Thread Matija “hook” Šuklje

Until this gets fixed, how about at least providing 1.2.2 or
1.1.93-0ubuntu4 as a force downgrade for 17.04 users that need VPN to
work properly?

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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-software/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

Cause is due to there being multiple debconf connections when gconf-
common is configured (all of which close without any content being
sent). The gnome-software debconf code only handled the first
connection.

** Changed in: gnome-software (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Zesty)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Yakkety)
   Status: New => Fix Committed

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

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

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

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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-software/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1691032] Re: Some PCs still turn off the backlight by zero brightness even when the maximum brightness level is less than 100

2017-05-23 Thread Will Cooke

Added to Trello: https://trello.com/c/DdHQRncy/20-bug-1691032-some-pcs-
still-turn-off-the-backlight-by-zero-brightness-even-when-the-maximum-
brightness-level-is-less-than-100

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

Title:
  Some PCs still turn off the backlight by zero brightness even when the
  maximum brightness level is less than 100

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  New
Status in Unity Settings Daemon:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  The minimum brightness of the laptop screen panel may not be realistic
  sometimes especially when having a problematic screen panel.

  For example, Dell Precision 5720 AIO only has 9 levels in
  /sys/class/backlight/intel_backlight/max_brightness because the wrong
  settings in VBIOS. It is an all-in-one desktop PC and there is no
  brightness hotkey to control the backlight. When we set 0 to
  /sys/class/backlight/intel_backlight/brightness, it turns off the
  panel's backlight and there is no way to brightness up the backlight
  again so we can only avoid using 0 as the minimum backlight level.

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

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-23 Thread Jean-Baptiste Lallement

** Description changed:

  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation
  
- = Expected result = 
+ = Expected result =
  Chrome installs correctly
  
  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst
  
  ucf /usr/share/gconf/default.path /etc/gconf/2/path
  
+ 
+ Record on errors.ubuntu.com
+ https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f
  
  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.
  
  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gnome-software package in Ubuntu:
  New
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gnome-software source package in Zesty:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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-software/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

** No longer affects: gconf (Ubuntu)

** No longer affects: gconf (Ubuntu Xenial)

** No longer affects: gconf (Ubuntu Yakkety)

** No longer affects: gconf (Ubuntu Zesty)

** No longer affects: gconf (Ubuntu Artful)

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gnome-software package in Ubuntu:
  New
Status in gnome-software source package in Xenial:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gnome-software source package in Zesty:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result =
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path

  
  Record on errors.ubuntu.com
  https://errors.ubuntu.com/problem/95c5d509e333a0e080eaf9e58e755a510e0c9c0f

  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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-software/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2017-05-23 Thread Jean-Baptiste Lallement

I reproduced the same defect on Artful. Also while installing updates
the libpam-systemd also failed to install with a similar trace.

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in gconf source package in Xenial:
  New
Status in gnome-software source package in Xenial:
  New
Status in gconf source package in Yakkety:
  New
Status in gnome-software source package in Yakkety:
  New
Status in gconf source package in Zesty:
  New
Status in gnome-software source package in Zesty:
  New
Status in gconf source package in Artful:
  New
Status in gnome-software source package in Artful:
  New

Bug description:
  = Test Case =
  1. Download the debian package of Chrome from google
  2. Open nautilus and double-click on the file to launch ubuntu software
  3. Install the package and proceed with the installation

  = Expected result = 
  Chrome installs correctly

  = Actual result =
  The installation hangs on the following command in gconf2-common.postinst

  ucf /usr/share/gconf/default.path /etc/gconf/2/path


  = Original Report =
  I received this error when trying to install local file 
google-chrome-stable.deb version 58.0.3029.96-1.
  This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. 
Other times, the installation process just hangs at some percentage. I am 
testing this gnome-software version due to Bug (LP: #1672424).
  The same file was successfully installed with gdebi.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  6 13:56:26 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 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/gconf/+bug/1688721/+subscriptions

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

[Desktop-packages] [Bug 1110498] Re: [raring] GNOME System Monitor leaks memory

2017-05-23 Thread Bug Watch Updater

** Changed in: gnome-system-monitor
   Status: Confirmed => Fix Released

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

Title:
  [raring] GNOME System Monitor leaks memory

Status in Gnome System Monitor:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  Triaged

Bug description:
  GNOME System Monitor leaks memory in Ubuntu 13.04 Raring Ringtail,
  here's a screenshot with the memory usage after about 2-3 hours:
  http://i.imgur.com/ot5Q6ZG.png

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-system-monitor 3.6.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Wed Jan 30 17:11:59 2013
  InstallationDate: Installed on 2012-12-30 (31 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to raring on 2013-01-12 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/1110498/+subscriptions

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

[Desktop-packages] [Bug 1691032] Re: Some PCs still turn off the backlight by zero brightness even when the maximum brightness level is less than 100

2017-05-23 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  Some PCs still turn off the backlight by zero brightness even when the
  maximum brightness level is less than 100

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  New
Status in Unity Settings Daemon:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  The minimum brightness of the laptop screen panel may not be realistic
  sometimes especially when having a problematic screen panel.

  For example, Dell Precision 5720 AIO only has 9 levels in
  /sys/class/backlight/intel_backlight/max_brightness because the wrong
  settings in VBIOS. It is an all-in-one desktop PC and there is no
  brightness hotkey to control the backlight. When we set 0 to
  /sys/class/backlight/intel_backlight/brightness, it turns off the
  panel's backlight and there is no way to brightness up the backlight
  again so we can only avoid using 0 as the minimum backlight level.

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

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

[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates