[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

[Launchpad Bug Tracker]

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

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1717992

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 

[Touch-packages] [Bug 1717992] Re: Sound silently plays to "Dummy Output"

[ereli]

my workaround is  running `pulseaudio -k` and restarting Spotify. Chrome
doesn't need a restart to play.

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 
root=/dev/mapper/ubu-root ro quiet splash 

[Touch-packages] [Bug 1728810] Re: CUPS ERRORS

[Launchpad Bug Tracker]

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

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

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

Title:
  CUPS ERRORS

Status in cups package in Ubuntu:
  Expired

Bug description:
  There are problems in my PC about the "Server".-When I am traying to
  use my printer (wireless printer).-An advice apairs as: "failed to
  connect to server".

  I would have your help,thank You in advance.Sincerely Fernando
  Espinosa.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   [  OK  ] Started Network Manager.
Starting Network Manager Wait Online...
   [  OK  ] Reached target Network.
   [  OK  ] Started Unattended Upgrades Shutdown.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct 31 00:32:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] [1002:9809] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Wrestler [Radeon HD 7310] [17aa:365d]
  InstallationDate: Installed on 2016-11-27 (337 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10103
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic 
root=UUID=e9b7906b-8c2c-4887-89be-701551b926e7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EKKT30BUS
  dmi.board.name: Remore CRB
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD EM DPK IPG
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrEKKT30BUS:bd03/05/2013:svnLENOVO:pn10103:pvrLenovoC345:rvnLENOVO:rnRemoreCRB:rvrWin8STDEMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10103
  dmi.product.version: Lenovo C345
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 30 16:40:55 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1728810/+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 1730365] Re: pulseaudio keeps crashing and the audiom drops out

[Launchpad Bug Tracker]

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

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

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

Title:
  pulseaudio keeps crashing and the audiom drops out

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  1). 21:48:17 ⌂197% grizzlysmit@killashandra:~ 4m23s $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  21:54:30 ⌂217% grizzlysmit@killashandra:~ 2s $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  2).  $ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:10.0-2ubuntu3
Candidate: 1:10.0-2ubuntu3
Version table:
   *** 1:10.0-2ubuntu3 500
  500 http://au.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  3). I expected pulse to just keep running like it always did under
  previous releases of Ubuntu

  4). It keeps dropping out after a day or so no sound and settings
  (gnome-control-center sound) to it cannot connect to it running
  pulseaudio& in a shell fixes it

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 21:44:08 2017
  InstallationDate: Installed on 2017-07-24 (104 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-10-20 (16 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0G261D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0G261D:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1730365/+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 1741398] Re: Commented line in sudoers file breaks sudo

[Plutocrat]

Wow, OK apologies for wasting everyone's time in that case but I have to
say that its pretty confusing. Even within the sudoers file there are
comments prefixed by a hash. But if your comment happens to start with
#include it magically becomes active.

I now understand this is the intended behaviour, but in that case I'd
humbly suggest that there should be another, better way of doing
includes.

Also, perhaps visudo should throw an error when it finds an #include
that doesn't exist, rather than just exiting and then sudo refusing to
do anything.

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

Title:
  Commented line in sudoers file breaks sudo

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.04 Amazon AWS image. 
  sudo:
Installed: 1.8.16-0ubuntu1.5

  Used sudo visudo to edit /etc/sudoers file from the ubutntu admin user

  At the bottom of the file is a line

  #includedir /etc/sudoers.d

  I added a couple of lines at the end of the file to give permissions
  to another user. I accidentally hit backspace and altered the
  includedir line so it looked like this

  #includedir /etc/sudoercs

  I couldn't remember what the actual directory was at the time, but I
  thought, hey, its a commented line, it doesn't matter anyway. I was
  wrong.

  So visudo saved the file OK, but from then on, no valid sudo commands
  would work for any user. Including sudo visudo of course. Its an AWS
  instance, so no root login. Only recourse was to detach the volume,
  re-attach it to another instance, fix the spelling mistake.

  So obviously sudo freaked when the directory given didn't exist. But
  why would it, if the line is a comment? Something obviously wrong
  here. And given the lack of root, a particularly irritating and time
  consuming one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1741398/+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 1741591] [NEW] PCI/internal sound card not detected

[Freedomlover]

Public bug reported:

I have an HP 15-CC129TX Laptop with Intel Corporation Sunrise Point-LP
HD Audio. But Ubuntu 17.10 is not detecting my sound card and is
displaying dummy output in my sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan  6 09:07:37 2018
InstallationDate: Installed on 2018-01-05 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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: 08/25/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83F9
dmi.board.vendor: HP
dmi.board.version: 46.40
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have an HP 15-CC129TX Laptop with Intel Corporation Sunrise Point-LP
  HD Audio. But Ubuntu 17.10 is not detecting my sound card and is
  displaying dummy output in my sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  6 09:07:37 2018
  InstallationDate: Installed on 2018-01-05 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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: 08/25/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1741591/+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 1741584] [NEW] comments in variables

[Seth Arnold]

Public bug reported:

Nibaldo González discovered that AppArmor parses variable assignments
differently than many other lines and includes #comments if they are on
the same line in a surprising fashion:

https://lists.ubuntu.com/archives/apparmor/2018-January/011418.html

> 24|   @{libreoffice_ext} = [tT][xX][tT]  #.txt
> 25|   @{libreoffice_ext} += {,f,F}[oO][dDtT][tTsSpPbBgGfF]  #All the open
> document format
...

$ apparmor_parser -Qd < foo  | grep '#'
Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
Mode:   rwak:   Name:   
({/home//*,/root,/mnt,/media}/**.{[tT][xX][tT],#.txt,{,f,F}[oO][dDtT][tTsSpPbBgGfF],#All,the,open,document,format,[xX][mMsS][lL],#.xml,and,xsl,[pP][dD][fF],#.pdf,[uU][oO][fFtTsSpP],#Unified,office,format,{,x,X}[hH][tT][mM]{,l,L},#(x)htm(l),[jJ][pP][gG],[jJ][pP][eE][gG],[pP][nN][gG],[sS][vV][gG],[sS][vV][gG][zZ]99251,[tT][iI][fF],[tT][iI][fF][fF],[dD][oO][cCtT]{,x,X},[rR][tT][fF],[xX][lL][sSwWtT]{,x,X},[dD][iIbB][fF],#.dif,dbf,[cCtT][sS][vV],#.tsv,.csv,[sS][lL][kK],[pP][pP][tTsS]{,x,X},[pP][oO][tT]{,m,M},[sS][wW][fF],#Flash,[pP][sS][dD],#Photoshop,[mM][mM][lL]})

I've filed a bug for this profile but perhaps the solution should be to
modify the AppArmor parser instead:

https://bugs.launchpad.net/ubuntu/+source/libreoffice-l10n/+bug/1741581

Thanks

** Affects: apparmor
 Importance: Undecided
 Status: New

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

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

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

Title:
  comments in variables

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Nibaldo González discovered that AppArmor parses variable assignments
  differently than many other lines and includes #comments if they are
  on the same line in a surprising fashion:

  https://lists.ubuntu.com/archives/apparmor/2018-January/011418.html

  > 24|   @{libreoffice_ext} = [tT][xX][tT]  #.txt
  > 25|   @{libreoffice_ext} += {,f,F}[oO][dDtT][tTsSpPbBgGfF]  #All the open
  > document format
  ...

  $ apparmor_parser -Qd < foo  | grep '#'
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Mode:   rwak:   Name:   
({/home//*,/root,/mnt,/media}/**.{[tT][xX][tT],#.txt,{,f,F}[oO][dDtT][tTsSpPbBgGfF],#All,the,open,document,format,[xX][mMsS][lL],#.xml,and,xsl,[pP][dD][fF],#.pdf,[uU][oO][fFtTsSpP],#Unified,office,format,{,x,X}[hH][tT][mM]{,l,L},#(x)htm(l),[jJ][pP][gG],[jJ][pP][eE][gG],[pP][nN][gG],[sS][vV][gG],[sS][vV][gG][zZ]99251,[tT][iI][fF],[tT][iI][fF][fF],[dD][oO][cCtT]{,x,X},[rR][tT][fF],[xX][lL][sSwWtT]{,x,X},[dD][iIbB][fF],#.dif,dbf,[cCtT][sS][vV],#.tsv,.csv,[sS][lL][kK],[pP][pP][tTsS]{,x,X},[pP][oO][tT]{,m,M},[sS][wW][fF],#Flash,[pP][sS][dD],#Photoshop,[mM][mM][lL]})

  I've filed a bug for this profile but perhaps the solution should be
  to modify the AppArmor parser instead:

  https://bugs.launchpad.net/ubuntu/+source/libreoffice-
  l10n/+bug/1741581

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1741584/+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 1741579] [NEW] Wrong/confuse text on shutdown at unattended-upgrades

[ITEAS]

Public bug reported:

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades-0.90ubuntu0.9
Uname: 4.4.0-104-generic #127-Ubuntu SMP
Architecture: amd64

I've german systems, so when updates will be installed at shutdown this
text will be displayed at the screen.

German:
"unattended upgrade läuft während des herunterfahrens weiter, es wird fünf 
Sekunden lange gewartet"

English:
"unattended upgrade runs during the shutdown, it waits for five seconds"

This sentence make absolutly no sence for me. Maybe it is an 
translationproblem? Don't know text on the english ubuntuversion. 
The problem is that some customer turned of some computers, because the updates 
need more time then 5 seconds ;)

A better message will that was Windows10 displays at shutdown ...don't
turn off the computer, updates will be installed...

Thanks and best Reagards

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update upgrade

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

Title:
  Wrong/confuse text on shutdown at unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades-0.90ubuntu0.9
  Uname: 4.4.0-104-generic #127-Ubuntu SMP
  Architecture: amd64

  I've german systems, so when updates will be installed at shutdown
  this text will be displayed at the screen.

  German:
  "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf 
Sekunden lange gewartet"

  English:
  "unattended upgrade runs during the shutdown, it waits for five seconds"

  This sentence make absolutly no sence for me. Maybe it is an 
translationproblem? Don't know text on the english ubuntuversion. 
  The problem is that some customer turned of some computers, because the 
updates need more time then 5 seconds ;)

  A better message will that was Windows10 displays at shutdown ...don't
  turn off the computer, updates will be installed...

  Thanks and best Reagards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1741579/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

[Zeppe]

Im still experiencing this problem on Ubuntu 17.10 (very infrequently).
I'm getting:

[pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport
/org/bluez/hci0/dev_00_0C_8A_86_6A_94/fd0 (Operation Not Authorized)

often even in between 2 videos on youtube. This will freeze any video
playing btw. I can resolve with  `pulseaudio -k` and repairing the
bluetooth device.

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

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

Status in bluez package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released

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

  Ubuntu Xenial 16.04 LTS

  The log below:

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


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

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

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

-- 
Mailing list: https://launchpad.net/~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 1733700] Re: python tools do not understand 'non-magic' include rules

[Jamie Strandboge]

** Changed in: apparmor (Ubuntu Artful)
   Status: Triaged => In Progress

** Changed in: apparmor (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: apparmor (Ubuntu Trusty)
   Status: Triaged => In Progress

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

Title:
  python tools do not understand 'non-magic' include rules

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  In Progress
Status in apparmor source package in Xenial:
  In Progress
Status in apparmor source package in Zesty:
  Triaged
Status in apparmor source package in Artful:
  In Progress
Status in apparmor source package in Bionic:
  In Progress

Bug description:
  The apparmor parser supports 'include' and '#include' rules for
  specifying absolute paths, but the python tools only understand
  include rules for so called 'magic' '<>' file locations.

  = test case #0 (testsuite) =
  $ sudo apt-get install apparmor apparmor-utils # from proposed
  $ sudo apt-get build-dep apparmor
  $ sudo apt-get install quilt realpath pyflakes pyflakes3 # pyflakes3 on 
xenial and higher
  $ apt-get source apparmor # from proposed
  $ cd apparmor-*
  $ quilt push -a
  $ export PYTHONPATH=$(realpath libraries/libapparmor/swig/python)
  $ export PYTHON=/usr/bin/python3
  $ export PYTHON_VERSION=3
  $ export PYTHON_VERSIONS=python3
  $ cd libraries/libapparmor
  $ sh ./autogen.sh
  $ sh ./configure --prefix=/usr --with-perl --with-python
  $ make
  $ cd ../../binutils
  $ make
  $ ../parser
  $ make
  $ cd ../utils
  $ make
  $ make check

  = test case #1 (aa-enforce) =

  This assumes test case #0 has been performed.

  $ mkdir /tmp/test1 /tmp/test2

  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
    #include "/tmp/test1"
    include "/tmp/test2"
  }

  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok

  $ sudo aa-enforce /etc/apparmor.d/lp1733700 # currently fails

  = test case #2 (aa-genprof) =

  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.

  $ cat /tmp/lp1733700
  #!/bin/sh
  set -e
  sh -c "$@"

  $ chmod 755 /tmp/lp1733700

  # run without confinement:
  $ /tmp/lp1733700 'cat /etc/fstab' | head -1
  # /etc/fstab: static file system information.

  # invoke genprof
  $ sudo aa-genprof /tmp/lp1733700
  ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 's' - currently 
fails
  ... don't exercise the application any so we just have the default profile ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 'f'
  ...
  Finished generating profile for /tmp/lp1733700.

  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 15:53:07 2017
  #include 

  /tmp/lp1733700 {
    #include 
    #include 

    /bin/dash ix,
    /lib/x86_64-linux-gnu/ld-*.so mr,
    /tmp/lp1733700 r,

  }

  = test case #3 (aa-logprof) =

  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.

  This also assumes test case #2 was already performed and
  /etc/apparmor.d/tmp.lp1733700 exists.

  Disable kernel rate limiting:
  $ sudo sysctl -w kernel.printk_ratelimit=0

  Create mark entry in syslog:
  $ logger mark-lp1733700

  Try running logprof with no new denials:

  $ sudo aa-logprof -m mark-lp1733700   # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  $

  Adjust /etc/apparmor.d/tmp.lp1733700 to add:

    #include "/tmp/test1"
    include "/tmp/test2"

  Load it into the kernel:
  $ sudo apparmor_parser -r /etc/apparmor.d/tmp.lp1733700

  Create a new denial:
  $ /tmp/lp1733700 'uptime'
  sh: 1: uptime: Permission denied
  $

  Try running logprof:

  $ sudo aa-logprof -m mark-lp1733700 # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.

  Profile:  /tmp/lp1733700
  Execute:  /usr/bin/uptime
  Severity: unknown

  (I)nherit / (C)hild / (N)amed / (X) ix On / (D)eny / Abo(r)t / (F)inish
  ...
  The following local profiles were changed. Would you like to save them?
  
   [1 - /tmp/lp1733700]
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  

  Writing updated profile for /tmp/lp1733700.
  $

  Verify the profile for 'uptime' addition and that the /tmp/test1 and
  /tmp/test2 includes were not removed (it is ok that they are both
  '#include'):

  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 16:19:19 2017
  #include 

  /tmp/lp1733700 {
    #include "/tmp/test1"
    #include "/tmp/test2"
    #include 
    #include 

    /bin/dash ix,
    /lib/x86_64-linux-gnu/ld-*.so mr,
    /tmp/lp1733700 r,
    /usr/bin/uptime mrix,

  }

  = test case #4 

[Touch-packages] [Bug 1733700] Re: python tools do not understand 'non-magic' include rules

[Jamie Strandboge]

** Description changed:

  The apparmor parser supports 'include' and '#include' rules for
  specifying absolute paths, but the python tools only understand include
  rules for so called 'magic' '<>' file locations.
  
  = test case #0 (testsuite) =
  $ sudo apt-get install apparmor apparmor-utils # from proposed
  $ sudo apt-get build-dep apparmor
- $ sudo apt-get install quilt pyflakes pyflakes3 # pyflakes3 on xenial and 
higher
+ $ sudo apt-get install quilt realpath pyflakes pyflakes3 # pyflakes3 on 
xenial and higher
  $ apt-get source apparmor # from proposed
  $ cd apparmor-*
  $ quilt push -a
  $ export PYTHONPATH=$(realpath libraries/libapparmor/swig/python)
  $ export PYTHON=/usr/bin/python3
  $ export PYTHON_VERSION=3
  $ export PYTHON_VERSIONS=python3
  $ cd libraries/libapparmor
  $ sh ./autogen.sh
  $ sh ./configure --prefix=/usr --with-perl --with-python
  $ make
  $ cd ../../binutils
  $ make
  $ ../parser
  $ make
  $ cd ../utils
  $ make
  $ make check
  
  = test case #1 (aa-enforce) =
  
  This assumes test case #0 has been performed.
  
  $ mkdir /tmp/test1 /tmp/test2
  
  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
-   #include "/tmp/test1"
-   include "/tmp/test2"
+   #include "/tmp/test1"
+   include "/tmp/test2"
  }
  
  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
  
  $ sudo aa-enforce /etc/apparmor.d/lp1733700 # currently fails
- 
  
  = test case #2 (aa-genprof) =
  
  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.
  
  $ cat /tmp/lp1733700
  #!/bin/sh
  set -e
  sh -c "$@"
  
  $ chmod 755 /tmp/lp1733700
  
  # run without confinement:
  $ /tmp/lp1733700 'cat /etc/fstab' | head -1
  # /etc/fstab: static file system information.
  
  # invoke genprof
  $ sudo aa-genprof /tmp/lp1733700
  ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 's' - currently 
fails
  ... don't exercise the application any so we just have the default profile ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 'f'
  ...
  Finished generating profile for /tmp/lp1733700.
  
  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 15:53:07 2017
  #include 
  
  /tmp/lp1733700 {
-   #include 
-   #include 
- 
-   /bin/dash ix,
-   /lib/x86_64-linux-gnu/ld-*.so mr,
-   /tmp/lp1733700 r,
- 
- }
- 
+   #include 
+   #include 
+ 
+   /bin/dash ix,
+   /lib/x86_64-linux-gnu/ld-*.so mr,
+   /tmp/lp1733700 r,
+ 
+ }
  
  = test case #3 (aa-logprof) =
  
  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.
  
  This also assumes test case #2 was already performed and
  /etc/apparmor.d/tmp.lp1733700 exists.
  
  Disable kernel rate limiting:
  $ sudo sysctl -w kernel.printk_ratelimit=0
  
  Create mark entry in syslog:
  $ logger mark-lp1733700
  
  Try running logprof with no new denials:
  
  $ sudo aa-logprof -m mark-lp1733700   # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  $
  
  Adjust /etc/apparmor.d/tmp.lp1733700 to add:
  
-   #include "/tmp/test1"
-   include "/tmp/test2"
+   #include "/tmp/test1"
+   include "/tmp/test2"
  
  Load it into the kernel:
  $ sudo apparmor_parser -r /etc/apparmor.d/tmp.lp1733700
  
  Create a new denial:
  $ /tmp/lp1733700 'uptime'
  sh: 1: uptime: Permission denied
  $
  
  Try running logprof:
  
  $ sudo aa-logprof -m mark-lp1733700 # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  
  Profile:  /tmp/lp1733700
  Execute:  /usr/bin/uptime
  Severity: unknown
  
  (I)nherit / (C)hild / (N)amed / (X) ix On / (D)eny / Abo(r)t / (F)inish
  ...
  The following local profiles were changed. Would you like to save them?
  
-  [1 - /tmp/lp1733700]
+  [1 - /tmp/lp1733700]
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  
  
  Writing updated profile for /tmp/lp1733700.
  $
  
  Verify the profile for 'uptime' addition and that the /tmp/test1 and
  /tmp/test2 includes were not removed (it is ok that they are both
  '#include'):
  
  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 16:19:19 2017
  #include 
  
  /tmp/lp1733700 {
-   #include "/tmp/test1"
-   #include "/tmp/test2"
-   #include 
-   #include 
- 
-   /bin/dash ix,
-   /lib/x86_64-linux-gnu/ld-*.so mr,
-   /tmp/lp1733700 r,
-   /usr/bin/uptime mrix,
- 
- }
- 
+   #include "/tmp/test1"
+   #include "/tmp/test2"
+   #include 
+   #include 
+ 
+   /bin/dash ix,
+   /lib/x86_64-linux-gnu/ld-*.so mr,
+   /tmp/lp1733700 r,
+   /usr/bin/uptime mrix,
+ 
+ }
  
  = test case #4 (aa-mergeprof) =
  
  $ mkdir -p /tmp/aa-mergeprof/new
  $ mkdir /tmp/aa-mergeprof/new/tunables /tmp/aa-mergeprof/new/abstractions
  $ touch /tmp/aa-mergeprof/new/tunables/global 
/tmp/aa-mergeprof/new/abstractions/base /tmp/aa-mergeprof/new/abstractions/bash

[Touch-packages] [Bug 1733700] Re: python tools do not understand 'non-magic' include rules

[Jamie Strandboge]

** Description changed:

  The apparmor parser supports 'include' and '#include' rules for
  specifying absolute paths, but the python tools only understand include
  rules for so called 'magic' '<>' file locations.
  
  = test case #0 (testsuite) =
- $ sudo apt-get install apparmor apparmor-utils # not required with 2.12
+ $ sudo apt-get install apparmor apparmor-utils # from proposed
  $ sudo apt-get build-dep apparmor
- $ sudo apt-get install quilt pyflakes pyflakes3
- $ apt-get source apparmor
+ $ sudo apt-get install quilt pyflakes pyflakes3 # pyflakes3 on xenial and 
higher
+ $ apt-get source apparmor # from proposed
  $ cd apparmor-*
  $ quilt push -a
  $ export PYTHONPATH=$(realpath libraries/libapparmor/swig/python)
  $ export PYTHON=/usr/bin/python3
  $ export PYTHON_VERSION=3
  $ export PYTHON_VERSIONS=python3
  $ cd libraries/libapparmor
  $ sh ./autogen.sh
  $ sh ./configure --prefix=/usr --with-perl --with-python
  $ make
  $ cd ../../binutils
  $ make
  $ ../parser
  $ make
  $ cd ../utils
  $ make
  $ make check
  
  = test case #1 (aa-enforce) =
+ 
+ This assumes test case #0 has been performed.
+ 
  $ mkdir /tmp/test1 /tmp/test2
  
  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
#include "/tmp/test1"
include "/tmp/test2"
  }
  
  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
  
  $ sudo aa-enforce /etc/apparmor.d/lp1733700 # currently fails
  
  
  = test case #2 (aa-genprof) =
  
  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.
  
  $ cat /tmp/lp1733700
  #!/bin/sh
  set -e
  sh -c "$@"
  
  $ chmod 755 /tmp/lp1733700
  
  # run without confinement:
  $ /tmp/lp1733700 'cat /etc/fstab' | head -1
  # /etc/fstab: static file system information.
  
  # invoke genprof
  $ sudo aa-genprof /tmp/lp1733700
  ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 's' - currently 
fails
  ... don't exercise the application any so we just have the default profile ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 'f'
  ...
  Finished generating profile for /tmp/lp1733700.
  
  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 15:53:07 2017
  #include 
  
  /tmp/lp1733700 {
#include 
#include 
  
/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
  
  }
  
  
  = test case #3 (aa-logprof) =
  
  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.
  
  This also assumes test case #2 was already performed and
  /etc/apparmor.d/tmp.lp1733700 exists.
  
  Disable kernel rate limiting:
  $ sudo sysctl -w kernel.printk_ratelimit=0
  
  Create mark entry in syslog:
  $ logger mark-lp1733700
  
  Try running logprof with no new denials:
  
  $ sudo aa-logprof -m mark-lp1733700   # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  $
  
  Adjust /etc/apparmor.d/tmp.lp1733700 to add:
  
#include "/tmp/test1"
include "/tmp/test2"
  
  Load it into the kernel:
  $ sudo apparmor_parser -r /etc/apparmor.d/tmp.lp1733700
  
  Create a new denial:
  $ /tmp/lp1733700 'uptime'
  sh: 1: uptime: Permission denied
  $
  
  Try running logprof:
  
  $ sudo aa-logprof -m mark-lp1733700 # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  
  Profile:  /tmp/lp1733700
  Execute:  /usr/bin/uptime
  Severity: unknown
  
  (I)nherit / (C)hild / (N)amed / (X) ix On / (D)eny / Abo(r)t / (F)inish
  ...
  The following local profiles were changed. Would you like to save them?
  
   [1 - /tmp/lp1733700]
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  
  
  Writing updated profile for /tmp/lp1733700.
  $
  
  Verify the profile for 'uptime' addition and that the /tmp/test1 and
  /tmp/test2 includes were not removed (it is ok that they are both
  '#include'):
  
  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 16:19:19 2017
  #include 
  
  /tmp/lp1733700 {
#include "/tmp/test1"
#include "/tmp/test2"
#include 
#include 
  
/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
/usr/bin/uptime mrix,
  
  }
  
  
  = test case #4 (aa-mergeprof) =
  
  $ mkdir -p /tmp/aa-mergeprof/new
  $ mkdir /tmp/aa-mergeprof/new/tunables /tmp/aa-mergeprof/new/abstractions
  $ touch /tmp/aa-mergeprof/new/tunables/global 
/tmp/aa-mergeprof/new/abstractions/base /tmp/aa-mergeprof/new/abstractions/bash
  $ cp -a /tmp/aa-mergeprof/new /tmp/aa-mergeprof/old
  
  $ cat /tmp/aa-mergeprof/old/tmp.lp1733700 # no test2 include or cat
  #include 
  
  /tmp/lp1733700 {
#include 
#include 
#include "/tmp/test1"
  
/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
/usr/bin/uptime mrix,
  
  }
  
  $ cat /tmp/aa-mergeprof/new/tmp.lp1733700 

[Touch-packages] [Bug 1741563] Re: initramfs compression changed in bionic for shipped kernel

[Steve Langasek]

Doesn't sound like an initramfs-tools bug to me.  what is compressing it
with the non-default lzma during the build, and why is that
configuration no longer in place after boot?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  initramfs compression changed in bionic for shipped kernel

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  The shipped initrd doesn't match the compression that you'd get if you
  update the initrd on bionic:

  # A clean bionic cloud-image
  $ file /boot/initrd.img-4.13.0-17-generic
  /boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed

  # Update the initramfs (notice the deprecation warnings too)
  $ sudo update-initramfs -k all -u
  update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic
  WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
deprecated and will stop working in the future. Use 
/etc/cryptsetup-initramfs/conf-hook instead.

  # Now initramfs is gzip compressed when packaged initramfs was LZMA
  $ file /boot/initrd.img-4.13.0-17-generic
  /boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri 
Jan 5 20:54:07 2018, from Unix

  $ apt-cache policy initramfs-tools
  initramfs-tools:
Installed: 0.125ubuntu13
Candidate: 0.125ubuntu13
Version table:
   *** 0.125ubuntu13 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 
Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1741563/+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 1741565] [NEW] package gtk-update-icon-cache (not installed) failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 2

[alberto martinez]

Public bug reported:

I don't know what happend

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gtk-update-icon-cache (not installed)
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.9
AptOrdering:
 gtk-update-icon-cache:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jan  5 14:56:46 2018
DpkgHistoryLog:
 Start-Date: 2018-01-05  14:56:44
 Commandline: apt --fix-broken install
 Requested-By: amartinez (1000)
 Install: gtk-update-icon-cache:amd64 (3.22.11-0ubuntu3, automatic)
ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de 
salida de error 2
InstallationDate: Installed on 2017-03-15 (296 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: gtk+3.0
Title: package gtk-update-icon-cache (not installed) failed to install/upgrade: 
el subproceso script pre-installation nuevo devolvió el código de salida de 
error 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1741565

Title:
  package gtk-update-icon-cache (not installed) failed to
  install/upgrade: el subproceso script pre-installation nuevo devolvió
  el código de salida de error 2

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I don't know what happend

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gtk-update-icon-cache (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.9
  AptOrdering:
   gtk-update-icon-cache:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jan  5 14:56:46 2018
  DpkgHistoryLog:
   Start-Date: 2018-01-05  14:56:44
   Commandline: apt --fix-broken install
   Requested-By: amartinez (1000)
   Install: gtk-update-icon-cache:amd64 (3.22.11-0ubuntu3, automatic)
  ErrorMessage: el subproceso script pre-installation nuevo devolvió el código 
de salida de error 2
  InstallationDate: Installed on 2017-03-15 (296 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: gtk+3.0
  Title: package gtk-update-icon-cache (not installed) failed to 
install/upgrade: el subproceso script pre-installation nuevo devolvió el código 
de salida de error 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1741565/+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 1741563] [NEW] initramfs compression changed in bionic for shipped kernel

[Robert C Jennings]

Public bug reported:

The shipped initrd doesn't match the compression that you'd get if you
update the initrd on bionic:

# A clean bionic cloud-image
$ file /boot/initrd.img-4.13.0-17-generic
/boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed

# Update the initramfs (notice the deprecation warnings too)
$ sudo update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
deprecated and will stop working in the future. Use 
/etc/cryptsetup-initramfs/conf-hook instead.

# Now initramfs is gzip compressed when packaged initramfs was LZMA
$ file /boot/initrd.img-4.13.0-17-generic
/boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri 
Jan 5 20:54:07 2018, from Unix

$ apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.125ubuntu13
  Candidate: 0.125ubuntu13
  Version table:
 *** 0.125ubuntu13 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 
Packages
100 /var/lib/dpkg/status

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

Title:
  initramfs compression changed in bionic for shipped kernel

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  The shipped initrd doesn't match the compression that you'd get if you
  update the initrd on bionic:

  # A clean bionic cloud-image
  $ file /boot/initrd.img-4.13.0-17-generic
  /boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed

  # Update the initramfs (notice the deprecation warnings too)
  $ sudo update-initramfs -k all -u
  update-initramfs: Generating /boot/initrd.img-4.13.0-17-generic
  WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
deprecated and will stop working in the future. Use 
/etc/cryptsetup-initramfs/conf-hook instead.

  # Now initramfs is gzip compressed when packaged initramfs was LZMA
  $ file /boot/initrd.img-4.13.0-17-generic
  /boot/initrd.img-4.13.0-17-generic: gzip compressed data, last modified: Fri 
Jan 5 20:54:07 2018, from Unix

  $ apt-cache policy initramfs-tools
  initramfs-tools:
Installed: 0.125ubuntu13
Candidate: 0.125ubuntu13
Version table:
   *** 0.125ubuntu13 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 
Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1741563/+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 1738565] Re: package linux-image-4.4.0-104-generic 4.4.0-104.127 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Happened while upgrading to 16.04 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic 4.4.0-104.127
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  godwin 2234 F pulseaudio
  Date: Sat Dec 16 23:43:54 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=9f4d8b50-3753-4272-8dfd-fcb4bef3cb49
  InstallationDate: Installed on 2017-07-30 (139 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 15-3552
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic.efi.signed 
root=UUID=98aca646-8215-40a6-9f9c-d87ca9fab141 ro recovery nomodeset
  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-4.4.0-104-generic 4.4.0-104.127 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-12-16 (0 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.0.13
  dmi.board.name: 0M08DC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.0.13:bd12/22/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.13:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3552
  dmi.product.version: 4.0.13
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1738565/+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 1722508] Re: Font hinting appears broken on 17.10 beta

[gldickens3]

Hi Martin,

Thanks for the tip!  Defining the FREETYPE_PROPERTIES as you suggested
in /etc/environment did indeed disable hinting and renders the same
crisper fonts as was in earlier versions of Ubuntu.  Personally, I still
prefer to disable hinting in the source code but your suggestion works
just as well.

Thanks again!

Gordon

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

Title:
  Font hinting appears broken on 17.10 beta

Status in Qt:
  New
Status in freetype package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed
Status in qtbase-opensource-src source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1722508/+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 1741546] [NEW] Dell Inspiron 15 5567 laptops's default speaker does not play the bass in audio

[Ishan]

Public bug reported:

Dell Inspiron 15 5567 comes with Realtek ALC3246 audio chipset.
The sound card is perfect on Windows, very beautiful sound quality and sorround 
sound.
But in ubuntu 16.04 the bass does not play also the sound quality not so 
impressive to hear.

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


** Tags: alsa audio dell

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

Title:
  Dell Inspiron 15 5567 laptops's default speaker does not play the bass
  in audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Dell Inspiron 15 5567 comes with Realtek ALC3246 audio chipset.
  The sound card is perfect on Windows, very beautiful sound quality and 
sorround sound.
  But in ubuntu 16.04 the bass does not play also the sound quality not so 
impressive to hear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1741546/+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 463120] Re: Full laptop speakers are not used to play audio files

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Full laptop speakers are not used to play audio files

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I use a LENOVO Y 500 series laptop, it has a Bass function , which
  fine in windows os. But when playing music files in unbuntu, the sound
  is very low and for some reason the Bass is not activated. The Bass
  switch is on but the is no effect on the volume on the laptop
  speakers. The volume is very low as compared to when i play music in
  Vista. Plzz help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/463120/+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 1438014] Re: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

[Mikhail Kashkin]

I'm also using "Artful Aardwark" got many crashes with different
circumstances.  After some work in the background. When I'm opening and
try to interact:

- Trying to open Preferences
- Trying to right-click on highlighted link to select "Open Link" (crash just 
after right click)
- Trying to switch tab

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

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1438014/+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 1741515] [NEW] units: starting suspend.target should not fail when suspend is succesful

[Steffen Sindzinski]

Public bug reported:

Since systemd 233 the behavior of BindsTo is changed which can cause
suspend.target to fail when suspend.service is successful.

Please apply patch:
https://github.com/systemd/systemd/commit/64a36ae4b1dd23474dd7ea261381ac437b24fac2
which is fixing:
https://github.com/systemd/systemd/pull/6678

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


** Tags: systemd

** Tags added: systemd

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

Title:
  units: starting suspend.target should not fail when suspend is
  succesful

Status in systemd package in Ubuntu:
  New

Bug description:
  Since systemd 233 the behavior of BindsTo is changed which can cause
  suspend.target to fail when suspend.service is successful.

  Please apply patch:
  
https://github.com/systemd/systemd/commit/64a36ae4b1dd23474dd7ea261381ac437b24fac2
  which is fixing:
  https://github.com/systemd/systemd/pull/6678

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741515/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

[Brian Murray]

Hello Oliver, or anyone else affected,

Accepted initramfs-tools into artful-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.125ubuntu12.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Also affects: initramfs-tools (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools-ubuntu-core (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Artful:
  New

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

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

[Brian Murray]

Hello Oliver, or anyone else affected,

Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.11 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

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

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Fix Committed
Status in initramfs-tools-ubuntu-core source package in Artful:
  New

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1623125/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[varacanero]

Btw, I experience this issue with Ubuntu 17.10. I tried upgrading
pulseaudio to the bionic version but the problem persists.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[varacanero]

I also spend hours on this issue trying to get a Logitech H800 headset working 
and finally gave up.
It would be at least nice to know what's the problem (pulseaudio ? bluez ? 
Headset ?) and if it's on the roadmap to fix it.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[varacanero]

Also, how to find out which Headsets work and which not, before spending
the money and finding out they don't.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth headset profile HSP/HFP doesn't work

Status in blueman package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP 
profile, but when i try change sound profile in blueman-manager to HSP/HFP - 
then i get error "Failed to change profile to headset_head_unit".
  With profile a2dp headphones work good(clementine, chromium etc..), but I 
could not get work output headphones in steam games, i listen only silence(i 
think it's problem of pulseaudio)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Nov 28 19:51:59 2017
  InstallationDate: Installed on 2016-06-22 (524 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Bluedio
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Bluedio, recording] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
  dmi.bios.date: 07/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L2.38
  dmi.board.name: AM2NF6G-VSTA
  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.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA: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.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1734960/+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 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work

[Launchpad Bug Tracker]

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

** 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1734960

Title:
  Bluetooth headset profile HSP/HFP doesn't work

Status in blueman package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP 
profile, but when i try change sound profile in blueman-manager to HSP/HFP - 
then i get error "Failed to change profile to headset_head_unit".
  With profile a2dp headphones work good(clementine, chromium etc..), but I 
could not get work output headphones in steam games, i listen only silence(i 
think it's problem of pulseaudio)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Nov 28 19:51:59 2017
  InstallationDate: Installed on 2016-06-22 (524 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Bluedio
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Bluedio, recording] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
  dmi.bios.date: 07/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L2.38
  dmi.board.name: AM2NF6G-VSTA
  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.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA: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.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1734960/+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 1737289] Re: Bluetooth profile will not change when selected to enable microphone on headset

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth profile will not change when selected to enable microphone
  on headset

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth headset that supports a2dp as well as HSP/HFP
  profiles.  The headset launches in a2dp and you can select hsp/hfp but
  it never changes the profile and activates the microphone

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sbarcomb   2192 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  8 23:15:07 2017
  InstallationDate: Installed on 2017-10-19 (50 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Stephen s Beats Studio
  Symptom_Type: None of the above
  Title: [Stephen s Beats Studio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2013
  dmi.bios.vendor: Alienware
  dmi.bios.version: A11
  dmi.board.name: 07JNH0
  dmi.board.vendor: Alienware
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
  dmi.product.family: 0
  dmi.product.name: Aurora-R4
  dmi.product.version: 00
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737289/+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 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work

[varacanero]

I think this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559.

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

Title:
  Bluetooth headset profile HSP/HFP doesn't work

Status in blueman package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP 
profile, but when i try change sound profile in blueman-manager to HSP/HFP - 
then i get error "Failed to change profile to headset_head_unit".
  With profile a2dp headphones work good(clementine, chromium etc..), but I 
could not get work output headphones in steam games, i listen only silence(i 
think it's problem of pulseaudio)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Nov 28 19:51:59 2017
  InstallationDate: Installed on 2016-06-22 (524 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Bluedio
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pl7ofit3040 F pulseaudio
   /dev/snd/controlC1:  pl7ofit3040 F pulseaudio
  Symptom_Type: No sound at all
  Title: [Bluedio, recording] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago)
  dmi.bios.date: 07/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L2.38
  dmi.board.name: AM2NF6G-VSTA
  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.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA: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.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1734960/+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 1737289] Re: Bluetooth profile will not change when selected to enable microphone on headset

[varacanero]

I think this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559.

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

Title:
  Bluetooth profile will not change when selected to enable microphone
  on headset

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth headset that supports a2dp as well as HSP/HFP
  profiles.  The headset launches in a2dp and you can select hsp/hfp but
  it never changes the profile and activates the microphone

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sbarcomb   2192 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  8 23:15:07 2017
  InstallationDate: Installed on 2017-10-19 (50 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Stephen s Beats Studio
  Symptom_Type: None of the above
  Title: [Stephen s Beats Studio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2013
  dmi.bios.vendor: Alienware
  dmi.bios.version: A11
  dmi.board.name: 07JNH0
  dmi.board.vendor: Alienware
  dmi.board.version: A02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00:
  dmi.product.family: 0
  dmi.product.name: Aurora-R4
  dmi.product.version: 00
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737289/+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 1692316] Re: can't delete printer

[Dmitry Myachin]

Solving:

sudo /etc/init.d/cups stop
sudo nano -B /etc/cups/printers.conf

Remove printer from .conf

sudo /etc/init.d/cups start

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

Title:
  can't delete printer

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Trying to delete a printer through either system-config-printer or
  http://localhost:631/printers. Both claim that the printer was
  deleted, but it doesn't go away.  Cups logs:

  localhost - root [21/May/2017:08:58:17 -0400] "POST /admin/ HTTP/1.1" 200 103 
- -
  localhost - root [21/May/2017:08:58:17 -0400] "POST /admin/ HTTP/1.1" 200 
2329 - -
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 126 
- -
  localhost - - [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 401 142 
CUPS-Delete-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 142 
CUPS-Delete-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 996 
CUPS-Add-Modify-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 199 
CUPS-Add-Modify-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 
2072 - -

  But again, despite the "CUPS-Delete-Printer-successful-ok", it's not
  actually deleted.

  In system-config-printer, when I try this multiple times, I _might_
  see the printer briefly disappear from the printer listing, but then
  it comes back.

  Other printers I create to test what's going on here, I am able to
  delete. Just not this one.

  I will attach my /etc/cups/printers.conf.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun May 21 08:58:32 2017
  InstallationDate: Installed on 2016-01-16 (491 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  KernLog: [950067.827005] audit: type=1400 audit(1495370264.565:45): 
apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" 
name="/run/systemd/journal/socket" pid=18730 comm="evince" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=0
  Lpstat:
   device for duplex: socket://m551dn:9100
   device for HP-LaserJet-500-color-M551: ipp://m551dn.local:631/ipp/print
   device for simplex: socket://m551dn:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   duplex: HP LaserJet 500 color M551 Postscript (recommended)
   simplex: HP LaserJet 500 color M551 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (36 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1692316/+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 1692316] Re: can't delete printer

[Launchpad Bug Tracker]

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

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

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

Title:
  can't delete printer

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Trying to delete a printer through either system-config-printer or
  http://localhost:631/printers. Both claim that the printer was
  deleted, but it doesn't go away.  Cups logs:

  localhost - root [21/May/2017:08:58:17 -0400] "POST /admin/ HTTP/1.1" 200 103 
- -
  localhost - root [21/May/2017:08:58:17 -0400] "POST /admin/ HTTP/1.1" 200 
2329 - -
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 126 
- -
  localhost - - [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 401 142 
CUPS-Delete-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 142 
CUPS-Delete-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 996 
CUPS-Add-Modify-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 199 
CUPS-Add-Modify-Printer successful-ok
  localhost - root [21/May/2017:08:58:18 -0400] "POST /admin/ HTTP/1.1" 200 
2072 - -

  But again, despite the "CUPS-Delete-Printer-successful-ok", it's not
  actually deleted.

  In system-config-printer, when I try this multiple times, I _might_
  see the printer briefly disappear from the printer listing, but then
  it comes back.

  Other printers I create to test what's going on here, I am able to
  delete. Just not this one.

  I will attach my /etc/cups/printers.conf.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun May 21 08:58:32 2017
  InstallationDate: Installed on 2016-01-16 (491 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  KernLog: [950067.827005] audit: type=1400 audit(1495370264.565:45): 
apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" 
name="/run/systemd/journal/socket" pid=18730 comm="evince" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=0
  Lpstat:
   device for duplex: socket://m551dn:9100
   device for HP-LaserJet-500-color-M551: ipp://m551dn.local:631/ipp/print
   device for simplex: socket://m551dn:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   duplex: HP LaserJet 500 color M551 Postscript (recommended)
   simplex: HP LaserJet 500 color M551 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (36 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1692316/+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 1741481] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une err

[KAORE Jean Marie]

Public bug reported:

when i try to update

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Fri Jan  5 14:09:58 2018
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
InstallationDate: Installed on 2018-01-05 (0 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
IpRoute:
 default via 192.168.109.1 dev enp1s0 proto dhcp src 192.168.109.111 metric 100 
 192.168.109.0/24 dev enp1s0 proto kernel scope link src 192.168.109.111 
 192.168.109.1 dev enp1s0 proto dhcp scope link src 192.168.109.111 metric 100
IwConfig:
 lono wireless extensions.
 
 enp1s0no wireless extensions.
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
RfKill:
 
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: le sous-processus script post-installation installé a 
retourné une erreur de sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: 
Error: NetworkManager is not running.

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


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: le sous-processus script post-installation
  installé a retourné une erreur de sortie d'état 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  when i try to update

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Jan  5 14:09:58 2018
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2018-01-05 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IpRoute:
   default via 192.168.109.1 dev enp1s0 proto dhcp src 192.168.109.111 metric 
100 
   192.168.109.0/24 dev enp1s0 proto kernel scope link src 192.168.109.111 
   192.168.109.1 dev enp1s0 proto dhcp scope link src 192.168.109.111 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: le sous-processus script post-installation installé 
a retourné une erreur de sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1741481/+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 1741480] [NEW] package libapt-pkg5.0:amd64 1.2.15ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[Asaf Malin]

Public bug reported:

install failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libapt-pkg5.0:amd64 1.2.15ubuntu0.2
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 libapt-pkg5.0: Configure
 hspell: Install
 hspell: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jan  5 15:21:17 2018
DpkgHistoryLog:
 Start-Date: 2018-01-05  15:21:17
 Commandline: apt install hspell
 Requested-By: asaf (1000)
 Install: hspell:amd64 (1.2-3)
DpkgTerminalLog:
 dpkg: error processing package libapt-pkg5.0:amd64 (--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-10-28 (68 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: apt
Title: package libapt-pkg5.0:amd64 1.2.15ubuntu0.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)

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

Title:
  package libapt-pkg5.0:amd64 1.2.15ubuntu0.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apt package in Ubuntu:
  New

Bug description:
  install failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libapt-pkg5.0:amd64 1.2.15ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libapt-pkg5.0: Configure
   hspell: Install
   hspell: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jan  5 15:21:17 2018
  DpkgHistoryLog:
   Start-Date: 2018-01-05  15:21:17
   Commandline: apt install hspell
   Requested-By: asaf (1000)
   Install: hspell:amd64 (1.2-3)
  DpkgTerminalLog:
   dpkg: error processing package libapt-pkg5.0:amd64 (--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-10-28 (68 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apt
  Title: package libapt-pkg5.0:amd64 1.2.15ubuntu0.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/apt/+bug/1741480/+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 1741468] Re: Broken GUI in Ubuntu MATE Live Session

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1741468

** Tags added: iso-testing

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

Title:
  Broken GUI in Ubuntu MATE Live Session

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: MacBook Air, late 2013

  
  -The toolbar on the top and the bottom loads, but they seem to be images only.

  -I cannot click on the Applications, Places, System, Firefox, or MATE
  Welcome, nor the power button on the top bar.

  -The Bottom bar's show desktop and switch desktop does not click
  either.

  -My cursor shows and tracks, but it does not seem to register clicks.
  This is both with a mouse and a trackpad.

  -Background image is black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741468/+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 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

[Andreas Hasenack]

That is expected, see comment #8. Unless your apt operation exited with
a status code other than zero, i.e., apt or dpkg actually finished with
an error.

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

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1741473] [NEW] package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:

[Welton]

Public bug reported:

automatic login

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdrm-common 2.4.83-1~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jan  3 15:20:41 2018
Dependencies:
 
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgTerminalLog:
 A preparar para desempacotar .../libdrm-common_2.4.83-1~16.04.1_all.deb ...
 A descompactar libdrm-common (2.4.83-1~16.04.1) ...
 dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libdrm-common_2.4.83-1~16.04.1_all.deb (--unpack):
  a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no 
pacote libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1
ErrorMessage: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que 
também está no pacote libdrm-amdgpu1:amd64 
2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1
GraphicsCard:
 Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [8086:2042]
 NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828]
InstallationDate: Installed on 2017-04-10 (269 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=2ecae89c-893b-4efc-b110-7c907b246eb6 ro quiet splash nomodeset 
acpi_osi=Linux vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: libdrm
Title: package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a 
tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote 
libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: HOH6110H.86A.0011.2012.0530.1036
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61HO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG62445-103
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0011.2012.0530.1036:bd05/30/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-103:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jan  5 10:45:50 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input USB OPTICAL MOUSE   MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-package compiz-0.9 possible-manual-nvidia-install ubuntu 
xenial

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

Title:
  package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a
  tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está
  no pacote 

[Touch-packages] [Bug 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

[dino99]

** Attachment added: "log.wb-BUILTIN"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+attachment/5031483/+files/log.wb-BUILTIN

** Changed in: samba (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/1658273

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

[dino99]

oem@lapubu:~$ ls -l /etc/systemd/system/samba-ad-dc.service
lrwxrwxrwx 1 root root 9 oct.  16  2016 /etc/systemd/system/samba-ad-dc.service 
-> /dev/null

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

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

[dino99]

Got again that error on upgrading Artful:

Setting samba (2:4.6.7+dfsg-1ubuntu3.1) ...
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

Looking at '/etc/systemd/system/samba-ad-dc.service' , nautilus says
'unknown link', and the file's property shows : pointing to /dev/null
(size = 0)


** Attachment added: "log.nmbd"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+attachment/5031481/+files/log.nmbd

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

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

[dino99]

** Attachment added: "log.smbd"
   
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+attachment/5031482/+files/log.smbd

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

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1741468] [NEW] Broken GUI in Ubuntu MATE Live Session

[Jacob Kim]

Public bug reported:

Device: MacBook Air, late 2013


-The toolbar on the top and the bottom loads, but they seem to be images only.

-I cannot click on the Applications, Places, System, Firefox, or MATE
Welcome, nor the power button on the top bar.

-The Bottom bar's show desktop and switch desktop does not click either.

-My cursor shows and tracks, but it does not seem to register clicks.
This is both with a mouse and a trackpad.

-Background image is black.

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

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

Title:
  Broken GUI in Ubuntu MATE Live Session

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: MacBook Air, late 2013

  
  -The toolbar on the top and the bottom loads, but they seem to be images only.

  -I cannot click on the Applications, Places, System, Firefox, or MATE
  Welcome, nor the power button on the top bar.

  -The Bottom bar's show desktop and switch desktop does not click
  either.

  -My cursor shows and tracks, but it does not seem to register clicks.
  This is both with a mouse and a trackpad.

  -Background image is black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741468/+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 1741398] Re: Commented line in sudoers file breaks sudo

[Marc Deslauriers]

Hi, Thanks for reporting this issue, but that is not a comment at all.

>From the sudoers man page:

 It is possible to include other sudoers files from within the sudoers
 file currently being parsed using the #include and #includedir direc‐
 tives.

While # is used in some applications to indicate the start of a comment,
it is not the case in the sudoers file. It's also not the case in other
situations too, for example, in a C file.

I am closing this bug.

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

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

Title:
  Commented line in sudoers file breaks sudo

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.04 Amazon AWS image. 
  sudo:
Installed: 1.8.16-0ubuntu1.5

  Used sudo visudo to edit /etc/sudoers file from the ubutntu admin user

  At the bottom of the file is a line

  #includedir /etc/sudoers.d

  I added a couple of lines at the end of the file to give permissions
  to another user. I accidentally hit backspace and altered the
  includedir line so it looked like this

  #includedir /etc/sudoercs

  I couldn't remember what the actual directory was at the time, but I
  thought, hey, its a commented line, it doesn't matter anyway. I was
  wrong.

  So visudo saved the file OK, but from then on, no valid sudo commands
  would work for any user. Including sudo visudo of course. Its an AWS
  instance, so no root login. Only recourse was to detach the volume,
  re-attach it to another instance, fix the spelling mistake.

  So obviously sudo freaked when the directory given didn't exist. But
  why would it, if the line is a comment? Something obviously wrong
  here. And given the lack of root, a particularly irritating and time
  consuming one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1741398/+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 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.

[dino99]

** Tags added: artful

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

Title:
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
  dc.service is masked.

Status in samba package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  On a standalone desktop running zesty with a gnome-shell session, when
  upgrading the samba packages, i get:

  Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
  Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is 
masked.
  /usr/bin/deb-systemd-helper: error: systemctl preset failed on 
samba-ad-dc.service: No such file or directory

  note: ubuntu-bug ask questions about a possible windows relationship,
  but there is no option for a standalone system like that one; so as
  samba is installed to satisfy qemu, these questions completly ignore
  such case and send inappropriate report.

   and smbd still crashing on cold boot ( lp:1658293 ) (standalone
  desktop)

  note2: a more recent Debian version seems workaround that output:
  samba (2:4.4.5+dfsg-3)
  [ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
  Closes: #832352
  and samba (2:4.4.6+dfsg-1)
  Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
  ctdb.service) Closes: #838000.
  and samba (2:4.4.6+dfsg-2) 
* Remove uses of tevent internals. This fixes segfault.
  Closes: #840382, #840298.
  
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog

  ... time to get package synced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1718771] Re: Incorrect handling of link-local IPv6 DNS servers

[Dimitri John Ledkov]

Digging into this, there appears to be intent to support such DNS
servers. E.g.:

https://github.com/systemd/systemd/commit/2817157bb705e0f3e9ad4a83246a80d026866be3

However, need to check if all fe80:: dns servers are properly qualified
and have the ifindex set on them.

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

Title:
  Incorrect handling of link-local IPv6 DNS servers

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  We've recently seen odd looking DNS failures on autopkgtest:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/d/docker.io/20170921_065231_181b8@/log.gz

  This shows a fe80:: link-local IPv6 address as one of the DNS servers
  on the interface. That's because dnsmasq includes both the link-local
  and global addresses of its DNS server in the router advertisement.

  systemd-networkd appears to pick that up and send it to resolved,
  which includes it in its config but apparently doesn't know how to
  actually query it, leading to the failure above.

  
  This is racy because once DHCPv4 completes, the resolved config will then 
work properly again.

  
  I've confirmed that dnsmasq properly answers on all addresses:
http://paste.ubuntu.com/25588197/

  
  I've uploaded a workaround for this issue as part of the docker.io package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718771/+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 1725333] Re: do-release-upgrade broke WSL

[Bug Watch Updater]

** Changed in: gnubash
   Status: New => Fix Released

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

Title:
  do-release-upgrade broke WSL

Status in Gnu Bash:
  Fix Released
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1725333/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

[Michael Vogt]

I uploaded updates for zesty and artful now as well.

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1623125/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

[Michael Vogt]

It is like ogra said - the snapd team does not care about zesty/artful,
but if it makes the SRU easier we are happy to push to zesty/artful as
well.

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1623125/+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 1741416] [NEW] package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239

[Christian Uceda]

Public bug reported:

I noticed after a reboot that this was an issue for some reason after
the system tried to upgrade apport:

Start-Date: 2018-01-05  07:44:52
Commandline: /usr/bin/unattended-upgrade
Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), 
python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), apport-gtk:amd64 
(2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-problem-report:amd64 
(2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2018-01-05  07:45:10

I fixed it with:

apt-get dist-upgrade -f

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.15
Uname: Linux 4.14.8-041408-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashReports: 600:0:116:145106:2018-01-05 07:45:09.131217479 +:2018-01-05 
07:45:10.131217479 +:/var/crash/apport.0.crash
Date: Fri Jan  5 07:45:10 2018
DuplicateSignature:
 package:apport:2.20.1-0ubuntu2.15
 Setting up apport (2.20.1-0ubuntu2.15) ...
 Segmentation fault
 dpkg: error processing package apport (--configure):
  subprocess installed post-installation script returned error exit status 239
ErrorMessage: subprocess installed post-installation script returned error exit 
status 239
InstallationDate: Installed on 2017-05-29 (220 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 239
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apport 2.20.1-0ubuntu2.15 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 239

Status in apport package in Ubuntu:
  New

Bug description:
  I noticed after a reboot that this was an issue for some reason after
  the system tried to upgrade apport:

  Start-Date: 2018-01-05  07:44:52
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), 
python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), apport-gtk:amd64 
(2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-problem-report:amd64 
(2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15)
  Error: Sub-process /usr/bin/dpkg returned an error code (1)
  End-Date: 2018-01-05  07:45:10

  I fixed it with:

  apt-get dist-upgrade -f

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.15
  Uname: Linux 4.14.8-041408-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashReports: 600:0:116:145106:2018-01-05 07:45:09.131217479 +:2018-01-05 
07:45:10.131217479 +:/var/crash/apport.0.crash
  Date: Fri Jan  5 07:45:10 2018
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.15
   Setting up apport (2.20.1-0ubuntu2.15) ...
   Segmentation fault
   dpkg: error processing package apport (--configure):
subprocess installed post-installation script returned error exit status 239
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 239
  InstallationDate: Installed on 2017-05-29 (220 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 239
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741416/+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 1741416] Re: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239

[Apport retracing service]

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

Title:
  package apport 2.20.1-0ubuntu2.15 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 239

Status in apport package in Ubuntu:
  New

Bug description:
  I noticed after a reboot that this was an issue for some reason after
  the system tried to upgrade apport:

  Start-Date: 2018-01-05  07:44:52
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), 
python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), apport-gtk:amd64 
(2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-problem-report:amd64 
(2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15)
  Error: Sub-process /usr/bin/dpkg returned an error code (1)
  End-Date: 2018-01-05  07:45:10

  I fixed it with:

  apt-get dist-upgrade -f

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.15
  Uname: Linux 4.14.8-041408-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashReports: 600:0:116:145106:2018-01-05 07:45:09.131217479 +:2018-01-05 
07:45:10.131217479 +:/var/crash/apport.0.crash
  Date: Fri Jan  5 07:45:10 2018
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.15
   Setting up apport (2.20.1-0ubuntu2.15) ...
   Segmentation fault
   dpkg: error processing package apport (--configure):
subprocess installed post-installation script returned error exit status 239
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 239
  InstallationDate: Installed on 2017-05-29 (220 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 239
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741416/+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