date:20170523

** 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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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:

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

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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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/~touch-packages
Post to :

[Touch-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 Ubuntu
Touch seeded packages, which is

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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

[Touch-packages] [Bug 1594293] Re: Polari theming issues under Ubuntu

** Branch linked: lp:~3v1n0/ubuntu-themes/titlebar-separator-theme

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Critical => Medium

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1594293

Title:
  Polari theming issues under Ubuntu

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  1) Ubuntu 16.04 64bits Unity
  2) Polari 3.18.1
  3) Polari and Ambiance/Radiance theme should match perfectly
  4) Instead, the interface is glitched.

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

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

[Touch-packages] [Bug 1690194] Re: Tweak Tool headerbar has extra lines with Ambiance

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

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1690194

Title:
  Tweak Tool headerbar has extra lines with Ambiance

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  light-themes 16.10+17.10.20170504-0ubuntu2

  Screenshots attached with both Ambiance and Adwaita (for comparison).

  1. Tweak Tool has extra white vertical lines in its headerbar with Ambiance.
  2. It looks like Adwaita does have a single line there but it is aligned with 
the left sidebar.
  3. If you look really closely, you can see an extra gutter border around the 
headerbar.

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

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

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

2017-05-23 Thread Jeremy Bicha

** 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 Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu-qt 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1582992] Re: broken apport hook: TypeError: Can't convert 'bytes' object to str implicitly

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1582992

Title:
  broken apport hook: TypeError: Can't convert 'bytes' object to str
  implicitly

Status in apport package in Ubuntu:
  Expired
Status in libvirt package in Ubuntu:
  Invalid

Bug description:
  The apport hooks appear broken:

  # ubuntu-bug libvirt-bin
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ERROR: hook /usr/share/apport/package-hooks/source_libvirt.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
  TypeError: add_info() takes 1 positional argument but 2 were given

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 202, in 
_run_hook
  symb['add_info'](report)
File "/usr/share/apport/package-hooks/source_libvirt.py", line 21, in 
add_info
  'libvirt-.*'])
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 716, in 
attach_mac_events
  for match in re.findall(aa_re, report.get('KernLog', '') + 
report.get('AuditLog', '')):
  TypeError: Can't convert 'bytes' object to str implicitly

  
  Don't worry about the Wnck thing, that's bug 1580412.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libvirt-bin 1.3.1-1ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue May 17 22:02:30 2016
  InstallationDate: Installed on 2012-10-18 (1307 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=rxvt-unicode
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libvirt
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2016-04-30T00:20:19.958268

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

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

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1692925] Re: Dark button border in Nautilus CSD with Radiance theme

** Branch linked: lp:~3v1n0/ubuntu-themes/radiance-headerbar-buttons-fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1692925

Title:
  Dark button border in Nautilus CSD with Radiance theme

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 17.04
  Release:17.04

  $ apt-cache policy light-themes
  light-themes:
Installed: 16.10+17.04.20170406-0ubuntu1
Candidate: 16.10+17.04.20170406-0ubuntu1
Version table:
   *** 16.10+17.04.20170406-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  
  As in the attached picture, the button borders in Nautilus look too dark for 
Radiance theme

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: light-themes 16.10+17.04.20170406-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 23 17:03:30 2017
  InstallationDate: Installed on 2017-04-20 (33 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692925] Re: Dark button border in Nautilus CSD with Radiance theme

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1692925

Title:
  Dark button border in Nautilus CSD with Radiance theme

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 17.04
  Release:17.04

  $ apt-cache policy light-themes
  light-themes:
Installed: 16.10+17.04.20170406-0ubuntu1
Candidate: 16.10+17.04.20170406-0ubuntu1
Version table:
   *** 16.10+17.04.20170406-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  
  As in the attached picture, the button borders in Nautilus look too dark for 
Radiance theme

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: light-themes 16.10+17.04.20170406-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 23 17:03:30 2017
  InstallationDate: Installed on 2017-04-20 (33 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1690966] Re: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-themes (Ubuntu)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1690966

Title:
  Gnome Shell elements (power menu, launcher etc) are the wrong colour
  when using Ambiance (wrong grey, and blue highlights)

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In artful, Gnome Shell elements (power menu, launcher etc) are the
  wrong colour when using Ambiance (wrong grey, and blue highlights)

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

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

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1693095] [NEW] package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

2017-05-23 Thread matthew

Public bug reported:

i was install os updates from the gui installer.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: bsdutils 1:2.28.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Tue May 23 20:42:55 2017
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-21 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.3
SourcePackage: util-linux
Title: package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1693095

Title:
  package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in util-linux package in Ubuntu:
  New

Bug description:
  i was install os updates from the gui installer.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bsdutils 1:2.28.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue May 23 20:42:55 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-21 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: util-linux
  Title: package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-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 configuration

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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to bluez 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1692925] Re: Weird button border in Nautilus with Radiance theme

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- Weird button border in Nautilus with Radiance theme
+ Dark button border in Nautilus CSD with Radiance theme

** Tags added: visual-quality

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1692925

Title:
  Dark button border in Nautilus CSD with Radiance theme

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 17.04
  Release:17.04

  $ apt-cache policy light-themes
  light-themes:
Installed: 16.10+17.04.20170406-0ubuntu1
Candidate: 16.10+17.04.20170406-0ubuntu1
Version table:
   *** 16.10+17.04.20170406-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  
  As in the attached picture, the button borders in Nautilus look too dark for 
Radiance theme

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: light-themes 16.10+17.04.20170406-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 23 17:03:30 2017
  InstallationDate: Installed on 2017-04-20 (33 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

2017-05-23 Thread Tyler Hicks

I've requested a CVE from MITRE for this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1621396

Title:
  systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Yakkety:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed

Bug description:
  This is one of background errors that happens without any active app being 
involved.
  For the records, I had open: Firefox, Slack, Franz and the Terminal

  [Testcase]
  Notice the dropoff rate of the crash report on errors:

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

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep  8 09:33:55 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1189 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago)
  UserGroups:

  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1693056] [NEW] do-release-upgrade hangs at The user 'syslog' is already a member of 'adm' every single time

2017-05-23 Thread amar

Public bug reported:

Uuntu 15.10

> $ sudo apt-cache policy rsyslog

> rsyslog:
>   Installed: 8.12.0-1ubuntu2
>   Candidate: 8.12.0-1ubuntu2
>   Version table:
>  *** 8.12.0-1ubuntu2 0
> 500 http://ubuntu-archive.mirror.serveriai.lt/ubuntu/ wily/main amd64 
> Packages
> 100 /var/lib/dpkg/status


Whenever I try to run any command that is to reinstall/fix rsylog or try to 
upgrade my Ubuntu server (by running `do-release-upgrade`) it ends in:

> Reading cache
> 
> Checking package manager
> 
> Setting up rsyslog (8.12.0-1ubuntu2)  ...

> The user 'syslog' is already a member of 'adm'.

Because of this I am locked on **Ubuntu 15.10**.

**Note**: I started getting this error after I upgraded from `15.04`
when system was setting up after upgrade to `15.10`. I was asked to
choose version and it said `N` for default or existing version and I
went for it.

What I expect: To peacefully upgrade my VPS Ubuntu version to 16.04.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1693056

Title:
   do-release-upgrade hangs at The user 'syslog' is already a member of
  'adm' every single time

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Uuntu 15.10

  > $ sudo apt-cache policy rsyslog

  > rsyslog:
  >   Installed: 8.12.0-1ubuntu2
  >   Candidate: 8.12.0-1ubuntu2
  >   Version table:
  >  *** 8.12.0-1ubuntu2 0
  > 500 http://ubuntu-archive.mirror.serveriai.lt/ubuntu/ wily/main 
amd64 Packages
  > 100 /var/lib/dpkg/status

  
  Whenever I try to run any command that is to reinstall/fix rsylog or try to 
upgrade my Ubuntu server (by running `do-release-upgrade`) it ends in:

  > Reading cache
  > 
  > Checking package manager
  > 
  > Setting up rsyslog (8.12.0-1ubuntu2)  ...

  > The user 'syslog' is already a member of 'adm'.

  Because of this I am locked on **Ubuntu 15.10**.

  **Note**: I started getting this error after I upgraded from `15.04`
  when system was setting up after upgrade to `15.10`. I was asked to
  choose version and it said `N` for default or existing version and I
  went for it.

  What I expect: To peacefully upgrade my VPS Ubuntu version to 16.04.

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

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

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1417037] Re: Upgrade to 7.4.4-1ubuntu2.5 hangs

2017-05-23 Thread amar

It always gets stuck on

> The user `syslog' is already a member of `adm'.

No matter what.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1417037

Title:
  Upgrade to 7.4.4-1ubuntu2.5 hangs

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  I've just ran an update+dist-upgrade which pulled 7.4.4-1ubuntu2.5.
  It's sat there doing nothing. CTRL+C won't kill it. Htop shows that
  the last process to be created is "stop rsyslog" which follows
  "invoke-rc.d rsyslog restart".

  dpkg.log:

  2015-02-02 09:39:10 configure rsyslog:amd64 7.4.4-1ubuntu2.5 
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5
  2015-02-02 09:39:10 status half-configured rsyslog:amd64 7.4.4-1ubuntu2.5

  I have KILLed "stop rsyslog" which then moves on to "start rsyslog"
  which I have also had to KILL.

  Setting up rsyslog (7.4.4-1ubuntu2.5) ...
  The user `syslog' is already a member of `adm'.
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd

  Terminated
  Terminated
  invoke-rc.d: initscript rsyslog, action "restart" failed.
  dpkg: error processing package rsyslog (--configure):
   subprocess installed post-installation script returned error exit status 143
  Setting up linux-image-virtual-lts-utopic (3.16.0.30.23) ...
  Setting up linux-libc-dev:amd64 (3.13.0-45.74) ...
  Setting up python3-software-properties (0.92.37.3) ...
  Setting up software-properties-common (0.92.37.3) ...
  Errors were encountered while processing:
   rsyslog
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  W: Operation was interrupted before it could finish

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.16.0-29.39~14.04.1-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Feb  2 09:43:26 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1664846] Re: [Wishlist] Support for teaming driver

2017-05-23 Thread Steve Langasek

I guess lack of ifupdown support is worked around with
{pre,post}-{up,down} scripts.

The first thing to do is figure out whether / how this needs to be
represented in the network yaml.  Is there a reason to treat this as a
different kind/class of network config than a bond using the bonding
driver?  Or should the choice of bonding driver (bonding vs. teaming) be
a decision made at a completely different level than netplan?

Once that's determined, we would need to work out how this can be
represented in the networkd renderer.  Opening a task on systemd for
this.

** Changed in: netplan
   Status: Triaged => Incomplete

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1664846

Title:
  [Wishlist] Support for teaming driver

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  The MAAS team is supporting a customer who is using the 'teaming'
  driver rather than the 'bonding' driver. This is essentially a bonding
  driver which also delivers some additional features, and has
  additional userspace runtime control.

  Netplan should allow for bonds to be configured with the teaming
  driver in addition to the bonding driver.

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

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

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to debconf 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded packages, which is subscribed to debconf 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1689833] Re: OpenVPN server does not start properly on boot

Thank you for reporting this bug. I will add it to the server team
backlog, as it does appear to be a real issue.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1689833

Title:
  OpenVPN server does not start properly on boot

Status in openvpn package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  OpenVPN intermittently fails to bind to local address during boot on
  Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does
  not.

  /var/log/openvpn.log
  Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] 
[LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb  2 2016
  Wed May 10 15:42:02 2017 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 
2.08
  Wed May 10 15:42:02 2017 Diffie-Hellman initialized with 2048 bit key
  Wed May 10 15:42:02 2017 Control Channel Authentication: using 
'./easy-rsa/keys/ta.key' as a OpenVPN static key file
  Wed May 10 15:42:02 2017 Outgoing Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:02 2017 Incoming Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:02 2017 Socket Buffers: R=[212992->212992] S=[212992->212992]
  Wed May 10 15:42:02 2017 TCP/UDP: Socket bind failed on local address 
[AF_INET]192.168.4.254:1194: Cannot assign requested address
  Wed May 10 15:42:02 2017 Exiting due to fatal error

  In case it does not start, running 'sudo service openvpn start' fixes
  that problem.

  /var/log/openvpn.log
  Wed May 10 15:42:43 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] 
[LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb  2 2016
  Wed May 10 15:42:43 2017 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 
2.08
  Wed May 10 15:42:43 2017 Diffie-Hellman initialized with 2048 bit key
  Wed May 10 15:42:43 2017 Control Channel Authentication: using 
'./easy-rsa/keys/ta.key' as a OpenVPN static key file
  Wed May 10 15:42:43 2017 Outgoing Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:43 2017 Incoming Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:43 2017 Socket Buffers: R=[212992->212992] S=[212992->212992]
  Wed May 10 15:42:43 2017 ROUTE_GATEWAY 192.168.4.1/255.255.255.0 IFACE=ens4 
HWADDR=52:54:00:f0:26:0c
  Wed May 10 15:42:43 2017 TUN/TAP device tun0 opened
  Wed May 10 15:42:43 2017 TUN/TAP TX queue length set to 100
  Wed May 10 15:42:43 2017 do_ifconfig, tt->ipv6=0, 
tt->did_ifconfig_ipv6_setup=0
  Wed May 10 15:42:43 2017 /sbin/ip link set dev tun0 up mtu 1500
  Wed May 10 15:42:43 2017 /sbin/ip addr add dev tun0 local 172.16.1.1 peer 
172.16.1.2
  Wed May 10 15:42:43 2017 /sbin/ip route add 172.16.1.0/24 via 172.16.1.2
  Wed May 10 15:42:43 2017 GID set to nogroup
  Wed May 10 15:42:43 2017 UID set to nobody
  Wed May 10 15:42:43 2017 UDPv4 link local (bound): [AF_INET]192.168.4.254:1194
  Wed May 10 15:42:43 2017 UDPv4 link remote: [undef]
  Wed May 10 15:42:43 2017 MULTI: multi_init called, r=256 v=256
  Wed May 10 15:42:43 2017 IFCONFIG POOL: base=172.16.1.4 size=62, ipv6=0
  Wed May 10 15:42:43 2017 IFCONFIG POOL LIST
  Wed May 10 15:42:43 2017 Initialization Sequence Completed

  My guess is that systemd starts OpenVPN too early before the network
  is brought up sufficiently. Running 'sudo systemctl edit --full
  openvpn' and adding 'Wants=network-online.target' does not change that
  behaviour.

  user@server:~$ sudo systemd-analyze critical-chain
  graphical.target @2.160s
  └─multi-user.target @2.159s
    └─ntp.service @2.054s +104ms
  └─remote-fs.target @2.052s
    └─remote-fs-pre.target @2.052s
  └─open-iscsi.service @1.993s +57ms
    └─iscsid.service @1.942s +47ms
  └─network-online.target @1.941s
    └─network.target @1.929s
  └─networking.service @1.793s +134ms
    └─apparmor.service @1.140s +395ms
  └─local-fs.target @1.140s
    └─local-fs-pre.target @1.139s
  └─lvm2-monitor.service @602ms +536ms
    └─lvm2-lvmetad.service @773ms
  └─systemd-journald.socket @574ms
    └─-.slice @500ms

  The boot time is quite short. Clean install with the additional
  packages ntp and openssh-server. This happens both on bare metal and
  as a Virtual Machine (KVM) as well.

  /etc/openvpn/server.conf
  local 192.168.4.254
  port 1194
  proto udp
  dev tun
  ca ./easy-rsa/keys/ca.crt
  cert ./easy-rsa/keys/crt.crt
  key ./easy-rsa/keys/key.key
  dh ./easy-rsa/keys/dh2048.pem
  tls-auth ./easy-rsa/keys/ta.key 0
  server 172.16.1.0 255.255.255.0

[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1692981

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
  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
  AptOrdering:
   libssl1.0.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:47:55 2017
  DuplicateSignature:
   package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
   dpkg: error processing package libssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-15 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692869] Re: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1692869

Title:
  package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  PEDIU PARA ATUALIZAR A VERSÃO DO UBUNTU E MEU COMPUTADOR NÃO INICIA.
  QUANDO VOU PARA A VERSÃO DE FÁBRICA, ELE PEDE PARA APAGAR TUDO O QUE
  TENHO SALVO NELE... MUITO CHATO ISSO.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-79-generic 4.4.0-79.100
  ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moema  2203 F pulseaudio
   /dev/snd/controlC0:  moema  2203 F pulseaudio
  Date: Sun May 21 22:33:00 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d0bb8c75-db9d-4561-9aa7-47a604ccabc5
  InstallationDate: Installed on 2016-07-27 (299 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=d3e14fc3-5335-4916-937a-726db739d94a ro quiet splash radeon.modeset=0 
nouveau.modeset=0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  StagingDrivers: rts5139
  Title: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (1 days ago)
  dmi.bios.date: 05/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/08/2016:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1692869/+subscriptions

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

[Touch-packages] [Bug 1692869] Re: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

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.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1692869

Title:
  package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  PEDIU PARA ATUALIZAR A VERSÃO DO UBUNTU E MEU COMPUTADOR NÃO INICIA.
  QUANDO VOU PARA A VERSÃO DE FÁBRICA, ELE PEDE PARA APAGAR TUDO O QUE
  TENHO SALVO NELE... MUITO CHATO ISSO.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-79-generic 4.4.0-79.100
  ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moema  2203 F pulseaudio
   /dev/snd/controlC0:  moema  2203 F pulseaudio
  Date: Sun May 21 22:33:00 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d0bb8c75-db9d-4561-9aa7-47a604ccabc5
  InstallationDate: Installed on 2016-07-27 (299 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=d3e14fc3-5335-4916-937a-726db739d94a ro quiet splash radeon.modeset=0 
nouveau.modeset=0
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  StagingDrivers: rts5139
  Title: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (1 days ago)
  dmi.bios.date: 05/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/08/2016:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1692869/+subscriptions

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

[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

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.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1692981

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
  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
  AptOrdering:
   libssl1.0.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:47:55 2017
  DuplicateSignature:
   package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
   dpkg: error processing package libssl-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-15 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689144] Re: package libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado

Translated from DpkgTerminalLog:

Preparing to unpack ... / libnss3_2% 3a3.28.4-0ubuntu0.17.04.1_amd64.deb ...
Unpacking libnss3: amd64 (2: 3.28.4-0ubuntu0.17.04.1) about (2: 
3.26.2-1ubuntu1) ...
Preparing to unpack ... / libxslt1.1_1.1.29-2ubuntu0.1_amd64.deb ...
Unpacking libxslt1.1: amd64 (1.1.29-2ubuntu0.1) on (1.1.29-2) ...
Dpkg: error processing package libnspr4: amd64 (--configure):
 The package is in a bad state of inconsistency; Should
 Reinstall it before attempting to configure it.
Configuring libxslt1.1: amd64 (1.1.29-2ubuntu0.1) ...
Processing 'triggers' for libc-bin (2.24-9ubuntu2) ...
/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libplc4.so is not a symbolic link

/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libnspr4.so is not a
symbolic link

/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libplds4.so is not a
symbolic link

Dpkg: problems with dependencies prevent the configuration of libnss3: amd64:
 Libnss3: amd64 depends on libnspr4 (> = 2: 4.12); However:
  Package libnspr4: amd64 is not configured yet.

Dpkg: error processing package libnss3: amd64 (--configure):
 Dependency problems - leaving unconfigured

I believe your system is in a very inconsistent state and am unable to
reproduce this. As far as I can tell, there is no bug in nss, but when
libnspr4 is installed, issues are seen. Please manually try and
reinstall libnspr4 and see if the issues go away.

** Changed in: nss (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1689144

Title:
  package libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in nss package in Ubuntu:
  Incomplete

Bug description:
  Não sei muito bem somente que o sistema pediu para relatar para os
  desenvolvedores

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1
  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:
   libnss3:amd64: Install
   libxslt1.1:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun May  7 12:49:50 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2017-05-06 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: nss
  Title: package libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1689204] Re: dpkg: error processing archive /var/cache/apt/archives/init-system-helpers_1.29ubuntu4_all.deb (--unpack): trying to overwrite '/usr/sbin/invoke-rc.d', which is also

I am unable to reproduce this issue. Per the changelog, sysv-rc (from
src:sysvinit) dropped the invoke.rc bits in 2.88dsf-59.3ubuntu1:

sysvinit (2.88dsf-59.3ubuntu1) xenial; urgency=low

  * Dropped various changes for invoke.rc which has moved to
init-system-helpers.


# apt install --reinstall sysv-rc init-system-helpers
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 15 not upgraded.
Need to get 50.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 sysv-rc all 
2.88dsf-59.3ubuntu2 [18.2 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
init-system-helpers all 1.29ubuntu4 [32.3 kB]
Fetched 50.5 kB in 0s (61.0 kB/s)   
Preconfiguring packages ...
(Reading database ... 25504 files and directories currently installed.)
Preparing to unpack .../init-system-helpers_1.29ubuntu4_all.deb ...
Unpacking init-system-helpers (1.29ubuntu4) over (1.29ubuntu4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up init-system-helpers (1.29ubuntu4) ...
(Reading database ... 25504 files and directories currently installed.)
Preparing to unpack .../sysv-rc_2.88dsf-59.3ubuntu2_all.deb ...
Unpacking sysv-rc (2.88dsf-59.3ubuntu2) over (2.88dsf-59.3ubuntu2) ...
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up sysv-rc (2.88dsf-59.3ubuntu2) ...

and dpkg agrees that sysv-rc no longer contains any invoke-rc
references:

# dpkg -L sysv-rc
/.
/etc
/etc/rc0.d
/etc/rc0.d/README
/etc/init.d
/etc/init.d/rcS
/etc/init.d/README
/etc/init.d/rc
/etc/rc3.d
/etc/rc3.d/README
/etc/rc1.d
/etc/rc1.d/README
/etc/rcS.d
/etc/rcS.d/README
/etc/rc2.d
/etc/rc2.d/README
/etc/rc6.d
/etc/rc6.d/README
/etc/rc5.d
/etc/rc5.d/README
/etc/rc4.d
/etc/rc4.d/README
/var
/var/lib
/var/lib/insserv
/usr
/usr/share
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/sysv-rc
/usr/share/doc
/usr/share/doc/sysv-rc
/usr/share/doc/sysv-rc/copyright
/usr/share/doc/sysv-rc/README.Debian
/usr/share/doc/sysv-rc/NEWS.Debian.gz
/usr/share/doc/sysv-rc/README.runlevels.gz
/usr/share/sysv-rc
/usr/share/sysv-rc/saveconfig
/usr/share/doc/sysv-rc/changelog.Debian.gz

Can you provide any more details, and perhaps the output for `apt policy
sysv-rc`?

** Changed in: init-system-helpers (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1689204

Title:
  dpkg: error processing archive /var/cache/apt/archives/init-system-
  helpers_1.29ubuntu4_all.deb (--unpack):  trying to overwrite
  '/usr/sbin/invoke-rc.d', which is also in package sysv-rc
  2.88dsf-59.3ubuntu2

Status in init-system-helpers package in Ubuntu:
  Incomplete

Bug description:
  I was trying to do a normal apt-get upgrade when I started to run into
  issues. I am not sure how to fix this since it is a system package.
  This system was upgraded from 14.04 to 16.04, but it was working fine
  for awhile.

  I started in this thread, but I could not get it working.
  https://ubuntuforums.org/showthread.php?t=2359412

  This machine is now a Proxmox VM, so I have the option to do some
  testing with it.

  
  #: apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
bsdutils linux-generic linux-headers-generic linux-image-generic
  The following packages will be upgraded:
apparmor apt apt-transport-https apt-utils bind9-host console-setup 
console-setup-linux dbus dbus-x11 desktop-file-utils distro-info-data dnsutils 
docker-engine
dpkg-dev eject graphviz grub-common grub-pc grub-pc-bin grub2-common init 
init-system-helpers initramfs-tools initramfs-tools-bin initramfs-tools-core
keyboard-configuration klibc-utils krb5-locales krb5-multidev 
libapparmor-perl libapparmor1 libapt-inst2.0 libapt-pkg5.0 libarchive13 
libbind9-140 libblkid1
libc-bin libc-dev-bin libc6 libc6-dev libcdt5 libcgraph6 libdbus-1-3 
libdns-export162 libdns162 libdpkg-perl libdrm-amdgpu1 libdrm-intel1 
libdrm-nouveau2
libdrm-radeon1 libdrm2 libevent-2.0-5 libevent-core-2.0-5 libfdisk1 
libfreetype6 libfreetype6-dev libgc1c2 libgd-dev libgd3 libgl1-mesa-dri 
libgl1-mesa-glx
libglapi-mesa libglib2.0-0 libglib2.0-data libgnutls-openssl27 libgnutls30 
libgssapi-krb5-2 libgssrpc4 libgvc6 libgvpr2 libhogweed4 libicu55 
libisc-export160
libisc160 libisccc140 libisccfg140 libk5crypto3 libkadm5clnt-mit9 
libkadm5srv-mit9 libkdb5-8 libklibc libkrb5-3 libkrb5support0 liblwres141 
libmount1
libmysqlclient-dev libmysqlclient20 libnettle6 libpam-systemd libpathplan4 
libpci-dev libpci3 libpq-dev

[Touch-packages] [Bug 1693038] Re: needs to support restart on Lubuntu and Xubuntu

>From #ubuntu-devel:

14:14 < bdmurray> gnome-session-quit - End the current GNOME session
14:14 < bdmurray> There's a reboot button in software-properties-gtk that I'm 
  guessing doesn't do anything on Lubuntu or Xubuntu.
14:15 < Unit193> xfce4-session-logout --reboot
14:15 < bdmurray> Unit193: will there be a prompt too?
14:15 < Unit193> If you want that, drop '--reboot'


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

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Tags added: rls-aa-incoming

** Tags added: artful trusty xenial zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1693038

Title:
  needs to support restart on Lubuntu and Xubuntu

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The fix for bug 1241210 only works in gnome-session based sessions.
  Let's make sure that the driver restart button works on Xubuntu and
  Lubuntu.

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

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

[Touch-packages] [Bug 1692925] Re: Weird button border in Nautilus with Radiance theme

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1692925

Title:
  Weird button border in Nautilus with Radiance theme

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 17.04
  Release:17.04

  $ apt-cache policy light-themes
  light-themes:
Installed: 16.10+17.04.20170406-0ubuntu1
Candidate: 16.10+17.04.20170406-0ubuntu1
Version table:
   *** 16.10+17.04.20170406-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  
  As in the attached picture, the button borders in Nautilus look too dark for 
Radiance theme

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: light-themes 16.10+17.04.20170406-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 23 17:03:30 2017
  InstallationDate: Installed on 2017-04-20 (33 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693038] [NEW] needs to support restart on Lubuntu and Xubuntu

Public bug reported:

The fix for bug 1241210 only works in gnome-session based sessions.
Let's make sure that the driver restart button works on Xubuntu and
Lubuntu.

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: artful rls-aa-incoming trusty xenial zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1693038

Title:
  needs to support restart on Lubuntu and Xubuntu

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The fix for bug 1241210 only works in gnome-session based sessions.
  Let's make sure that the driver restart button works on Xubuntu and
  Lubuntu.

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

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

[Touch-packages] [Bug 1637800] Re: add a motd script for news

2017-05-23 Thread Dustin Kirkland 

** Changed in: base-files (Ubuntu Xenial)
 Assignee: Dustin Kirkland  (kirkland) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1637800

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions

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

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1693032] [NEW] missing dependency on gnome-session-bin

Public bug reported:

When bug 1241210 was fixed SoftwarePropertiesGtk.py was changed to call
gnome-session-quit which is provided by gnome-session-bin. However, a
dependency on gnome-session-bin was never added to software-properties-
gtk. This has led to the following possible Traceback:

Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1116, in on_driver_restart_clicked
subprocess.call(['gnome-session-quit', '--reboot'])
  File "/usr/lib/python3.5/subprocess.py", line 247, in call
with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
restore_signals, start_new_session)
  File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'gnome-session-quit'

There are a large collection of these crashes mixed in with this bucket:

https://errors.ubuntu.com/problem/bc249affe50a221622d55a34ecfe5223704c012c

I suspect that a lot of these crashes are from Lubuntu or Xubuntu
systems, but its possible some are not and the missing dependency should
be fixed anyway.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When bug 1241210 was fixed SoftwarePropertiesGtk.py was changed to call
  gnome-session-quit which is provided by gnome-session-bin. However, a
  dependency on gnome-session-bin was never added to software-properties-
  gtk. This has led to the following possible Traceback:
  
  Traceback (most recent call last):
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1116, in on_driver_restart_clicked
- subprocess.call(['gnome-session-quit', '--reboot'])
-   File "/usr/lib/python3.5/subprocess.py", line 247, in call
- with Popen(*popenargs, **kwargs) as p:
-   File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
- restore_signals, start_new_session)
-   File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child
- raise child_exception_type(errno_num, err_msg)
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1116, in on_driver_restart_clicked
+ subprocess.call(['gnome-session-quit', '--reboot'])
+   File "/usr/lib/python3.5/subprocess.py", line 247, in call
+ with Popen(*popenargs, **kwargs) as p:
+   File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
+ restore_signals, start_new_session)
+   File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child
+ raise child_exception_type(errno_num, err_msg)
  FileNotFoundError: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'gnome-session-quit'
  
  There are a large collection of these crashes mixed in with this bucket:
  
  https://errors.ubuntu.com/problem/bc249affe50a221622d55a34ecfe5223704c012c
  
- I suspect that a lot of these crashes are from Xubuntu systems, but its
- possible some are not and the missing dependency should be fixed anyway.
+ I suspect that a lot of these crashes are from Lubuntu or Xubuntu
+ systems, but its possible some are not and the missing dependency should
+ be fixed anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1693032

Title:
  missing dependency on gnome-session-bin

Status in software-properties package in Ubuntu:
  New

Bug description:
  When bug 1241210 was fixed SoftwarePropertiesGtk.py was changed to
  call gnome-session-quit which is provided by gnome-session-bin.
  However, a dependency on gnome-session-bin was never added to
  software-properties-gtk. This has led to the following possible
  Traceback:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1116, in on_driver_restart_clicked
  subprocess.call(['gnome-session-quit', '--reboot'])
    File "/usr/lib/python3.5/subprocess.py", line 247, in call
  with Popen(*popenargs, **kwargs) as p:
    File "/usr/lib/python3.5/subprocess.py", line 676, in __init__
  restore_signals, start_new_session)
    File "/usr/lib/python3.5/subprocess.py", line 1282, in _execute_child
  raise child_exception_type(errno_num, err_msg)
  FileNotFoundError: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'gnome-session-quit'

  There are a large collection of these crashes mixed in with this
  bucket:

  https://errors.ubuntu.com/problem/bc249affe50a221622d55a34ecfe5223704c012c

  I suspect that a lot of these crashes are from Lubuntu or Xubuntu
  systems, but its possible some are not and the missing dependency
  should be fixed anyway.

To manage notifications about this bug go to:

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1692127] Re: duplicate signature for Package problems can be too short

This should be SRU'ed to stable releases but let's make sure it is
working properly first.

** Also affects: apport (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

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

** Changed in: apport (Ubuntu Zesty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1692127

Title:
  duplicate signature for Package problems can be too short

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Fix Released

Bug description:
  Steve brought up bug 1691983 and how it's duplicate signature is
  missing information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

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

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

[Touch-packages] [Bug 1693019] [NEW] package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: Paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ko

2017-05-23 Thread Paul Kiefer

Public bug reported:

Can not find it just don’t  download it

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: iproute2 4.3.0-1ubuntu3.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 libjasper1: Install
 iproute2: Configure
 libjasper1: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue May 23 21:34:50 2017
ErrorMessage: Paketet är i ett väldigt dåligt inkonsistent läge; du bör  
ominstallera det innan du försöker konfigurera.
InstallationDate: Installed on 2017-04-29 (23 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: iproute2
Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: 
Paketet är i ett väldigt dåligt inkonsistent läge; du bör  ominstallera det 
innan du försöker konfigurera.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1693019

Title:
  package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade:
  Paketet är i ett väldigt dåligt inkonsistent läge; du bör
  ominstallera det innan du försöker konfigurera.

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Can not find it just don’t  download it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   libjasper1: Install
   iproute2: Configure
   libjasper1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 23 21:34:50 2017
  ErrorMessage: Paketet är i ett väldigt dåligt inkonsistent läge; du bör  
ominstallera det innan du försöker konfigurera.
  InstallationDate: Installed on 2017-04-29 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: 
Paketet är i ett väldigt dåligt inkonsistent läge; du bör  ominstallera det 
innan du försöker konfigurera.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 857524] Re: dhclient-script will not work with read-only /etc

2017-05-23 Thread gombi

This change makes dhclient-script dependent on the existence of
/etc/fstab. If /etc/fstab does not exist, dhclient fails to grab an IP.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/857524

Title:
  dhclient-script will not work with read-only /etc

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  dhclient-script attempts to support read-only root , but it wont correctly 
work.
  For a read-only root to work, and support dhclient-script writing to 
/etc/resolv.conf, then /etc/resolv.conf would have to be a symlink to a 
writeable location (ie, /run).

  To that end, dhclient-script attempts to check and see if / is going
  to be mounted 'rw' and only wait for that case if it is.

  The problem is that it basically has the following logic:
if root_will_be_mounted_rw; then
wait-for-writable /etc/
fi
new_resolv_conf=/etc/resolv.conf.dhclient-new
write new file to to $new_resolv_conf
change attributes of $new_resolv_conf to match resolv.conf
mv $new_resolv_conf /etc/resolv.conf

  That doesn't work if /etc is read-only and /etc/resolv.conf is a symlink for 
the following reasons:
   * $new_resolv_conf is being written to /etc/ (and wont be writable)
   * the mv will actually break the symlink and try to create a new file in /etc

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: isc-dhcp-client 4.1.1-P1-17ubuntu9
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:50:56 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to oneiric on 2010-11-15 (311 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/857524/+subscriptions

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

[Touch-packages] [Bug 1681493] Re: Ubuntu Zesty: Problem With Screen Brightness Settings

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1681493

Title:
  Ubuntu Zesty: Problem With Screen Brightness Settings

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS (Nvidia GTX1070)
  Ubuntu 17.04
  Xorg-Server-1.19.3
  Nvidia driver 375.39

  Situation on 2017-04-05:
  Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen 
brightness, but after restarting the screen brightness of my laptop resets to 
maximum.

  Situation on 2017-04-08:
  Today I received many Ubuntu updates (kernel included), and I also installed 
freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - 
Proprietary GPU Drivers PPA).
  Now brightness settings are correctly saved, but I have a new problem: 
changing brightness level doesn't produce any effect (both with or without 
Nvidia driver installed)

  Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and
  "acpi_video1"

  ~$ systemctl status systemd-backlight@backlight:acpi_video0.service
  ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 683 (code=exited, status=0/SUCCESS)

  ~$ systemctl status systemd-backlight@backlight:acpi_video1.service
  ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 684 (code=exited, status=0/SUCCESS)

  Situation on 2017-04-10:
  I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via 
additional drivers.
  Now the situation has returned to initial problem: I can again adjust the 
screen brightness, but after restarting the screen brightness of my laptop 
again resets to maximum.
  --- 
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-02 (98 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. G752VS
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: systemd 232-21ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VS.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G752VS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1681493] Re: Ubuntu Zesty: Problem With Screen Brightness Settings

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1681493

Title:
  Ubuntu Zesty: Problem With Screen Brightness Settings

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS (Nvidia GTX1070)
  Ubuntu 17.04
  Xorg-Server-1.19.3
  Nvidia driver 375.39

  Situation on 2017-04-05:
  Ubuntu 17.04 doesn't save my brightness settings. I can adjust the screen 
brightness, but after restarting the screen brightness of my laptop resets to 
maximum.

  Situation on 2017-04-08:
  Today I received many Ubuntu updates (kernel included), and I also installed 
freshly released Nvidia 381.09 driver (via “Graphics Drivers” team - 
Proprietary GPU Drivers PPA).
  Now brightness settings are correctly saved, but I have a new problem: 
changing brightness level doesn't produce any effect (both with or without 
Nvidia driver installed)

  Inside "/sys/class/backlight/" I have two folders: "acpi_video0" and
  "acpi_video1"

  ~$ systemctl status systemd-backlight@backlight:acpi_video0.service
  ● systemd-backlight@backlight:acpi_video0.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 16min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 683 (code=exited, status=0/SUCCESS)

  ~$ systemctl status systemd-backlight@backlight:acpi_video1.service
  ● systemd-backlight@backlight:acpi_video1.service - Load/Save Screen 
Backlight B
 Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static; 
vendo
 Active: active (exited) since Sat 2017-04-08 13:37:31 CEST; 22min ago
   Docs: man:systemd-backlight@.service(8)
   Main PID: 684 (code=exited, status=0/SUCCESS)

  Situation on 2017-04-10:
  I purged Nvidia 381.09 driver and reinstalled default Nvidia 375.39 via 
additional drivers.
  Now the situation has returned to initial problem: I can again adjust the 
screen brightness, but after restarting the screen brightness of my laptop 
again resets to maximum.
  --- 
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-02 (98 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161229)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1837 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 0bda:57fa Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04d9:a070 Holtek Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. G752VS
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: systemd 232-21ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1cb200eb-669b-45c4-af32-e67f66a464f2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VS.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VS.306:bd10/19/2016:svnASUSTeKCOMPUTERINC.:pnG752VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G752VS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-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 Ubuntu
Touch seeded 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)

[Touch-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 Ubuntu
Touch seeded 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

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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

[Touch-packages] [Bug 1693002] [NEW] SRU of LXC 1.0.10 (upstream bugfix release)

2017-05-23 Thread Stéphane Graber

Public bug reported:

LXC upstream released LXC 1.0.10 as a bugfix release with following changelog:
- Security fix for CVE-2016-10124
- Security fix for CVE-2017-5985

- attach: simplify lsm_openat()
- commands: improve logging
- utils: add macro __LXC_NUMSTRLEN
- tests; Don't cause test failures on cleanup errors
- conf: clearly report to either use drop or keep
- attach: close lsm label file descriptor
- conf, attach: save errno across call to close
- templates/lxc-debian.in: Fix typo in calling dpkg with
  --print-foreign-architectures option
- templates/lxc-debian.in: handle ppc hostarch -> powerpc
- Fix regression in errno handling cherry-pick
- don't try to get stuff from /usr/lib/systemd on the host
- lxc-opensuse: rm poweroff.target -> sigpwr.target copy
- Add --enable-gnutls option
- tests: skip unpriv tests on broken overlay module
- Use AC_HEADER_MAJOR to detect major()/minor()/makedev()
- Make lxc-start-ephemeral Python 3.2-compatible
- systemd: enable delegate in service file
- confile: clear lxc.network..ipv{4,6} when empty
- seccomp: allow x32 guests on amd64 hosts.
- squeeze is not a supported release anymore, drop the key
- seccomp: set SCMP_FLTATR_ATL_TSKIP if available
- lxc-checkconfig: verify new[ug]idmap are setuid-root
- python3: Deal with potential NULL char*
- lxc-download.in / allow setting keyserver from env
- lxc-download.in / Document keyserver change in help
- Change variable check to match existing style
- tests: Support running on IPv6 networks
- tests: Kill containers (don't wait for shutdown)
- Fix opening wrong file in suggest_default_idmap
- lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals
- Increased buffer length in print_stats()
- remove obsolete note about api stability
- conf: less error prone pointer access
- create ISSUE_TEMPLATE.md
- issue template: fix typo
- conf: order mount options
- commands: avoid NULL pointer dereference
- commands: non-functional changes
- lxccontainer: avoid NULL pointer dereference


Just like Ubuntu itself, upstream releases long term support releases, as is 
1.0 and then periodic point releases including all the accumulated bugfixes.

Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.

This should qualify under the minor upstream bugfix release allowance of
the SRU policy, letting us SRU this without paperwork for every single
change included in this upstream release.

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: lxc (Ubuntu Trusty)
 Importance: Undecided
 Status: In Progress

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

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

** Changed in: lxc (Ubuntu Trusty)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1693002

Title:
  SRU of LXC 1.0.10 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Invalid
Status in lxc source package in Trusty:
  In Progress

Bug description:
  LXC upstream released LXC 1.0.10 as a bugfix release with following changelog:
  - Security fix for CVE-2016-10124
  - Security fix for CVE-2017-5985

  - attach: simplify lsm_openat()
  - commands: improve logging
  - utils: add macro __LXC_NUMSTRLEN
  - tests; Don't cause test failures on cleanup errors
  - conf: clearly report to either use drop or keep
  - attach: close lsm label file descriptor
  - conf, attach: save errno across call to close
  - templates/lxc-debian.in: Fix typo in calling dpkg with
--print-foreign-architectures option
  - templates/lxc-debian.in: handle ppc hostarch -> powerpc
  - Fix regression in errno handling cherry-pick
  - don't try to get stuff from /usr/lib/systemd on the host
  - lxc-opensuse: rm poweroff.target -> sigpwr.target copy
  - Add --enable-gnutls option
  - tests: skip unpriv tests on broken overlay module
  - Use AC_HEADER_MAJOR to detect major()/minor()/makedev()
  - Make lxc-start-ephemeral Python 3.2-compatible
  - systemd: enable delegate in service file
  - confile: clear lxc.network..ipv{4,6} when empty
  - seccomp: allow x32 guests on amd64 hosts.
  - squeeze is not a supported release anymore, drop the key
  - seccomp: set SCMP_FLTATR_ATL_TSKIP if available
  - lxc-checkconfig: verify new[ug]idmap are setuid-root
  - python3: Deal with potential NULL char*
  - lxc-download.in / allow setting keyserver from env
  - lxc-download.in / Document keyserver change in help
  - Change variable check to match

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

2017-05-23 Thread daniel CURTIS

Hello. I'm sorry Luigi Espenlaub. I should write "chown" in my post. Or
at least mention, that it's just reference to the man pages etc. Sorry
once again. I'm very glad, that You understand it now :- )

Best regards.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1522675

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

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 Ubuntu
Touch seeded 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

[Touch-packages] [Bug 1692996] Re: package apport 2.20.4-0ubuntu4 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 Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1692996

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

Status in apport package in Ubuntu:
  New

Bug description:
  I tried to install the following updates:
  apport 2.20.4-0ubuntu4.1
  apport-gtk 2.20-4-0ubuntu4.1
  unattended-upgrades 0.93.1ubuntu2.2
  these upgrades failed to install and produced a system error.

  I then tried to update an application, indicator-kdeconnect which then
  produced the apport error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   indicator-kdeconnect:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   600:110:117:0:2017-05-17 16:02:54.202140415 -0400:2017-05-12 
10:15:15.548592471 -0400:/var/crash/_opt_google_chrome_chrome.1000.uploaded
   640:1000:117:8425789:2017-05-17 16:02:51.106106996 -0400:2017-05-17 
16:02:52.106106996 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash
   664:1000:117:0:2017-05-17 16:02:52.110107045 -0400:2017-05-17 
16:02:52.110107045 -0400:/var/crash/_opt_google_chrome_chrome.1000.upload
   640:1000:117:7647277:2017-05-22 15:31:16.909297466 -0400:2017-05-22 
15:31:17.909297466 -0400:/var/crash/_usr_bin_compiz.1000.crash
   600:0:117:204585:2017-05-23 14:09:48.879699707 -0400:2017-05-23 
14:09:49.879699707 -0400:/var/crash/apport.0.crash
  Date: Tue May 23 14:09:49 2017
  DuplicateSignature:
   package:apport:2.20.4-0ubuntu4
   Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package apport (--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 2014-11-19 (916 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 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-14 (39 days ago)

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

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

[Touch-packages] [Bug 1692996] [NEW] package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-05-23 Thread David Moncrief

Public bug reported:

I tried to install the following updates:
apport 2.20.4-0ubuntu4.1
apport-gtk 2.20-4-0ubuntu4.1
unattended-upgrades 0.93.1ubuntu2.2
these upgrades failed to install and produced a system error.

I then tried to update an application, indicator-kdeconnect which then
produced the apport error.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4
AptOrdering:
 indicator-kdeconnect:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CrashReports:
 600:110:117:0:2017-05-17 16:02:54.202140415 -0400:2017-05-12 
10:15:15.548592471 -0400:/var/crash/_opt_google_chrome_chrome.1000.uploaded
 640:1000:117:8425789:2017-05-17 16:02:51.106106996 -0400:2017-05-17 
16:02:52.106106996 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash
 664:1000:117:0:2017-05-17 16:02:52.110107045 -0400:2017-05-17 
16:02:52.110107045 -0400:/var/crash/_opt_google_chrome_chrome.1000.upload
 640:1000:117:7647277:2017-05-22 15:31:16.909297466 -0400:2017-05-22 
15:31:17.909297466 -0400:/var/crash/_usr_bin_compiz.1000.crash
 600:0:117:204585:2017-05-23 14:09:48.879699707 -0400:2017-05-23 
14:09:49.879699707 -0400:/var/crash/apport.0.crash
Date: Tue May 23 14:09:49 2017
DuplicateSignature:
 package:apport:2.20.4-0ubuntu4
 Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
 Rebuilding /usr/share/applications/bamf-2.index...
 dpkg: error processing package apport (--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 2014-11-19 (916 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package apport 2.20.4-0ubuntu4 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-14 (39 days ago)

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


** Tags: amd64 apport-package zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1692996

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

Status in apport package in Ubuntu:
  New

Bug description:
  I tried to install the following updates:
  apport 2.20.4-0ubuntu4.1
  apport-gtk 2.20-4-0ubuntu4.1
  unattended-upgrades 0.93.1ubuntu2.2
  these upgrades failed to install and produced a system error.

  I then tried to update an application, indicator-kdeconnect which then
  produced the apport error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   indicator-kdeconnect:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   600:110:117:0:2017-05-17 16:02:54.202140415 -0400:2017-05-12 
10:15:15.548592471 -0400:/var/crash/_opt_google_chrome_chrome.1000.uploaded
   640:1000:117:8425789:2017-05-17 16:02:51.106106996 -0400:2017-05-17 
16:02:52.106106996 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash
   664:1000:117:0:2017-05-17 16:02:52.110107045 -0400:2017-05-17 
16:02:52.110107045 -0400:/var/crash/_opt_google_chrome_chrome.1000.upload
   640:1000:117:7647277:2017-05-22 15:31:16.909297466 -0400:2017-05-22 
15:31:17.909297466 -0400:/var/crash/_usr_bin_compiz.1000.crash
   600:0:117:204585:2017-05-23 14:09:48.879699707 -0400:2017-05-23 
14:09:49.879699707 -0400:/var/crash/apport.0.crash
  Date: Tue May 23 14:09:49 2017
  DuplicateSignature:
   package:apport:2.20.4-0ubuntu4
   Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package apport (--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 2014-11-19 (916 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you

[Touch-packages] [Bug 1692997] [NEW] libelf test for section size in wrong place

2017-05-23 Thread David Anderson

Public bug reported:

It seems to me that the test for an invalid section size
wants be moved up from the map case to cover both the read and the map
case.

To guard against a bogus section size for both cases.
Rather than relying on a malloc failure to catch a 
completely bogus section size.  
Thus allowing a more accurate error indication.

>From elfutils_0.165.orig.tar.bz2

elfutils-0.165/libelf/elf_getdata.c


--- elf_getdata.c.orig  2017-05-23 10:56:05.547607473 -0700
+++ elf_getdata.c   2017-05-23 11:08:27.459670572 -0700
@@ -292,21 +292,20 @@
  __libelf_seterrno (ELF_E_INVALID_DATA);
  return 1;
}
+ /* First see whether the information in the section header is
+   valid and it does not ask for too much.  Check for unsigned
+   overflow.  */
+  if (unlikely (offset > elf->maximum_size
+  || elf->maximum_size - offset < size))
+{
+  /* Something is wrong.  */
+  __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
+  return 1;
+}
 
   /* We can use the mapped or loaded data if available.  */
   if (elf->map_address != NULL)
{
- /* First see whether the information in the section header is
-valid and it does not ask for too much.  Check for unsigned
-overflow.  */
- if (unlikely (offset > elf->maximum_size
- || elf->maximum_size - offset < size))
-   {
- /* Something is wrong.  */
- __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
- return 1;
-   }
-
  scn->rawdata_base = scn->rawdata.d.d_buf
= (char *) elf->map_address + elf->start_offset + offset;
}

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1692997

Title:
  libelf test for section size in wrong place

Status in elfutils package in Ubuntu:
  New

Bug description:
  It seems to me that the test for an invalid section size
  wants be moved up from the map case to cover both the read and the map
  case.

  To guard against a bogus section size for both cases.
  Rather than relying on a malloc failure to catch a 
  completely bogus section size.  
  Thus allowing a more accurate error indication.

  From elfutils_0.165.orig.tar.bz2

  elfutils-0.165/libelf/elf_getdata.c

  
  --- elf_getdata.c.orig2017-05-23 10:56:05.547607473 -0700
  +++ elf_getdata.c 2017-05-23 11:08:27.459670572 -0700
  @@ -292,21 +292,20 @@
  __libelf_seterrno (ELF_E_INVALID_DATA);
  return 1;
}
  + /* First see whether the information in the section header is
  + valid and it does not ask for too much.  Check for unsigned
  + overflow.  */
  +  if (unlikely (offset > elf->maximum_size
  +  || elf->maximum_size - offset < size))
  +{
  +  /* Something is wrong.  */
  +  __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
  +  return 1;
  +}
   
 /* We can use the mapped or loaded data if available.  */
 if (elf->map_address != NULL)
{
  -   /* First see whether the information in the section header is
  -  valid and it does not ask for too much.  Check for unsigned
  -  overflow.  */
  -   if (unlikely (offset > elf->maximum_size
  -   || elf->maximum_size - offset < size))
  - {
  -   /* Something is wrong.  */
  -   __libelf_seterrno (ELF_E_INVALID_SECTION_HEADER);
  -   return 1;
  - }
  -
  scn->rawdata_base = scn->rawdata.d.d_buf
= (char *) elf->map_address + elf->start_offset + offset;
}

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

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

[Touch-packages] [Bug 1683095] Re: rsync has -C / --cvs-exclude enabled permanently

Hello and thank you for filing this bug report.

Can you provide (perhaps as attachments if needed) an example command
and output that show the exact issue?

Please mark it as New once you have done so.

** Changed in: rsync (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1683095

Title:
  rsync has -C / --cvs-exclude enabled permanently

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.04 I've noticed that every rsync command
  has the -C option added and I can see no way to disable this very
  unwanted behavior. I've been running the same set of rsync commands
  for years and the -C option was never tacked on like it is now (as far
  as I can tell). I've read the man pages, checked the various config
  files, tried adding --no-C to all of my scripts (as annoying as that
  is) and still see no functioning way to disable this.

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

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

[Touch-packages] [Bug 1682227] Re: dnsmasq, network manager still not able to relay DNS queries or respond to DNS requests after VPN connection failure / die off

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

This bug is essentially about the same "VPN fails to DNS" issue as bug
1688018; marking as a duplicate, since the other bug report as more
information about the issue.

** This bug has been marked a duplicate of bug 1688018
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1682227

Title:
  dnsmasq, network manager *still* not able to relay DNS queries or
  respond to DNS requests after VPN connection failure / die off

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  This remains an issue.  Supposedly fixed, it's still an issue in
  16.04.

  When an OpenVPN connection enables, or dies off, dnsmasq ceases to
  respond.  The upstream DNS servers set are two bind9 instances that
  both reply to direct queries, so the core issue is that `dnsmasq` is
  broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 12 15:58:28 2017
  InstallationDate: Installed on 2016-12-20 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1682227] Re: dnsmasq, network manager still not able to relay DNS queries or respond to DNS requests after VPN connection failure / die off

Thank you very much for filing this bug report. It seems like it is a
real issue and I will place it on the Server Team's backlog for now.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1682227

Title:
  dnsmasq, network manager *still* not able to relay DNS queries or
  respond to DNS requests after VPN connection failure / die off

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  This remains an issue.  Supposedly fixed, it's still an issue in
  16.04.

  When an OpenVPN connection enables, or dies off, dnsmasq ceases to
  respond.  The upstream DNS servers set are two bind9 instances that
  both reply to direct queries, so the core issue is that `dnsmasq` is
  broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 12 15:58:28 2017
  InstallationDate: Installed on 2016-12-20 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436168] Re: systemd-journald crashed with SIGABRT in journal_file_move_to_object()

2017-05-23 Thread mxyzptlk

Keep getting this bug lately in 17.10. Seems to happen most often when
using Chrome/Chromium or Opera, and more often still if using one of
those browsers on a Google property (Google Search, Google Images,
Gmail, YouTube).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1436168

Title:
  systemd-journald crashed with SIGABRT in journal_file_move_to_object()

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Crashed over night while recovering backup.

  .

  Xubuntu 15.04 beta1

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  Date: Tue Mar 24 23:13:27 2015
  ExecutablePath: /lib/systemd/systemd-journald
  ExecutableTimestamp: 1427124595
  InstallationDate: Installed on 2015-03-23 (1 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H
  ProcCmdline: /lib/systemd/systemd-journald
  ProcCwd: /
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=45370e47-0377-4e9d-87fc-81889c091532 ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-journald crashed with SIGABRT
  UpgradeStatus: Upgraded to vivid on 2015-03-24 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 07/08/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7c
  dmi.board.name: GA-MA790GP-UD4H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790GP-UD4H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1682136] Re: dnsmasq bad hex constant with 2 mac addresses but not true

Hello and thank you for filing this bug report. 12.04 has gone EOL in
the meanwhile, though. Does this issue occur with Trusty or later?

** Changed in: dnsmasq (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1682136

Title:
  dnsmasq bad hex constant with 2 mac addresses but not true

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  Following line of dnsmasq.conf will not allow dnsmasq to start giving
  error "bad hex constant at line x in /etc/dnsmasq.conf" and this
  despite the fact that there is no error in mac addresses.

  dhcp-
  
host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi

  With only one of those two mac addresses, all is good, so there is no
  error in mac addresses. In the dnsmasq.conf they are other dhcp-host
  with multiple mac addresses like

  dhcp-
  
host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi

  and they are not rejected.

  When copying the default configuration line in a dnsmasq-2.72-3 of
  Debian 8.7, no problem.

  Description:Ubuntu 12.04.5 LTS
  Release:12.04

  dnsmasq:
Installé : 2.59-4ubuntu0.2
Candidat : 2.59-4ubuntu0.2
   Table de version :
   *** 2.59-4ubuntu0.2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   2.59-4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf]
  ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  Date: Wed Apr 12 15:25:20 2017
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724

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

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

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

** Tags added: rls-aa-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1458204

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)

** Also affects: zlib (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Tags added: regression-release

** Tags added: rls-aa-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1692870

Title:
  gzip compression broken in UniFi (built-in tomcat)

Status in zlib package in Ubuntu:
  Confirmed
Status in zlib source package in Zesty:
  New

Bug description:
  [Impact] 
  Since I upgraded from Ubuntu 16.10 to 17.04, my Guest portal for my UniFi 
system was broken (https://www.ubnt.com/download/unifi/).

  Curl gave me the following response:
  # curl - --compress localhost:8880/guest/s/default/
  *   Trying ::1...
  * TCP_NODELAY set
  * Connected to localhost (::1) port 8880 (#0)
  > GET /guest/s/default/ HTTP/1.1
  > Host: localhost:8880
  > User-Agent: curl/7.52.1
  > Accept: */*
  > Accept-Encoding: deflate, gzip
  >
  < HTTP/1.1 200 OK
  < Server: Apache-Coyote/1.1
  < Content-Type: text/html;charset=utf-8
  < Transfer-Encoding: chunked
  < Content-Encoding: gzip
  < Vary: Accept-Encoding
  < Date: Tue, 23 May 2017 11:19:22 GMT
  <
  * Error while processing content unencoding: invalid code lengths set
  * Failed writing data
  * Curl_http_done: called premature == 1
  * Closing connection 0
  curl: (23) Error while processing content unencoding: invalid code lengths set

  [Test Case]
  Just install a fresh Ubuntu 17.04 with UniFi controller. And the Guest Portal 
is broken. See above.
  When disabling compression in curl, it works fine.

  After some debugging, I found out that downgrading to zlib 1:1.2.8
  .dfsg-2ubuntu5.1 was a workaround.

  Now after digging into the issue some more, I found the following upstream 
patch (unreleased version), fixes the issue:
  https://github.com/madler/zlib/commit/f9694097dd69354b03cb8af959094c7f260db0a1

  [Regression Potential]
  Everybody upgrading from 16.10 (or previous) to 17.04 will be affected by 
this.

  The patch is taken from upstream, so this isn't a change we will need
  to keep different from upstream.

  I've already created a new package (see debdiff) that fixes the issue.

  [Other Info]
  Now as the UniFi controller is just some Tomcat, which relies on Java 
(OpenJDK), which uses zlib for its built-in Compression/Decompression. I guess 
even more java related tools can be broken. But I didn't have time to test this.

  At least some other people using UniFi have the same issue, see:
  
https://community.ubnt.com/t5/UniFi-Wireless/ERR-CONTENT-DECODING-FAILED-on-guest-portal-customisation/td-p/1903419

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

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

[Touch-packages] [Bug 1692910] Re: package python3-software-properties 0.96.20.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139

2017-05-23 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that a package failed to install due to a segmentation fault in
the application being used for the package installation process.
Unfortunately, this bug report isn't very useful in its current state
and a crash report would be much more useful.  Could you try recreating
this issue by enabling apport to catch the crash report 'sudo service
apport start force_start=1' and then trying to install the same package
again?  This process will create a new bug report so I am marking this
one as Invalid.  Thanks again for helping out!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: package-install-segfault

** Changed in: software-properties (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1692910

Title:
  package python3-software-properties 0.96.20.6 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 139

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  Hi, tried to run an update. The main files were related to python and
  KiCAD. During installation of KiCAD the PC crashed and returned to the
  purle login screen. I couldnt login so restarted. Then tried again and
  the update failed again and raised this link to complet the bug
  report. My guess would be its connected to the KiCAD update so will
  try uninstalling KiCAD.

  Thanks

  Dave H

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-software-properties 0.96.20.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 15:24:30 2017
  DuplicateSignature:
   package:python3-software-properties:0.96.20.6
   Unpacking kicad-library (201705230749+1258~3~ubuntu16.04.1) over 
(201705161649+1252~3~ubuntu16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kicad-library_201705230749+1258~3~ubuntu16.04.1_all.deb 
(--unpack):
unable to install new version of 
'/usr/share/kicad/modules/packages3d/NF-Transformers_ETAL.3dshapes/NF-Transformer_P3181_ETAL_HandSoldering.wrl':
 No such file or directory
  ErrorMessage: subprocess new pre-removal script returned error exit status 139
  InstallationDate: Installed on 2016-11-30 (174 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.20.6 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1669270] Re: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

2017-05-23 Thread Steve Langasek

ok, the output of 'debconf-show ucf' looks reasonable, so the problem
doesn't appear to be with debconf database corruption.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ucf in Ubuntu.
https://bugs.launchpad.net/bugs/1669270

Title:
  package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 10

Status in ucf package in Ubuntu:
  New

Bug description:
  When I start my screen, a blue screen appears with 2 options,
  1. GNU/grub-pc
  2. Advanced options for ubuntu.

  And I have to always click on 1 to get my PC started(or it
  automatically chooses 1).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-pc 2.02~beta2-36ubuntu3.7
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Mar  2 10:55:13 2017
  DpkgHistoryLog:
   Start-Date: 2017-03-02  10:55:02
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: libgd3:amd64 (2.1.1-4ubuntu0.16.04.5, 2.1.1-4ubuntu0.16.04.6), 
libtiff5:amd64 (4.0.6-1, 4.0.6-1ubuntu0.1)
  DuplicateSignature:
   package:grub-pc:2.02~beta2-36ubuntu3.7
   Setting up unattended-upgrades (0.90ubuntu0.3) ...
   dpkg: error processing package unattended-upgrades (--configure):
subprocess installed post-installation script returned error exit status 10
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2017-02-16 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InvalidGrubScript: /etc/default/grub
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=3cfa4b16-e389-41c3-a5c6-98add8a87218 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: grub2
  Title: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689854] Update Released

The verification of the Stable Release Update for isc-dhcp 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 Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1689854

Title:
  Multiple DHCPv6 client interfaces fail to receive some server
  responses

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  When using isc-dhcp-client on a Trusty system, with multiple
  interfaces configured to use DHCPv6, not all the DHCPv6 clients will
  receive the server responses on some of the interfaces.  This results
  in not all DHCPv6 interfaces being configured.

  [Test Case]

  Set up a DHCPv6 server with multiple interfaces (3-4 is enough) and
  configure it to serve DHCPv6 on all the interfaces (as separate
  subnets).  The server release does not matter.  Set up a client system
  with the same number of interfaces, connected/bridged to the server
  interfaces.  The client must be a Trusty system.  Configure (with
  ifupdown via /etc/network/interfaces) all the interfaces to use
  DHCPv6, and reboot.  Keep rebooting until one or more of the DHCPv6
  interfaces fails to get an address; it should not take more than a few
  reboots.  After a failure, even manual ifdown/ifup on the failed
  interface will not get a DHCPv6 address.

  [Regression Potential]

  * As this changes how the isc-dhcp-client binds to IPv6 sockets, this
  could cause problems when the client tries to bind, send, or receive,
  with this or other operations.

  * This is fixed upstream already, and the patch is included in Xenial
  and later releases.  This patch is needed only in the Trusty release.

  * Upstream patch :
  
https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=commit;h=4b8251a0c06b7d8706a28904fdef2414f045cc2c

  [Other Info]

  * [ISC-Bugs #34784]
  Please note that no ISC bug URL can be provided since the ISC bug database is 
closed :

  Reference:  https://www.isc.org/community/report-bug/
  ...
  Confidentiality

  It is typical for open-source projects to have an open bug database. At the 
moment, the ISC bug database is closed.  However, we reserve the right to 
publish your bug report at some point in the future. Please do not include 
information you consider to be confidential.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1689854/+subscriptions

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

[Touch-packages] [Bug 1689854] Re: Multiple DHCPv6 client interfaces fail to receive some server responses

This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.9

---
isc-dhcp (4.2.4-7ubuntu12.9) trusty; urgency=medium

* [4b8251a] DHCPv6: fix socket handling so multiple DHCPv6 local clients will
successfully get addresses (LP: #1689854)

-- Dan Streetman Wed, 10 May 2017
12:19:35 -0300

** Changed in: isc-dhcp (Ubuntu Trusty)
Status: Fix Committed => Fix Released

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1689854

Title:
Multiple DHCPv6 client interfaces fail to receive some server
responses

Status in isc-dhcp package in Ubuntu:
Fix Released
Status in isc-dhcp source package in Trusty:
Fix Released

Bug description:
[Impact]

When using isc-dhcp-client on a Trusty system, with multiple
interfaces configured to use DHCPv6, not all the DHCPv6 clients will
receive the server responses on some of the interfaces. This results
in not all DHCPv6 interfaces being configured.

[Test Case]

Set up a DHCPv6 server with multiple interfaces (3-4 is enough) and
configure it to serve DHCPv6 on all the interfaces (as separate
subnets). The server release does not matter. Set up a client system
with the same number of interfaces, connected/bridged to the server
interfaces. The client must be a Trusty system. Configure (with
ifupdown via /etc/network/interfaces) all the interfaces to use
DHCPv6, and reboot. Keep rebooting until one or more of the DHCPv6
interfaces fails to get an address; it should not take more than a few
reboots. After a failure, even manual ifdown/ifup on the failed
interface will not get a DHCPv6 address.

[Regression Potential]

* As this changes how the isc-dhcp-client binds to IPv6 sockets, this
could cause problems when the client tries to bind, send, or receive,
with this or other operations.

* This is fixed upstream already, and the patch is included in Xenial
and later releases. This patch is needed only in the Trusty release.

* Upstream patch :

https://source.isc.org/cgi-bin/gitweb.cgi?p=dhcp.git;a=commit;h=4b8251a0c06b7d8706a28904fdef2414f045cc2c

[Other Info]

* [ISC-Bugs #34784]
Please note that no ISC bug URL can be provided since the ISC bug database is
closed :

Reference: https://www.isc.org/community/report-bug/
...
Confidentiality

It is typical for open-source projects to have an open bug database. At the
moment, the ISC bug database is closed. However, we reserve the right to
publish your bug report at some point in the future. Please do not include
information you consider to be confidential.
...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1689854/+subscriptions

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

[Touch-packages] [Bug 1692925] [NEW] Weird button border in Nautilus with Radiance theme

2017-05-23 Thread Carlo Lobrano

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

$ apt-cache policy light-themes
light-themes:
  Installed: 16.10+17.04.20170406-0ubuntu1
  Candidate: 16.10+17.04.20170406-0ubuntu1
  Version table:
 *** 16.10+17.04.20170406-0ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
100 /var/lib/dpkg/status


As in the attached picture, the button borders in Nautilus look too dark for 
Radiance theme

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: light-themes 16.10+17.04.20170406-0ubuntu1
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
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 23 17:03:30 2017
InstallationDate: Installed on 2017-04-20 (33 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

** Attachment added: "Nautilus screenshot"
   
https://bugs.launchpad.net/bugs/1692925/+attachment/4882004/+files/nautilus-detail.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1692925

Title:
  Weird button border in Nautilus with Radiance theme

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 17.04
  Release:17.04

  $ apt-cache policy light-themes
  light-themes:
Installed: 16.10+17.04.20170406-0ubuntu1
Candidate: 16.10+17.04.20170406-0ubuntu1
Version table:
   *** 16.10+17.04.20170406-0ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  500 http://it.archive.ubuntu.com/ubuntu zesty/main i386 Packages
  100 /var/lib/dpkg/status

  
  As in the attached picture, the button borders in Nautilus look too dark for 
Radiance theme

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: light-themes 16.10+17.04.20170406-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 23 17:03:30 2017
  InstallationDate: Installed on 2017-04-20 (33 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-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 Ubuntu
Touch seeded 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

[Touch-packages] [Bug 1692910] Re: package python3-software-properties 0.96.20.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1692910

Title:
  package python3-software-properties 0.96.20.6 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 139

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hi, tried to run an update. The main files were related to python and
  KiCAD. During installation of KiCAD the PC crashed and returned to the
  purle login screen. I couldnt login so restarted. Then tried again and
  the update failed again and raised this link to complet the bug
  report. My guess would be its connected to the KiCAD update so will
  try uninstalling KiCAD.

  Thanks

  Dave H

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-software-properties 0.96.20.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 15:24:30 2017
  DuplicateSignature:
   package:python3-software-properties:0.96.20.6
   Unpacking kicad-library (201705230749+1258~3~ubuntu16.04.1) over 
(201705161649+1252~3~ubuntu16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kicad-library_201705230749+1258~3~ubuntu16.04.1_all.deb 
(--unpack):
unable to install new version of 
'/usr/share/kicad/modules/packages3d/NF-Transformers_ETAL.3dshapes/NF-Transformer_P3181_ETAL_HandSoldering.wrl':
 No such file or directory
  ErrorMessage: subprocess new pre-removal script returned error exit status 139
  InstallationDate: Installed on 2016-11-30 (174 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.20.6 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-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,

[Touch-packages] [Bug 1692910] [NEW] package python3-software-properties 0.96.20.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139

2017-05-23 Thread Dave H

Public bug reported:

Hi, tried to run an update. The main files were related to python and
KiCAD. During installation of KiCAD the PC crashed and returned to the
purle login screen. I couldnt login so restarted. Then tried again and
the update failed again and raised this link to complet the bug report.
My guess would be its connected to the KiCAD update so will try
uninstalling KiCAD.

Thanks

Dave H

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-software-properties 0.96.20.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue May 23 15:24:30 2017
DuplicateSignature:
 package:python3-software-properties:0.96.20.6
 Unpacking kicad-library (201705230749+1258~3~ubuntu16.04.1) over 
(201705161649+1252~3~ubuntu16.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/kicad-library_201705230749+1258~3~ubuntu16.04.1_all.deb 
(--unpack):
  unable to install new version of 
'/usr/share/kicad/modules/packages3d/NF-Transformers_ETAL.3dshapes/NF-Transformer_P3181_ETAL_HandSoldering.wrl':
 No such file or directory
ErrorMessage: subprocess new pre-removal script returned error exit status 139
InstallationDate: Installed on 2016-11-30 (174 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: software-properties
Title: package python3-software-properties 0.96.20.6 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1692910

Title:
  package python3-software-properties 0.96.20.6 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 139

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hi, tried to run an update. The main files were related to python and
  KiCAD. During installation of KiCAD the PC crashed and returned to the
  purle login screen. I couldnt login so restarted. Then tried again and
  the update failed again and raised this link to complet the bug
  report. My guess would be its connected to the KiCAD update so will
  try uninstalling KiCAD.

  Thanks

  Dave H

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-software-properties 0.96.20.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 15:24:30 2017
  DuplicateSignature:
   package:python3-software-properties:0.96.20.6
   Unpacking kicad-library (201705230749+1258~3~ubuntu16.04.1) over 
(201705161649+1252~3~ubuntu16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kicad-library_201705230749+1258~3~ubuntu16.04.1_all.deb 
(--unpack):
unable to install new version of 
'/usr/share/kicad/modules/packages3d/NF-Transformers_ETAL.3dshapes/NF-Transformer_P3181_ETAL_HandSoldering.wrl':
 No such file or directory
  ErrorMessage: subprocess new pre-removal script returned error exit status 139
  InstallationDate: Installed on 2016-11-30 (174 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.20.6 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692582] Re: RFE: dbus AppArmor mediation matching by message type

2017-05-23 Thread Simon McVittie

> What time frame are you looking for to land fixes for this

I don't have a specific timeline for this, I just wanted to raise it as
a missing feature before I forgot about it.

I think the project that I wanted this for might be able to work around
the missing feature with rules like

dbus (send,receive) bus=session path=/com/example/MyService/**,
dbus receive bus=session peer=(label=unconfined),

so that unconfined developer/test processes can call Ping() and
Introspect(), all processes can call the service's methods and receive
its signals, but the service can't call methods on (the interesting
object paths of) more-privileged processes like systemd.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1692582

Title:
  RFE: dbus AppArmor mediation matching by message type

Status in apparmor package in Ubuntu:
  New

Bug description:
  Suppose you're writing an AppArmor profile for a D-Bus service like
  Tracker. The service might get compromised (perhaps it's network-
  facing) so you don't want it to be able to act as a client of
  privileged processes like systemd --user. However, imagine you do want
  arbitrary third-party "apps" to be allowed to use the service if they
  have appropriate rules in their own AppArmor profiles.

  One reasonably natural way to encode this without tightly coupling the
  service and its clients would be:

  profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
  }

  profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
  }

  However, the AppArmor integration in src:dbus and the rule parser in
  src:apparmor don't allow this: they match fine-grained information
  like the method name and object path, but have no concept of message
  types. This seems backwards: I only expect the object path to be
  useful in very rare/niche cases, but the message type is "larger" and
  more important than anything else from the message payload.

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

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

[Touch-packages] [Bug 1640784] Re: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1640784

Title:
  package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  fresh install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 10 14:57:54 2016
  DuplicateSignature:
   package:unattended-upgrades:0.90ubuntu0.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package unattended-upgrades (--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-11-10 (0 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1640784/+subscriptions

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

[Touch-packages] [Bug 1692870] Re: gzip compression broken in UniFi (built-in tomcat)