[Touch-packages] [Bug 1696912] Re: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package isc-dhcp-common is not ready for configuration cannot configure (current status 'half-in

[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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1696912

Title:
  package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade:
  package isc-dhcp-common is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  having trouble updating.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-common 4.3.3-5ubuntu12.7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 22:27:25 2017
  Dependencies:
   debianutils 4.7
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   sensible-utils 0.0.9
  DuplicateSignature:
   package:isc-dhcp-common:4.3.3-5ubuntu12.7
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package isc-dhcp-common (--configure):
package isc-dhcp-common is not ready for configuration
  ErrorMessage: package isc-dhcp-common is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-25 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: 
package isc-dhcp-common is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1696912/+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 1696916] [NEW] HDMI Not Detecting

[Deepak Raj Kurrey]

Public bug reported:

I wanted to use the HDMI port provided, but its not being detected by
the Display Manager.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Fri Jun  9 11:06:34 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
 bbswitch, 0.8, 4.10.0-22-generic, x86_64: installed
 virtualbox, 5.1.22, 4.10.0-21-generic, x86_64: installed
 virtualbox, 5.1.22, 4.10.0-22-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
 NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
InstallationDate: Installed on 2017-05-26 (14 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=6720d34d-0396-4e10-870a-ae9a296df10b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 1/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN47WW(V3.08)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 3194STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias: 
dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Jun  9 10:57:11 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty

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

Title:
  HDMI Not Detecting

Status in xorg package in Ubuntu:
  New

Bug description:
  I wanted to use the HDMI port provided, but its not being detected by
  the Display Manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  

[Touch-packages] [Bug 1696912] [NEW] package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: package isc-dhcp-common is not ready for configuration cannot configure (current status 'half-

[Lawrence Isbell]

Public bug reported:

having trouble updating.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-common 4.3.3-5ubuntu12.7
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun  8 22:27:25 2017
Dependencies:
 debianutils 4.7
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
 sensible-utils 0.0.9
DuplicateSignature:
 package:isc-dhcp-common:4.3.3-5ubuntu12.7
 Processing triggers for libc-bin (2.23-0ubuntu7) ...
 dpkg: error processing package isc-dhcp-common (--configure):
  package isc-dhcp-common is not ready for configuration
ErrorMessage: package isc-dhcp-common is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-04-25 (44 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: isc-dhcp
Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: 
package isc-dhcp-common is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade:
  package isc-dhcp-common is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  having trouble updating.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-common 4.3.3-5ubuntu12.7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 22:27:25 2017
  Dependencies:
   debianutils 4.7
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   sensible-utils 0.0.9
  DuplicateSignature:
   package:isc-dhcp-common:4.3.3-5ubuntu12.7
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package isc-dhcp-common (--configure):
package isc-dhcp-common is not ready for configuration
  ErrorMessage: package isc-dhcp-common is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-25 (44 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-common 4.3.3-5ubuntu12.7 failed to install/upgrade: 
package isc-dhcp-common is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1696912/+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 1696910] [NEW] [E402NA, Realtek ALC256, Mic, Internal] Recording problem

[piviul]

Public bug reported:

the builtin microphone doesn't works at all. I have tried to go in
alsamixer to see if the microphone was disabled but alsamixer says: This
sound device does not have any capture controls.

The same happens if I attach a microphone in the jack. Usb microphones
seems to works.

I attach a file generated with checkbox-gui with all test hardware of
the notebooks.

Have a great day

Piviul

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  natascia   1225 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jun  9 07:14:04 2017
InstallationDate: Installed on 2017-06-05 (3 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 :  
 r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
Symptom_Card: Audio interno - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_Type: None of the above
Title: [E402NA, Realtek ALC256, Mic, Internal] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E402NA.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: E402NA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE402NA.304:bd02/24/2017:svnASUSTeKCOMPUTERINC.:pnE402NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: E402NA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug xenial

** Attachment added: "submission_2017-06-09T04:57:14.416551.html"
   
https://bugs.launchpad.net/bugs/1696910/+attachment/4892792/+files/submission_2017-06-09T04%3A57%3A14.416551.html

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

Title:
  [E402NA, Realtek ALC256, Mic, Internal] Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the builtin microphone doesn't works at all. I have tried to go in
  alsamixer to see if the microphone was disabled but alsamixer says:
  This sound device does not have any capture controls.

  The same happens if I attach a microphone in the jack. Usb microphones
  seems to works.

  I attach a file generated with checkbox-gui with all test hardware of
  the notebooks.

  Have a great day

  Piviul

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  natascia   1225 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun  9 07:14:04 2017
  InstallationDate: Installed on 2017-06-05 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Audio interno - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: None of the above
  Title: [E402NA, Realtek ALC256, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E402NA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E402NA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE402NA.304:bd02/24/2017:svnASUSTeKCOMPUTERINC.:pnE402NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E402NA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 

[Touch-packages] [Bug 1663050] Re: Intel 7265 wireless device disconnect: link is not ready

[Launchpad Bug Tracker]

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

** Changed in: linux-hwe (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/1663050

Title:
  Intel 7265 wireless device disconnect: link is not ready

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed

Bug description:
  The wifi device disconnect sometime randomly or sometime when switching 
hotspot with the following dmesg output:
  [ 1039.212949] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.213503] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.221549] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 1039.221561] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 1039.221566] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 1039.221569] pcieport :00:1c.0:[ 0] Receiver Error (First)
  [ 1039.239086] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready

  The device at pcieport :00:1c.0 seems to be the Intel 7265 wireless:
  $ lspci -tv
  -[:00]-+-00.0  Intel Corporation Device 5904
 +-02.0  Intel Corporation Device 5916
 +-14.0  Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
 +-14.2  Intel Corporation Sunrise Point-LP Thermal subsystem
 +-16.0  Intel Corporation Sunrise Point-LP CSME HECI #1
 +-17.0  Intel Corporation Sunrise Point-LP SATA Controller [AHCI 
mode]
 +-1c.0-[01]00.0  Intel Corporation Wireless 7265
 +-1d.0-[02]00.0  Samsung Electronics Co Ltd NVMe SSD Controller
 +-1f.0  Intel Corporation Device 9d58
 +-1f.2  Intel Corporation Sunrise Point-LP PMC
 +-1f.3  Intel Corporation Device 9d71
 \-1f.4  Intel Corporation Sunrise Point-LP SMBus

  To allow the device to connect again I use the following:
  $ sudo systemctl restart network-manager.service

  That said, the pcieport :00:1c.0 dmesg outputs sometimes appears
  without affecting the wifi connection...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ inxi -Abd
  System:Host: 710s Kernel: 4.4.0-62-generic x86_64 (64 bit) Desktop: Unity 
7.4.0  Distro: Ubuntu 16.04 xenial
  Machine:   System: LENOVO (portable) product: 80VQ v: Lenovo ideapad 
710S-13IKB
 Mobo: LENOVO model: Lenovo ideapad 710S-13IKB v: SDK0J40709 WIN
 Bios: LENOVO v: 3HCN12S2 date: 10/07/2016
  CPU:   Dual core Intel Core i7-7500U (-HT-MCP-) speed/max: 600/2701 MHz
  Graphics:  Card: Intel Device 5916
 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1920x1080@60.02hz
 GLX Renderer: Mesa DRI Intel Kabylake GT2 GLX Version: 3.0 Mesa 
11.2.0
  Audio: Card Intel Device 9d71 driver: snd_hda_intel Sound: ALSA v: 
k4.4.0-62-generic
  Network:   Card: Intel Wireless 7265 driver: iwlwifi
  Drives:HDD Total Size: NA (-) ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
 Optical: No optical drives detected.
  Info:  Processes: 244 Uptime: 34 min Memory: 2000.8/7876.3MB Client: 
Shell (bash) inxi: 2.2.35

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1663050/+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 1663050] Re: Intel 7265 wireless device disconnect: link is not ready

[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/1663050

Title:
  Intel 7265 wireless device disconnect: link is not ready

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed

Bug description:
  The wifi device disconnect sometime randomly or sometime when switching 
hotspot with the following dmesg output:
  [ 1039.212949] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.213503] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.221549] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 1039.221561] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 1039.221566] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 1039.221569] pcieport :00:1c.0:[ 0] Receiver Error (First)
  [ 1039.239086] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready

  The device at pcieport :00:1c.0 seems to be the Intel 7265 wireless:
  $ lspci -tv
  -[:00]-+-00.0  Intel Corporation Device 5904
 +-02.0  Intel Corporation Device 5916
 +-14.0  Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
 +-14.2  Intel Corporation Sunrise Point-LP Thermal subsystem
 +-16.0  Intel Corporation Sunrise Point-LP CSME HECI #1
 +-17.0  Intel Corporation Sunrise Point-LP SATA Controller [AHCI 
mode]
 +-1c.0-[01]00.0  Intel Corporation Wireless 7265
 +-1d.0-[02]00.0  Samsung Electronics Co Ltd NVMe SSD Controller
 +-1f.0  Intel Corporation Device 9d58
 +-1f.2  Intel Corporation Sunrise Point-LP PMC
 +-1f.3  Intel Corporation Device 9d71
 \-1f.4  Intel Corporation Sunrise Point-LP SMBus

  To allow the device to connect again I use the following:
  $ sudo systemctl restart network-manager.service

  That said, the pcieport :00:1c.0 dmesg outputs sometimes appears
  without affecting the wifi connection...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ inxi -Abd
  System:Host: 710s Kernel: 4.4.0-62-generic x86_64 (64 bit) Desktop: Unity 
7.4.0  Distro: Ubuntu 16.04 xenial
  Machine:   System: LENOVO (portable) product: 80VQ v: Lenovo ideapad 
710S-13IKB
 Mobo: LENOVO model: Lenovo ideapad 710S-13IKB v: SDK0J40709 WIN
 Bios: LENOVO v: 3HCN12S2 date: 10/07/2016
  CPU:   Dual core Intel Core i7-7500U (-HT-MCP-) speed/max: 600/2701 MHz
  Graphics:  Card: Intel Device 5916
 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1920x1080@60.02hz
 GLX Renderer: Mesa DRI Intel Kabylake GT2 GLX Version: 3.0 Mesa 
11.2.0
  Audio: Card Intel Device 9d71 driver: snd_hda_intel Sound: ALSA v: 
k4.4.0-62-generic
  Network:   Card: Intel Wireless 7265 driver: iwlwifi
  Drives:HDD Total Size: NA (-) ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
 Optical: No optical drives detected.
  Info:  Processes: 244 Uptime: 34 min Memory: 2000.8/7876.3MB Client: 
Shell (bash) inxi: 2.2.35

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1663050/+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 1663050] Re: Intel 7265 wireless device disconnect: link is not ready

[Alex Shtof]

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

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

Title:
  Intel 7265 wireless device disconnect: link is not ready

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed

Bug description:
  The wifi device disconnect sometime randomly or sometime when switching 
hotspot with the following dmesg output:
  [ 1039.212949] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.213503] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.221549] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 1039.221561] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 1039.221566] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 1039.221569] pcieport :00:1c.0:[ 0] Receiver Error (First)
  [ 1039.239086] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready

  The device at pcieport :00:1c.0 seems to be the Intel 7265 wireless:
  $ lspci -tv
  -[:00]-+-00.0  Intel Corporation Device 5904
 +-02.0  Intel Corporation Device 5916
 +-14.0  Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
 +-14.2  Intel Corporation Sunrise Point-LP Thermal subsystem
 +-16.0  Intel Corporation Sunrise Point-LP CSME HECI #1
 +-17.0  Intel Corporation Sunrise Point-LP SATA Controller [AHCI 
mode]
 +-1c.0-[01]00.0  Intel Corporation Wireless 7265
 +-1d.0-[02]00.0  Samsung Electronics Co Ltd NVMe SSD Controller
 +-1f.0  Intel Corporation Device 9d58
 +-1f.2  Intel Corporation Sunrise Point-LP PMC
 +-1f.3  Intel Corporation Device 9d71
 \-1f.4  Intel Corporation Sunrise Point-LP SMBus

  To allow the device to connect again I use the following:
  $ sudo systemctl restart network-manager.service

  That said, the pcieport :00:1c.0 dmesg outputs sometimes appears
  without affecting the wifi connection...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ inxi -Abd
  System:Host: 710s Kernel: 4.4.0-62-generic x86_64 (64 bit) Desktop: Unity 
7.4.0  Distro: Ubuntu 16.04 xenial
  Machine:   System: LENOVO (portable) product: 80VQ v: Lenovo ideapad 
710S-13IKB
 Mobo: LENOVO model: Lenovo ideapad 710S-13IKB v: SDK0J40709 WIN
 Bios: LENOVO v: 3HCN12S2 date: 10/07/2016
  CPU:   Dual core Intel Core i7-7500U (-HT-MCP-) speed/max: 600/2701 MHz
  Graphics:  Card: Intel Device 5916
 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1920x1080@60.02hz
 GLX Renderer: Mesa DRI Intel Kabylake GT2 GLX Version: 3.0 Mesa 
11.2.0
  Audio: Card Intel Device 9d71 driver: snd_hda_intel Sound: ALSA v: 
k4.4.0-62-generic
  Network:   Card: Intel Wireless 7265 driver: iwlwifi
  Drives:HDD Total Size: NA (-) ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
 Optical: No optical drives detected.
  Info:  Processes: 244 Uptime: 34 min Memory: 2000.8/7876.3MB Client: 
Shell (bash) inxi: 2.2.35

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1663050/+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 1696900] [NEW] error brokecount>0 mean installed package have unmet dependencies

[Ruben Montoya]

Public bug reported:

mean installed package have unmet dependencies
error brokecount>0
ubuntu 16.04 lts

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jun  8 20:57:07 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:17df]
InstallationDate: Installed on 2017-05-28 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Hewlett-Packard HP EliteBook 2570p
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=d1d64119-317e-4385-a581-c35f967a59d7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ISB Ver. F.31
dmi.board.name: 17DF
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 61.20
dmi.chassis.asset.tag: CNU246B69H
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ISBVer.F.31:bd10/01/2012:svnHewlett-Packard:pnHPEliteBook2570p:pvrA1029D1102:rvnHewlett-Packard:rn17DF:rvrKBCVersion61.20:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 2570p
dmi.product.version: A1029D1102
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jun  8 19:56:54 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  error brokecount>0 mean installed package have unmet dependencies

Status in xorg package in Ubuntu:
  New

Bug description:
  mean installed package have unmet dependencies
  error brokecount>0
  ubuntu 16.04 lts

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jun  8 20:57:07 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:17df]
  InstallationDate: Installed on 2017-05-28 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard HP EliteBook 2570p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=d1d64119-317e-4385-a581-c35f967a59d7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ISB Ver. F.31
  dmi.board.name: 17DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 61.20
  dmi.chassis.asset.tag: CNU246B69H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1696797] Re: [regression] Mir EGL clients all crash with SIGSEGV in XGetXCBConnection()

[Daniel van Vugt]

Yep. A problem we've hit a few times before...

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

Title:
  [regression] Mir EGL clients all crash with SIGSEGV in
  XGetXCBConnection()

Status in Mir:
  New
Status in mesa package in Ubuntu:
  New
Status in miral package in Ubuntu:
  Invalid

Bug description:
  Running today's daily ISO, enabled universe and installed:

  $ sudo apt install miral-examples mir-graphics-drivers-desktop
  qterminal qtubuntu-desktop

  Then,

  $ miral-app -launcher qterminal

  works.

  But after doing,

  $ sudo apt upgrade -y

  It crashes as seen here.

  Probably related:

  $ sudo apt install mir-demos
  $ mir_demo_server --test-client mir_demo_client_eglplasma

  also crashes.

  Avoiding EGL use by:

  $ miral-app -kiosk

  Works until an EGL app is started

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: miral-examples 1.3.2+17.04.20170330.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Thu Jun  8 16:15:14 2017
  ExecutablePath: /usr/bin/miral-shell
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  ProcCmdline: /usr/bin/miral-shell --file /run/user/999/miral_socket 
--desktop_file_hint=miral-shell.desktop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: miral
  StacktraceTop:
   XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: miral-shell crashed with SIGSEGV in XGetXCBConnection()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1696797/+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 1696797] Re: [regression] Mir EGL clients all crash with SIGSEGV in XGetXCBConnection()

[Chris Halse Rogers]

So, the problem here is going to be the EGL platform detection - it's
failing to detect Mir, and is instead trying (and failing) to connect to
an X server.

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

Title:
  [regression] Mir EGL clients all crash with SIGSEGV in
  XGetXCBConnection()

Status in Mir:
  New
Status in mesa package in Ubuntu:
  New
Status in miral package in Ubuntu:
  Invalid

Bug description:
  Running today's daily ISO, enabled universe and installed:

  $ sudo apt install miral-examples mir-graphics-drivers-desktop
  qterminal qtubuntu-desktop

  Then,

  $ miral-app -launcher qterminal

  works.

  But after doing,

  $ sudo apt upgrade -y

  It crashes as seen here.

  Probably related:

  $ sudo apt install mir-demos
  $ mir_demo_server --test-client mir_demo_client_eglplasma

  also crashes.

  Avoiding EGL use by:

  $ miral-app -kiosk

  Works until an EGL app is started

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: miral-examples 1.3.2+17.04.20170330.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Thu Jun  8 16:15:14 2017
  ExecutablePath: /usr/bin/miral-shell
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  ProcCmdline: /usr/bin/miral-shell --file /run/user/999/miral_socket 
--desktop_file_hint=miral-shell.desktop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: miral
  StacktraceTop:
   XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: miral-shell crashed with SIGSEGV in XGetXCBConnection()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1696797/+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 1696797] Re: [regression] Mir EGL clients all crash with SIGSEGV in XGetXCBConnection()

[Daniel van Vugt]

On the other hand, this appears to be the same as bug 1526658, which was
fixed in Mir itself...

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

** Changed in: mir
   Status: Invalid => New

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

Title:
  [regression] Mir EGL clients all crash with SIGSEGV in
  XGetXCBConnection()

Status in Mir:
  New
Status in mesa package in Ubuntu:
  New
Status in miral package in Ubuntu:
  Invalid

Bug description:
  Running today's daily ISO, enabled universe and installed:

  $ sudo apt install miral-examples mir-graphics-drivers-desktop
  qterminal qtubuntu-desktop

  Then,

  $ miral-app -launcher qterminal

  works.

  But after doing,

  $ sudo apt upgrade -y

  It crashes as seen here.

  Probably related:

  $ sudo apt install mir-demos
  $ mir_demo_server --test-client mir_demo_client_eglplasma

  also crashes.

  Avoiding EGL use by:

  $ miral-app -kiosk

  Works until an EGL app is started

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: miral-examples 1.3.2+17.04.20170330.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Thu Jun  8 16:15:14 2017
  ExecutablePath: /usr/bin/miral-shell
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  ProcCmdline: /usr/bin/miral-shell --file /run/user/999/miral_socket 
--desktop_file_hint=miral-shell.desktop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: miral
  StacktraceTop:
   XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: miral-shell crashed with SIGSEGV in XGetXCBConnection()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1696797/+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 1696797] Re: [regression] Mir EGL clients all crash with SIGSEGV in XGetXCBConnection()

[Daniel van Vugt]

Yep. The crash happens in all Mir GL clients. Other Mir demo servers
start up OK, but miral-shell crashes because it has an internal client
(SpinnerSplash).

** Summary changed:

- miral-shell crashed with SIGSEGV in XGetXCBConnection()
+ [regression] Mir EGL clients all crash with SIGSEGV in XGetXCBConnection()

** Tags added: regression-release

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

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

** Changed in: mir
   Status: New => Invalid

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

Title:
  [regression] Mir EGL clients all crash with SIGSEGV in
  XGetXCBConnection()

Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in miral package in Ubuntu:
  Invalid

Bug description:
  Running today's daily ISO, enabled universe and installed:

  $ sudo apt install miral-examples mir-graphics-drivers-desktop
  qterminal qtubuntu-desktop

  Then,

  $ miral-app -launcher qterminal

  works.

  But after doing,

  $ sudo apt upgrade -y

  It crashes as seen here.

  Probably related:

  $ sudo apt install mir-demos
  $ mir_demo_server --test-client mir_demo_client_eglplasma

  also crashes.

  Avoiding EGL use by:

  $ miral-app -kiosk

  Works until an EGL app is started

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: miral-examples 1.3.2+17.04.20170330.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Thu Jun  8 16:15:14 2017
  ExecutablePath: /usr/bin/miral-shell
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  ProcCmdline: /usr/bin/miral-shell --file /run/user/999/miral_socket 
--desktop_file_hint=miral-shell.desktop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: miral
  StacktraceTop:
   XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: miral-shell crashed with SIGSEGV in XGetXCBConnection()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1696797/+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 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager

[Launchpad Bug Tracker]

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

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

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

Title:
  Failed to use bus name org.freedesktop.DisplayManager

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I have implemented the command lightdm --test-mode --debug and I happened 
here such error:
  ==
  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Using Xephyr for X servers
  [+0.01s] DEBUG: Registered seat module xlocal
  [+0.01s] DEBUG: Registered seat module xremote
  [+0.01s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Registered seat module surfaceflinger
  [+1.13s] DEBUG: Adding default seat
  [+1.13s] DEBUG: Seat: Starting
  [+1.13s] DEBUG: Seat: Creating greeter session
  [+1.17s] DEBUG: Seat: Creating display server of type x
  [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+1.20s] DEBUG: Using VT 7
  [+1.20s] DEBUG: Seat: Starting local X display on VT 7
  [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+1.36s] DEBUG: DisplayServer x-1: Launching X Server
  [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+1.36s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  Failed to use bus name org.freedesktop.DisplayManager, do you have 
appropriate permissions?
  =
  On the Internet I have the exact solution to this problem is not found. The 
computer I have is only one graphics card and built-in The controller is not 
present. Somebody help than you can!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648319/+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 1696797] Re: miral-shell crashed with SIGSEGV in XGetXCBConnection()

[Daniel van Vugt]

This looks like a typical Mesa regression. And Mesa got updated 13 hours
ago (4 hours prior to this bug report). That's probably no coincidence
:)

https://launchpad.net/ubuntu/+source/mesa

** Information type changed from Private to Public

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

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

Title:
  miral-shell crashed with SIGSEGV in XGetXCBConnection()

Status in Mir:
  New
Status in mesa package in Ubuntu:
  New
Status in miral package in Ubuntu:
  New

Bug description:
  Running today's daily ISO, enabled universe and installed:

  $ sudo apt install miral-examples mir-graphics-drivers-desktop
  qterminal qtubuntu-desktop

  Then,

  $ miral-app -launcher qterminal

  works.

  But after doing,

  $ sudo apt upgrade -y

  It crashes as seen here.

  Probably related:

  $ sudo apt install mir-demos
  $ mir_demo_server --test-client mir_demo_client_eglplasma

  also crashes.

  Avoiding EGL use by:

  $ miral-app -kiosk

  Works until an EGL app is started

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: miral-examples 1.3.2+17.04.20170330.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Thu Jun  8 16:15:14 2017
  ExecutablePath: /usr/bin/miral-shell
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  ProcCmdline: /usr/bin/miral-shell --file /run/user/999/miral_socket 
--desktop_file_hint=miral-shell.desktop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: miral
  StacktraceTop:
   XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
  Title: miral-shell crashed with SIGSEGV in XGetXCBConnection()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1696797/+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 1696880] Re: Numbers overlap in the 'Dash to Dock' extension gui.

[Daniel van Vugt]

** Package changed: ubuntu-themes (Ubuntu) => gnome-shell-extension-
dashtodock (Ubuntu)

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

Title:
  Numbers overlap in the 'Dash to Dock' extension gui.

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  New

Bug description:
  There is some number overlap in the 'Dash to Dock' gui. In the 'Icon
  size limit' section.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun  8 18:38:13 2017
  InstallationDate: Installed on 2017-06-08 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1696880/+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 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

[Launchpad Bug Tracker]

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

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

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

Title:
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic:
  No such file or directory

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Please affect that report to the real package; i've chosen apt by
  default as i've no idea about the faulty one.

  Doing some daily upgrades as usual, and have seen that curious error
  while setting 'initramfs':

  Setting up linux-firmware (1.164) ...
  update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
  update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
  WARNING: missing /lib/modules/4.8.0-25-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
  WARNING: missing /lib/modules/4.8.0-0-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

  That ZZ installation indeed only has 4.10 kernels installed, and is
  often checked for cleaning (autoremove/bleachbit). Packages are always
  purged when removed.

  So i wonder why and which process/script has left a crappy /boot/ list
  of initrd.img-4.8* to produce the errors above.

  oem@u64:~$ ls -la /boot/
  total 142448
  drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
  drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
  -rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
  -rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
  -rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
  -rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
  drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
  drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
  -rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
  -rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
  -rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
  -rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
  -rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
  -rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
  -rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
  -rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
  -rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
  -rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
  -rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 21 06:28:04 2017
  Dependencies:

  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1674568/+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 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

[Jarod]

same error.

$ ls /boot/
abi-4.10.0-22-generic initrd.img-4.10.0-22-generic  
initrd.img-4.4.0-14-generic  initrd.img-4.4.0-8-generic  
memtest86+_multiboot.bin
config-4.10.0-22-generic  initrd.img-4.4.0-10-generic   
initrd.img-4.4.0-15-generic  initrd.img-4.4.0-9-generic  
System.map-4.10.0-22-generic
efi   initrd.img-4.4.0-12-generic   
initrd.img-4.4.0-2-generic   memtest86+.bin  
vmlinuz-4.10.0-22-generic
grub  initrd.img-4.4.0-13-generic   
initrd.img-4.4.0-7-generic   memtest86+.elf


$ ls /var/lib/initramfs-tools/
4.10.0-22-generic  4.4.0-12-generic  4.4.0-14-generic  4.4.0-2-generic  
4.4.0-7-generic  4.4.0-9-generic
4.4.0-10-generic   4.4.0-13-generic  4.4.0-15-generic  4.4.0-4-generic  
4.4.0-8-generic

all kernel version except 4.10.0-22-generic already deleted

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

Title:
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic:
  No such file or directory

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Please affect that report to the real package; i've chosen apt by
  default as i've no idea about the faulty one.

  Doing some daily upgrades as usual, and have seen that curious error
  while setting 'initramfs':

  Setting up linux-firmware (1.164) ...
  update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
  update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
  WARNING: missing /lib/modules/4.8.0-25-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
  WARNING: missing /lib/modules/4.8.0-0-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

  That ZZ installation indeed only has 4.10 kernels installed, and is
  often checked for cleaning (autoremove/bleachbit). Packages are always
  purged when removed.

  So i wonder why and which process/script has left a crappy /boot/ list
  of initrd.img-4.8* to produce the errors above.

  oem@u64:~$ ls -la /boot/
  total 142448
  drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
  drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
  -rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
  -rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
  -rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
  -rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
  drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
  drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
  -rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
  -rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
  -rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
  -rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
  -rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
  -rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
  -rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
  -rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
  -rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
  -rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
  -rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 21 06:28:04 2017
  Dependencies:

  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1657243] Re: package openssl 1.0.2g-1ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package openssl 1.0.2g-1ubuntu4 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I have recently installed ubuntu on my computer. I wanted to install 2
  upgrades and it crashed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Jan 17 21:10:53 2017
  DuplicateSignature:
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package openssl (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-12-05 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1657243/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie

[Launchpad Bug Tracker]

This bug was fixed in the package whoopsie - 0.2.56

---
whoopsie (0.2.56) artful; urgency=medium

  * src/whoopsie.c: Add HotspotError from the openjdk-8 package hook which can
be larger than 1KB to the list of accepted fields. (LP: #1696814)

 -- Brian Murray   Thu, 08 Jun 2017 15:44:53 -0700

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

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

Title:
  add openjdk hs log to list of acceptable_fields in whoopsie

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists)
  to a Crash report under the HotspotError key. The hook is currently
  limited to attaching files under 100 KB.

  Please add HotspotError key to the whitelist in order for it to be
  available in error tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Kai Holthaus]

@nacc: Add-on: On my Debian systems (Debian jessie and stretch) that
also experience this issue, however, the lines do look like what you
described - and still the system hangs at reboot / shutdown.

In a previous message it sounded like you had identified an issue and a
fix - did I misinterpret your response? If so, was it a fix I can apply
to my xenial system and test?

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Kai Holthaus]

@nacc: No, my lines do not like that. On my xenial system, I have:

Wants=network-online.target remote-fs-pre.target
After=network-online.target

Which is probably why on my system the iscsid daemon shuts down before
the logout.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1696876] Re: Epson Stylus Photo 1390 driver missing in CUPS

[William Grant]

** No longer affects: launchpad

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

Title:
  Epson Stylus Photo 1390 driver missing in CUPS

Status in CUPS:
  New
Status in Gutenprint:
  New
Status in cups package in Ubuntu:
  Incomplete
Status in gutenprint package in Ubuntu:
  Incomplete

Bug description:
  I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
   still no PPD for this printer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1696876/+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 1696881] Re: package python3-software-properties 0.96.20.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

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

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

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

Title:
  package python3-software-properties 0.96.20.7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  was installing updates and got this error.
  Release 16.04
  unable to locate package pkgname.
  I expected updates to install, not all did.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-software-properties 0.96.20.7
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 18:48:24 2017
  DuplicateSignature:
   package:python3-software-properties:0.96.20.7
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package python3-software-properties (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-04-12 (788 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.20.7 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-09-13 (268 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1696881/+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 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

[ChristianEhrhardt]

Thanks Tore for checking so much Details and all the relations to 
NetworkManager it might have on a Desktop.
On a server (no NM) I'd think it is always enabled i'd think.

But if that is a bug or not is a"discussion".
Just as much as users want it off (here) others want it on - see bug 176125 and 
bug 841353.
I think it is about the best default and control.
Reading through these bugs IMHO I see stronger arguments to keep it enabled for 
now - and since /etc/sysctl.d/10-ipv6-privacy.conf is a conffile it can be 
adapted if needed.

I'd currently be more concerned if disabling in
/etc/sysctl.d/10-ipv6-privacy.conf would not switch them off in all of
them, but had no time to check.

I'll also subscribe cyphermox who worked on enabling that if this
becomes more of a discussion.

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

Title:
  IPv6 Privacy Extensions enabled on Ubuntu Server by default

Status in cloud-init package in Ubuntu:
  Triaged
Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.04 LTS and Ubuntu 12.10 server images both ship with the
  IPv6 Privacy Extensions enabled (as defined in RFC 4941[0]). Not only
  are they enabled, but these addresses are preferred over addresses
  obtained using SLAAC. While is may be considered a reasonable default
  on an image being used on a personal computer, it's not something that
  is sane to have enabled by default in a server environment. Having
  this extension enabled can wreak havoc if you are expecting a specific
  IPv6 address when you know the MAC addresses of your systems
  beforehand.

  The file that is responsible for causing this to be defaulted to
  enabled is: "/etc/sysctl.d/10-ipv6-privacy.conf". This file appears to
  be part of the procps package (as per the output of 'dpkg -S') and
  contains the following:

  # IPv6 Privacy Extensions (RFC 4941)
  # ---
  # IPv6 typically uses a device's MAC address when choosing an IPv6 address
  # to use in autoconfiguration. Privacy extensions allow using a randomly
  # generated IPv6 address, which increases privacy.
  #
  # Acceptable values:
  #0 - don’t use privacy extensions.
  #1 - generate privacy addresses
  #2 - prefer privacy addresses and use them over the normal addresses.
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2

  In short, IPv6 privacy extensions should not be enabled by default
  when deploying an Ubuntu server image. In a server environment you
  should be able to reliably determine your IPv6 address based on the
  MAC address of the system.

  Thank you for taking the time to look in to this as well as consider
  changing the default behavior of Ubuntu server.

  -Tim Heckman

  [0] http://tools.ietf.org/html/rfc4941

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+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 1696881] Re: package python3-software-properties 0.96.20.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1696881

Title:
  package python3-software-properties 0.96.20.7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in software-properties package in Ubuntu:
  New

Bug description:
  was installing updates and got this error.
  Release 16.04
  unable to locate package pkgname.
  I expected updates to install, not all did.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-software-properties 0.96.20.7
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 18:48:24 2017
  DuplicateSignature:
   package:python3-software-properties:0.96.20.7
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package python3-software-properties (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-04-12 (788 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.20.7 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-09-13 (268 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1696881/+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 1696881] [NEW] package python3-software-properties 0.96.20.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

[Alexander Fordyce]

Public bug reported:

was installing updates and got this error.
Release 16.04
unable to locate package pkgname.
I expected updates to install, not all did.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-software-properties 0.96.20.7
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun  8 18:48:24 2017
DuplicateSignature:
 package:python3-software-properties:0.96.20.7
 Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
 dpkg: error processing package python3-software-properties (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2015-04-12 (788 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: software-properties
Title: package python3-software-properties 0.96.20.7 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-09-13 (268 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package python3-software-properties 0.96.20.7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in software-properties package in Ubuntu:
  New

Bug description:
  was installing updates and got this error.
  Release 16.04
  unable to locate package pkgname.
  I expected updates to install, not all did.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-software-properties 0.96.20.7
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 18:48:24 2017
  DuplicateSignature:
   package:python3-software-properties:0.96.20.7
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package python3-software-properties (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-04-12 (788 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.20.7 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-09-13 (268 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1696881/+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 1696876] Re: Epson Stylus Photo 1390 driver missing in CUPS

[Till Kamppeter]

Is anywhere promised that there is a Linux driver/free software driver
for this printer? If yes, where?


** Changed in: launchpad
   Status: New => Invalid

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

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

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

Title:
  Epson Stylus Photo 1390 driver missing in CUPS

Status in CUPS:
  New
Status in Gutenprint:
  New
Status in Launchpad itself:
  Invalid
Status in cups package in Ubuntu:
  Incomplete
Status in gutenprint package in Ubuntu:
  Incomplete

Bug description:
  I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
   still no PPD for this printer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1696876/+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 1696880] [NEW] Numbers overlap in the 'Dash to Dock' extension gui.

[Robin Hicks]

Public bug reported:

There is some number overlap in the 'Dash to Dock' gui. In the 'Icon
size limit' section.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20170518-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jun  8 18:38:13 2017
InstallationDate: Installed on 2017-06-08 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Numbers overlap in the 'Dash to Dock' extension gui.

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  There is some number overlap in the 'Dash to Dock' gui. In the 'Icon
  size limit' section.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun  8 18:38:13 2017
  InstallationDate: Installed on 2017-06-08 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1696880/+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 1577596] Re: ntpd not started when using ntpdate

[ChristianEhrhardt]

Hi Heinrich,
thank you for picking up working on this.
I must beg your pardon as I come by this so late (as I'm currently cleaning 
bugs too long dormant).

I like the suggestion of a fix by adapting the scripts, but following comments 
#22 and #23 that would have to be accepted in Debian instead. If you wouldn't 
mind could you file a bug there and link it here?
Although the reason why we are somewhat reluctant to take the changes (details 
in the comments that I mentioned) also implies that the chance this is accepted 
is rather low.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1472639] Re: apparmor profile denied for kerberos: /run/.heim_org.h5l.kcm-socket

[Kartik Subbarao]

No worries Christian. As far as issues caused by unpredictable complex
interactions go, this one is fairly benign :-) I'm fine with the
workaround -- it's just one more line that gets programmatically added
to a config file that has to be customized anyway. And who knows, it may
well have been resolved by now in newer versions of openldap and
kerberos.

In any case, I appreciate your empathy -- if only I could channel it to
the maintainers of other software where I've reported bugs that are far
more painful to deal with :-)

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

Title:
  apparmor profile denied for kerberos:  /run/.heim_org.h5l.kcm-socket

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  The slapd apparmor profile doesn't allow access to /run/.heim_org.h5l
  .kcm-socket which is used by kerberos:

  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
  name="/run/.heim_org.h5l.kcm-socket" pid=61289 comm="slapd"
  requested_mask="wr" denied_mask="wr" fsuid=389 ouid=0

  This is as of 2.4.40+dfsg-1ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1472639/+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 1696876] [NEW] Epson Stylus Photo 1390 driver missing in CUPS

[Yoshiba]

Public bug reported:

I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
 still no PPD for this printer.

** Affects: cups
 Importance: Undecided
 Status: New

** Affects: gutenprint
 Importance: Undecided
 Status: New

** Affects: launchpad
 Importance: Undecided
 Status: New

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

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


** Tags: cups cups-driver-gutenprint

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

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

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

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

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

Title:
  Epson Stylus Photo 1390 driver missing in CUPS

Status in CUPS:
  New
Status in Gutenprint:
  New
Status in Launchpad itself:
  New
Status in cups package in Ubuntu:
  New
Status in gutenprint package in Ubuntu:
  New

Bug description:
  I have a Epson Stylus Photo 1390 printer and I installed Ubuntu, CUPS, 
cups-driver-gutenprint, but 
   still no PPD for this printer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1696876/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie

[Brian Murray]

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

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

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

Title:
  add openjdk hs log to list of acceptable_fields in whoopsie

Status in whoopsie package in Ubuntu:
  In Progress

Bug description:
  OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists)
  to a Crash report under the HotspotError key. The hook is currently
  limited to attaching files under 100 KB.

  Please add HotspotError key to the whitelist in order for it to be
  available in error tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1564451] Re: User processes are counted towards systemd limit for sshd processes (add libpam-systemd to openssh-server)

[ChristianEhrhardt]

** Summary changed:

- User processes are counted towards systemd limit for sshd processes
+ User processes are counted towards systemd limit for sshd processes (add 
libpam-systemd to openssh-server)

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

Title:
  User processes are counted towards systemd limit for sshd processes
  (add libpam-systemd to openssh-server)

Status in systemd:
  New
Status in openssh package in Ubuntu:
  New

Bug description:
  When running Xenial, user processes are counted towards the limit for
  the ssh.service, with a limit of 512. So if I login as a normal user
  via ssh and start 512 processes, nobody will be able to login any more
  and even all other users currently logged in will not be able to start
  any new tasks. I'm not certain whether this behaviour is by design,
  but to me it looks like a critical DOS possibility, so tagging as
  security bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1564451/+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 270512] Re: openssh-client could suggest xauth rather than recommend it

[ChristianEhrhardt]

Wow this is an old issue (and still true as of artful) :-/
Maybe that really would be better off as a suggests.
In a graphical environment as suggested before it is around via the dep from 
xorg and others.

But other than feeling embarrased that this is around for so long I
think this is nothing that should be changed in Ubuntu individually.
That we should do in sync with Debian.

Therefore if anybody still (or newly re-en-kindled) cares it would be
great to file that with Debian and we pick it up from there. Also IIRC
cjwatson takes care of it in Ubuntu AND Debian so he certainly has more
experience to decide on this.

** Tags added: needs-upstream-report

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

Title:
  openssh-client could suggest xauth rather than recommend it

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  openssh-client is in the standard seed. It recommends xauth, which as
  of intrepid pulls the following packages in a basic server install :

  xauth
  |- libxext6
  |- libxmuu1
  |- x11-common

  It would pull even more if there wasn't already another Recommend bug
  in the minimal seed that pulled other X libraries (see bug 270500).

  Server systems do pretty well without those packages installed by
  default.

  Solution: drop the xauth "Recommends" and make it a "Suggests"
  instead.  Note that xauth gets pulled in in desktop installs through a
  xorg Depends, and that in Hardy xauth wasn't in the standard seed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/270512/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@Kai: In xenial, open-iscsi.service should have the following lines
alreadY

Wants=network-online.target remote-fs-pre.target iscsid.service
After=network-online.target iscsid.service

Can you confirm that is the case on your system?

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1696870] Re: on Lubuntu 17 (french version) System Tools / Software: progression bar stopped at 76% on installing Chromium, but i tried Chromium anyway and ended up here...

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1688721, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  on Lubuntu 17 (french version) System Tools / Software: progression
  bar stopped at 76% on installing Chromium, but i tried Chromium anyway
  and ended up here...

Status in gconf package in Ubuntu:
  New

Bug description:
  I will just try again and see if it works for this Chromium download
  and install!

  Oh, i have to say that «Logiciels» (System Tools / Software Installer)
  was empty at first, but i changed the server address in the
  Preferences and then i waited 1 or 2 minutes and then everything
  looked OK. I successfully downloaded and tested another software:
  GIMP.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Thu Jun  8 17:34:38 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-05 (3 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1696870/+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 1696870] [NEW] on Lubuntu 17 (french version) System Tools / Software: progression bar stopped at 76% on installing Chromium, but i tried Chromium anyway and ended up here...

[Sébastien Bouchard]

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

Public bug reported:

I will just try again and see if it works for this Chromium download and
install!

Oh, i have to say that «Logiciels» (System Tools / Software Installer)
was empty at first, but i changed the server address in the Preferences
and then i waited 1 or 2 minutes and then everything looked OK. I
successfully downloaded and tested another software: GIMP.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic i686
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Thu Jun  8 17:34:38 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-05 (3 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 zesty

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

Title:
  on Lubuntu 17 (french version) System Tools / Software: progression
  bar stopped at 76% on installing Chromium, but i tried Chromium anyway
  and ended up here...

Status in gconf package in Ubuntu:
  New

Bug description:
  I will just try again and see if it works for this Chromium download
  and install!

  Oh, i have to say that «Logiciels» (System Tools / Software Installer)
  was empty at first, but i changed the server address in the
  Preferences and then i waited 1 or 2 minutes and then everything
  looked OK. I successfully downloaded and tested another software:
  GIMP.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Thu Jun  8 17:34:38 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-05 (3 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1696870/+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 1472639] Re: apparmor profile denied for kerberos: /run/.heim_org.h5l.kcm-socket

[ChristianEhrhardt]

Hi,
this bug was dormant for a long time.
We have to face it that due to the complexity, the lack of an (easy) recreation 
and the fact that there is a workaround via modifying the apparmor profiles 
likely nothing gets changed - unless somebody in the community steps up and 
does so.

Yet as I read from Kartik, that is somewhat ok for now.

I bed your pardon, sometimes not being able to fix all bugs is a hard truth 
that makes me sad :-/
I'm happy that you are kind of ok with it in this case.

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

Title:
  apparmor profile denied for kerberos:  /run/.heim_org.h5l.kcm-socket

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  The slapd apparmor profile doesn't allow access to /run/.heim_org.h5l
  .kcm-socket which is used by kerberos:

  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
  name="/run/.heim_org.h5l.kcm-socket" pid=61289 comm="slapd"
  requested_mask="wr" denied_mask="wr" fsuid=389 ouid=0

  This is as of 2.4.40+dfsg-1ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1472639/+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 1617341] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ChristianEhrhardt]

** Tags added: need-upstream-report

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  Triaged

Bug description:
  The update did not install. Maybe because the net got disconnected in
  between ???

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   ntp: Install
   ntpdate: Install
   ntp: Configure
   ntpdate: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Aug 26 19:39:18 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-26  19:36:04
   Commandline: aptdaemon role='role-commit-packages' sender=':1.65'
   Upgrade: ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1), 
ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-28 (151 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=790d64f7-9847-4d8c-bbaa-3c87b8aaac16 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1617341/+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 1632575] Re: systemd starts two copies of ntp at boot time

[ChristianEhrhardt]

Yeah this is just using a generated sytsemd unit for the sysv init file.
Never the less I wasn't able to trigger that throughout some ntp upgrades in 
containers.

The bug was already inactive for very long, but I think the reason is
currently that it isn#t really actionable.

@Marius - was that a one time issue or did you get that to be
reproducible and debuggable back then?

** Changed in: ntp (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  systemd starts two copies of ntp at boot time

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  My system monitoring check noticed a stale /var/run/ntpd.pid pidfile
  on a xenial machine that rebooted at 2 AM after unattended upgrades.
  ntpd itself was running, but with a different pid.

  Digging through journalctl I can see

  Oct 12 02:00:11 xenial64 ntp[681]:  * Starting NTP server ntpd
  Oct 12 02:00:11 xenial64 systemd[1]: Started Getty on tty1.
  Oct 12 02:00:11 xenial64 systemd[1]: Reached target Login Prompts.
  Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 run-parts[760]: run-parts: executing 
/etc/redis/redis-server.post-up.d/00_example
  Oct 12 02:00:11 xenial64 systemd[1]: Starting LSB: Start NTP daemon...
  Oct 12 02:00:11 xenial64 ntpd[719]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
  Oct 12 02:00:11 xenial64 ntpd[719]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
  Oct 12 02:00:11 xenial64 ntp[770]:  * Starting NTP server ntpd
  Oct 12 02:00:11 xenial64 ntpd[778]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 
12:34:45 UTC 2016 (1): Starting
  Oct 12 02:00:11 xenial64 ntpd[778]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 109:114
  Oct 12 02:00:11 xenial64 ntp[770]:...done.
  Oct 12 02:00:11 xenial64 systemd[1]: Started LSB: Start NTP daemon.
  Oct 12 02:00:11 xenial64 systemd[1]: Started Advanced key-value store.
  Oct 12 02:00:11 xenial64 ntpd[773]: proto: precision = 0.077 usec (-24)
  Oct 12 02:00:11 xenial64 ntpd[780]: proto: precision = 0.076 usec (-24)
  Oct 12 02:00:11 xenial64 ntpd[780]: unable to bind to wildcard address :: 
- another process may be running - EXITING
  Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 0 v6wildcard 
[::]:123
  Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 1 v4wildcard 
0.0.0.0:123

  As you can see, for some reason systemd starts ntpd twice, so there's
  a race to take over the socket, and a race to take over the pidfile.
  ntpd[773] gets the socket, ntpd[780] gets the pidfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.3
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct 12 06:18:29 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1632575/+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 1696863] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: o pacote libssl1.0.0:i386 não está pronto para configuração não pode configurar (status actu

[teodosio]

Public bug reported:

In the Ubuntu Software App it said there was one update. I asked to
update and it stopped installation in the middle of the process.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libssl1.0.0: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Thu Jun  8 22:32:49 2017
DpkgTerminalLog:
 dpkg: erro ao processar o pacote libssl1.0.0:i386 (--configure):
  o pacote libssl1.0.0:i386 não está pronto para configuração
  não pode configurar (status actual `half-installed')
ErrorMessage: o pacote libssl1.0.0:i386 não está pronto para configuração  não 
pode configurar (status actual `half-installed')
InstallationDate: Installed on 2013-07-28 (1410 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: o 
pacote libssl1.0.0:i386 não está pronto para configuração  não pode configurar 
(status actual `half-installed')
UpgradeStatus: Upgraded to xenial on 2016-08-01 (311 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  o pacote libssl1.0.0:i386 não está pronto para configuração  não pode
  configurar (status actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  In the Ubuntu Software App it said there was one update. I asked to
  update and it stopped installation in the middle of the process.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Jun  8 22:32:49 2017
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote libssl1.0.0:i386 (--configure):
o pacote libssl1.0.0:i386 não está pronto para configuração
não pode configurar (status actual `half-installed')
  ErrorMessage: o pacote libssl1.0.0:i386 não está pronto para configuração  
não pode configurar (status actual `half-installed')
  InstallationDate: Installed on 2013-07-28 (1410 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
o pacote libssl1.0.0:i386 não está pronto para configuração  não pode 
configurar (status actual `half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (311 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696863/+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 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

[ChristianEhrhardt]

Sorry this has been dormant for way too long, but I can still not
reproduce as Serge couldn't back then. To properly reflect that I'm
setting incomplete for now.

You could try to check what /usr/lib/libvirt/virt-aa-helper does with your XML.
Maybe it fails to process it or generates content in your case that libvirt 
won't accept?

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

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

Title:
  virsh save doesn't work for vm with hdd image in non-default location,
  AppArmor-related error

Status in apparmor package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Incomplete

Bug description:
  virsh save does work for vm located in /var/lib/libvirt/images, but doesn't 
work for vm located for example in /mnt/storage/data/limages
  Error message:
  ~$ LANG=C virsh save owncloud /mnt/storage/data/images/owncloud.dump
  error: Failed to save domain owncloud to 
/mnt/storage/data/images/owncloud.dump
  error: внутренняя ошибка: не удалось обновить профиль AppArmor 
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  Translation:
  error: internal error: unable to update AppArmor profile  
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  I tried to dumpxml and then define it again from xml, but that doesn't help.
  Ubuntu Server 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1531703/+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 1569856] Re: wrong status of ntp service

[ChristianEhrhardt]

Maybe on the lsb scope this was already discussed, seems pretty generic
to me.

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

Title:
  wrong status of ntp service

Status in lsb package in Ubuntu:
  Confirmed

Bug description:
  I'am using lxd containers. In the containers installed ntp package.

  Ubuntu 14.04 has old init.d script to manage a service.

  This script using status_of_proc, function from /lib/lsb/init-
  functions which is disregards that system can have ntpd processes
  running in containers. And returns success status, when ntp service is
  not running on host system but it running in container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1569856/+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 1569856] Re: wrong status of ntp service

[ChristianEhrhardt]

I have to beg your pardon that I (and it seems nobody else) found time for 
that. 
Thinking about it again I think this isn't a ntp issue anyway but a generic 
problem for status_of_proc of init-functions.

Marking that to affect lsb-base instead due to that, that even applies
to Xenial as far as I could see so I'm not yet clear if/which releases
to mark.


** Package changed: ntp (Ubuntu) => lsb (Ubuntu)

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

Title:
  wrong status of ntp service

Status in lsb package in Ubuntu:
  Confirmed

Bug description:
  I'am using lxd containers. In the containers installed ntp package.

  Ubuntu 14.04 has old init.d script to manage a service.

  This script using status_of_proc, function from /lib/lsb/init-
  functions which is disregards that system can have ntpd processes
  running in containers. And returns success status, when ntp service is
  not running on host system but it running in container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1569856/+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 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[ChristianEhrhardt]

** Changed in: net-tools (Ubuntu Trusty)
   Status: New => Won't Fix

** Changed in: net-tools (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Fix Released
Status in net-tools source package in Trusty:
  Won't Fix
Status in net-tools source package in Xenial:
  Won't Fix

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/962616/+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 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[Nish Aravamudan]

** Also affects: net-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: net-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Fix Released
Status in net-tools source package in Trusty:
  Won't Fix
Status in net-tools source package in Xenial:
  Won't Fix

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/962616/+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 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[ChristianEhrhardt]

While parsing through older bugs I found that this is fixed since 16.10.
Marking correctly ...

** Changed in: net-tools (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Fix Released
Status in net-tools source package in Trusty:
  Won't Fix
Status in net-tools source package in Xenial:
  Won't Fix

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/962616/+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 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[ChristianEhrhardt]

Given that the impact is "only" a message about not finding any of the
eth? devices but not a breakage for most use cases I don't think it
qualifies for an SRU - also the low activity over time suggests it is
not needed badly due to a hard problem with it.

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Fix Released
Status in net-tools source package in Trusty:
  Won't Fix
Status in net-tools source package in Xenial:
  Won't Fix

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/962616/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

I have upstreamed the patch at 
https://bugzilla.gnome.org/show_bug.cgi?id=783569 !
Hopefully this can be incorporated into future releases of network-manager :)

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

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

[ChristianEhrhardt]

Hi,
I was parsing through issues that had no update for too much time.
I think the issue this gets no further activity is that there is no reproducer 
in a sense of "this is the way to reproduce" - it is confirmed which reflects 
multiple people hitting it and likely to exist which is just right.
But at the current state it is not really actionable for ~ubuntu-server, so for 
now I'm unsubscribing it for now. If there is any new insight it will show up 
on triage of the team anyway.

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

Title:
  rsync hangs on select(5, [], [4], [], {60, 0}

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  In the last few months my home directory backup stopped completing.
  I've been able to reproduce the problem on a single subdirectory
  although I had to add the --debug=all flag to reproduce it on that
  smaller directory.  Specifically, this command never completes:

  rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/

  The html2 directory is a copy of
  gnuradio-3.7.8.1/build/docs/doxygen/html .

  When I strace the command, I see this:
  write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished 
/tmp/html2/atsc__interleaver_8h__incl.md5
  ) = 58
  write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338, 
/tmp/html2/atsc__interleaver_8h__incl.png)
  ) = 59
  open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
  fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
  write(1, "html2/atsc__interleaver_8h__incl"..., 
37html2/atsc__interleaver_8h__incl.png
  ) = 37
  read(3, 
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""..., 
262144) = 262144
  select(6, [5], [4], [5], {60, 0})   = 2 (in [5], out [4], left {59, 
96})
  read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95) 
= 95
  write(4, 
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
 51574) = 51574
  select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
  write(4, 
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
 53259) = 53259
  select(5, [], [4], [], {60, 0}

  The select command times out over and over.  I get the same behavior
  when trying to back up my entire home directory but I don't need the
  --debug=all flag in that case.


  lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  apt-cache policy rsync
  rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsync 3.1.0-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: KDE
  Date: Wed Dec 23 09:44:17 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-09-18 (1922 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  SourcePackage: rsync
  UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie

[Tiago Stürmer Daitx]

** Attachment removed: "source-openjdk-8.py"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892544/+files/source-openjdk-8.py

** Attachment added: "source-openjdk-8.py"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892554/+files/source-openjdk-8.py

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

Title:
  add openjdk hs log to list of acceptable_fields in whoopsie

Status in whoopsie package in Ubuntu:
  New

Bug description:
  OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists)
  to a Crash report under the HotspotError key. The hook is currently
  limited to attaching files under 100 KB.

  Please add HotspotError key to the whitelist in order for it to be
  available in error tracker.

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

Re: [Touch-packages] [Bug 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

[John Johnson]

This is my run:rj@jrj-Aspire-X1700:~$ sudo apt -f install
[sudo] password for jrj:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
   freeglut3 javascript-common libaec0 libarmadillo6 libarpack2
   libavdevice-ffmpeg56 libcoin80v5 libhtsengine1 libmpcdec6 libsuperlu4
   linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic 
linux-headers-4.4.0-67
   linux-headers-4.4.0-67-generic linux-headers-4.4.0-70
   linux-headers-4.4.0-70-generic linux-headers-4.4.0-72
   linux-headers-4.4.0-72-generic linux-headers-4.4.0-75
   linux-headers-4.4.0-75-generic linux-headers-4.4.0-77
   linux-headers-4.4.0-77-generic linux-image-4.4.0-66-generic
   linux-image-4.4.0-67-generic linux-image-4.4.0-70-generic
   linux-image-4.4.0-72-generic linux-image-4.4.0-75-generic
   linux-image-4.4.0-77-generic linux-image-extra-4.4.0-66-generic
   linux-image-extra-4.4.0-67-generic linux-image-extra-4.4.0-70-generic
   linux-image-extra-4.4.0-72-generic linux-image-extra-4.4.0-75-generic
   linux-image-extra-4.4.0-77-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/130 kB of archives.
After this operation, 0 B of additional disk space will be used.
dpkg: error processing package libgssapi-krb5-2:i386 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
Errors were encountered while processing:
  libgssapi-krb5-2:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)
jrj@jrj-Aspire-X1700:~$



On 06/08/2017 01:15 PM, Andreas Hasenack wrote:
> sudo apt -f install

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

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie

[Tiago Stürmer Daitx]

This is the proposed openjdk-8 hook.

** Description changed:

- This is for Tiago's openjdk apport package hook.
+ OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to
+ a Crash report under the HotspotError key. The hook is currently limited
+ to attaching files under 100 KB.
+ 
+ Please add HotspotError key to the whitelist in order for it to be
+ available in error tracker.

** Attachment added: "source-openjdk-8.py"
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+attachment/4892544/+files/source-openjdk-8.py

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

Title:
  add openjdk hs log to list of acceptable_fields in whoopsie

Status in whoopsie package in Ubuntu:
  New

Bug description:
  OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists)
  to a Crash report under the HotspotError key. The hook is currently
  limited to attaching files under 100 KB.

  Please add HotspotError key to the whitelist in order for it to be
  available in error tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696826] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1688721, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  issue

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun  8 18:08:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-05 (3 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1696826/+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 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie

[Brian Murray]

** Changed in: whoopsie (Ubuntu)
 Assignee: Canonical Foundations Team (canonical-foundations) => Brian 
Murray (brian-murray)

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

Title:
  add openjdk hs log to list of acceptable_fields in whoopsie

Status in whoopsie package in Ubuntu:
  New

Bug description:
  OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists)
  to a Crash report under the HotspotError key. The hook is currently
  limited to attaching files under 100 KB.

  Please add HotspotError key to the whitelist in order for it to be
  available in error tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 1696826] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Gaurav Nandode]

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

Public bug reported:

issue

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Thu Jun  8 18:08:55 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-05 (3 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

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

Status in gconf package in Ubuntu:
  New

Bug description:
  issue

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun  8 18:08:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-05 (3 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1696826/+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 1696827] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openss

[JQ]

Public bug reported:

I keep getting a error with dvd+rw-tools, install and remove.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libssl1.0.0: Configure
 dvd+rw-tools: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Jun  8 12:33:20 2017
ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-05-23 (16 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: package libssl1.0.0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  I keep getting a error with dvd+rw-tools, install and remove.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Configure
   dvd+rw-tools: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun  8 12:33:20 2017
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-23 (16 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this 

[Touch-packages] [Bug 1384503] Re: rsync fails on large files with compression

[David Britton]

After much discussion, this is too risky for an SRU without much more
demonstrated analysis.  It seems more appropriate for a backport.

** Changed in: rsync (Ubuntu Trusty)
   Status: Triaged => Won't Fix

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

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Won't Fix

Bug description:
  [Status]
  This issue is currently Incomplete.

  We're currently blocked on obtaining access to a reliable, and publicly 
  available dataset that can be shared to reproduce the issue.  The test
  is critical to being able to evaluate the impact of the change on other
  users when assessing if the fix can be SRU'ed to trusty.

  If you are affected by this bug and can reliably reproduce the issue
  with a specific dataset that you are willing and permitted to share please
  comment and specify the dataset location, and how you reproduce the issue.

  
  [Original Description]
  Copying large (>10GB) files with rsync -z (compression) leads to a long hang 
and eventual error after transferring part of the file.  The error is 
consistent.  The file copies at normal speed until it reaches its maximum size 
(1.4 GB out of 20 GB for one, 6.9 GB out of 29 GB for another).  Then nothing 
happens for a while (many minutes).  Finally, there is an error:

  []
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) 
[sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  Current package (both hosts):

  rsync:
    Installed: 3.1.0-2ubuntu0.1
    Candidate: 3.1.0-2ubuntu0.1
    Version table:
   *** 3.1.0-2ubuntu0.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.1.0-2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+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 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Andreas Hasenack]

Could you show the output you go? Or was it silent?

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

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+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 1696814] [NEW] add openjdk hs log to list of acceptable_fields in whoopsie

[Brian Murray]

Public bug reported:

This is for Tiago's openjdk apport package hook.

** Affects: whoopsie (Ubuntu)
 Importance: Undecided
 Assignee: Canonical Foundations Team (canonical-foundations)
 Status: New

** Changed in: whoopsie (Ubuntu)
Milestone: None => ubuntu-17.06

** Changed in: whoopsie (Ubuntu)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  add openjdk hs log to list of acceptable_fields in whoopsie

Status in whoopsie package in Ubuntu:
  New

Bug description:
  This is for Tiago's openjdk apport package hook.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+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 696435] Re: wait-for-root fails to detect nbd root

[ChristianEhrhardt]

** Tags added: bot-stop-nagging

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

Title:
  wait-for-root fails to detect nbd root

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Confirmed

Bug description:
  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1 
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop.  If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/696435/+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 1380702] Re: No keyboards shortcuts in QT apps

[Dmitry Shachnev]

All tests pass now, let’s hope the SRU team will let it migrate now.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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

Re: [Touch-packages] [Bug 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

[John Johnson]

OK , I ran that.

Ended with error code 1


John


On 06/08/2017 01:15 PM, Andreas Hasenack wrote:
> Thanks for filing this bug in Ubuntu.
>
> Could you please try the following:
>
> sudo apt -f install
>
> It's a bit odd that you have a 64bit system but have the 32bit version
> of the libgssapi-krb5-2 package, something else must have pulled that in
> explicitly.
>
> ** Changed in: krb5 (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+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 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Andreas Hasenack]

Thanks for filing this bug in Ubuntu.

Could you please try the following:

sudo apt -f install

It's a bit odd that you have a 64bit system but have the 32bit version
of the libgssapi-krb5-2 package, something else must have pulled that in
explicitly.

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

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

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+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 1689592] Re: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  its alert shows up whenever i turn on my notebook

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun May  7 18:41:19 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-01-27 (102 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1689592/+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 1696803] Re: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1689592, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1689592
   package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1

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

Title:
  package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  Problem after install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Jun  8 11:35:16 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-06-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1696803/+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 1696803] [NEW] package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Heizer Garcia]

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

Public bug reported:

Problem after install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Jun  8 11:35:16 2017
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
InstallationDate: Installed on 2017-06-08 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: sudo
Title: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK

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

Title:
  package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  Problem after install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Jun  8 11:35:16 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-06-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1696803/+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 1694149] Re: ssl error using urllib2

[Brian J. Murrell]

I wonder why this ticket has not even been triaged.

It was filed against an LTS release of Ubuntu.

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

Title:
  ssl error using urllib2

Status in python-defaults package in Ubuntu:
  New

Bug description:
  On Ubuntu 14.04.5 LTS with python 2.7.5-5ubuntu3 and
  libpython2.7-stdlib 2.7.6-8ubuntu0.3, using this little example
  program:

  #!/usr/bin/python

  import urllib2

  USER_AGENT = 'Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36
  (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36'

  defaultHeaders = {'User-Agent':USER_AGENT,
   
'Accept':"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8",
   'Accept-Encoding':'gzip,deflate,sdch',
   'Accept-Language':'en-US,en;q=0.8'}

  url = 
"https://ga.video.cdn.pbs.org/videos/ask-old-house/dcf0b26c-f7d1-4b1f-b1cf-2e521aa5e796/110577/hd-mezzanine-16x9/zq3zp3pg_ask1524-cove-16x9-hls-192-2500k.m3u8;
  req = urllib2.Request(url.encode('utf-8'), None, defaultHeaders)

  response = urllib2.urlopen(req, timeout=30)

  I get this result:

  $ python /tmp/urllib2-error.py
  Traceback (most recent call last):
File "/tmp/urllib2-error.py", line 15, in 
  response = urllib2.urlopen(req, timeout=30)
File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
  return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 404, in open
  response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 422, in _open
  '_open', req)
File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
  result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 1222, in https_open
  return self.do_open(httplib.HTTPSConnection, req)
File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open
  raise URLError(err)
  urllib2.URLError: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1694149/+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 1696799] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1696799

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  share/bleachbit/bleachbit/Command.py", line 131, in execute
  func_ret = self.func()
File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
  raise RuntimeError(line)
  RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
  Delete 1.1MB /var/cache/apt/archivesshare/bleachbit/bleachbit/Command.py", 
line 131, in execute
  func_ret = self.func()
File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
  raise RuntimeError(line)
  RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
  Delete 1.1MB /var/cache/apt/archives

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Install
   libssl1.0.0: Configure
   libssl1.0.0: Configure
   libssl-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun  8 12:29:11 2017
  DuplicateSignature:
   package:libssl1.0.0:i386:1.0.2g-1ubuntu4.8
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8) ...
   dpkg: error processing package libssl1.0.0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-30 (190 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696799/+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 1696799] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[chris]

Public bug reported:

share/bleachbit/bleachbit/Command.py", line 131, in execute
func_ret = self.func()
  File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
raise RuntimeError(line)
RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
Delete 1.1MB /var/cache/apt/archivesshare/bleachbit/bleachbit/Command.py", line 
131, in execute
func_ret = self.func()
  File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
raise RuntimeError(line)
RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
Delete 1.1MB /var/cache/apt/archives

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libssl1.0.0: Install
 libssl1.0.0: Configure
 libssl1.0.0: Configure
 libssl-dev: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Jun  8 12:29:11 2017
DuplicateSignature:
 package:libssl1.0.0:i386:1.0.2g-1ubuntu4.8
 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8) ...
 dpkg: error processing package libssl1.0.0:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-11-30 (190 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 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: openssl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  share/bleachbit/bleachbit/Command.py", line 131, in execute
  func_ret = self.func()
File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
  raise RuntimeError(line)
  RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
  Delete 1.1MB /var/cache/apt/archivesshare/bleachbit/bleachbit/Command.py", 
line 131, in execute
  func_ret = self.func()
File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
  raise RuntimeError(line)
  RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
  Delete 1.1MB /var/cache/apt/archives

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libssl1.0.0: Install
   libssl1.0.0: Configure
   libssl1.0.0: Configure
   libssl-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun  8 12:29:11 2017
  DuplicateSignature:
   package:libssl1.0.0:i386:1.0.2g-1ubuntu4.8
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.8) ...
   dpkg: error processing package libssl1.0.0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-30 (190 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1696799/+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 1696693] Re: Mousepad/trackpad not working

[Timo Aaltonen]

try booting an older kernel

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Mousepad/trackpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I booted my pc this morning and found that the trackpad is no longer
  responding. Moving it or clicking, there is no response.

  I did nothing special yesterday nor manually installed anything, the
  only thing that was installed was some new Ubuntu updates through the
  software updater.

  My laptop is an Asus ROG GL553VD with Ubuntu 16.04.2 LTS.

  Looking in the list of hardware to see if the trackpad is recognized,
  I found 'ITE Tech. Inc. ITE Device(8910)' which seems to be the name
  for my trackpad.

  I tried 'sudo apt-get install xserver-xorg-input-synaptics' but it
  said it was already up-to-date (version 1.8.2-1ubuntu3)

  I can't include the package name in this report as 'apt-cache policy
  pkgname' doesn't work ("N: Unable to locate package pkgname")

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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: Thu Jun  8 11:11:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
  InstallationDate: Installed on 2017-05-28 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic.efi.signed 
root=UUID=958dbae2-1028-43ae-af29-6fa03c950ee3 ro acpi_backlight=vendor quiet 
splash acpi_osi= vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.301:bd12/30/2016:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jun  8 10:44:13 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1631 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696693/+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 1696686] Re: ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry

[Bug Watch Updater]

** Changed in: binutils
   Status: Unknown => Fix Released

** Changed in: binutils
   Importance: Unknown => Medium

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

Title:
  ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to
  PLT entry

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  New

Bug description:
  When linking large applications, we sometimes see this error. This is
  affecting the LLVM ARM buildbots.

  The issue was fixed upstream:
  https://sourceware.org/bugzilla/show_bug.cgi?id=20608

  Could you please backport it to Xenial?

  I have applied the patch on top of binutils_2.26.1.orig.tar.gz + 
binutils_2.26.1-1ubuntu1~16.04.3.diff.gz as found here: 
  https://packages.ubuntu.com/xenial-updates/binutils-arm-linux-gnueabihf

  It applies cleanly (except the ChangeLog) and passes make check.

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

Re: [Touch-packages] [Bug 1695808] Re: tasks killed for nop (-1)

[Serge Hallyn]

Note, I'm happy to update a fix for this for a (and a -proposed one
for xenial).

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

Title:
  tasks killed for nop (-1)

Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  As the seccomp manpage points out, after seeing a SECCOMP_RET_TRACE, a
  tracer can set nr to -1 to skip the syscall. Similarly, one task could
  be debugging another seccomp'd task, simply doing PTRACE_SYSCALL
  without using SECCOMP_PTRACE, and want to make the tracee skip a
  syscall by setting nr to -1.

  However, the way libseccomp checks for X86_SYSCALL_BIT wrongly catches
  nr == -1. This kills any application using -1 to skip a syscall.  This
  means that any such application running under lxd, which uses
  libseccomp to set its seccomp policies, fails.

  libseccomp upstream has been fixed, see
  https://github.com/seccomp/libseccomp/issues/80 .  Ideally this fix
  would be cherrypicked into both artful and xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1695808/+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 1695808] Re: tasks killed for nop (-1)

[Joshua Powers]

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

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

Title:
  tasks killed for nop (-1)

Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  As the seccomp manpage points out, after seeing a SECCOMP_RET_TRACE, a
  tracer can set nr to -1 to skip the syscall. Similarly, one task could
  be debugging another seccomp'd task, simply doing PTRACE_SYSCALL
  without using SECCOMP_PTRACE, and want to make the tracee skip a
  syscall by setting nr to -1.

  However, the way libseccomp checks for X86_SYSCALL_BIT wrongly catches
  nr == -1. This kills any application using -1 to skip a syscall.  This
  means that any such application running under lxd, which uses
  libseccomp to set its seccomp policies, fails.

  libseccomp upstream has been fixed, see
  https://github.com/seccomp/libseccomp/issues/80 .  Ideally this fix
  would be cherrypicked into both artful and xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1695808/+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 1696686] Re: ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry

[Matthias Klose]

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

** Also affects: binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=20608
   Importance: Unknown
   Status: Unknown

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

Title:
  ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to
  PLT entry

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  New

Bug description:
  When linking large applications, we sometimes see this error. This is
  affecting the LLVM ARM buildbots.

  The issue was fixed upstream:
  https://sourceware.org/bugzilla/show_bug.cgi?id=20608

  Could you please backport it to Xenial?

  I have applied the patch on top of binutils_2.26.1.orig.tar.gz + 
binutils_2.26.1-1ubuntu1~16.04.3.diff.gz as found here: 
  https://packages.ubuntu.com/xenial-updates/binutils-arm-linux-gnueabihf

  It applies cleanly (except the ChangeLog) and passes make check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1696686/+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 1695900] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Joshua Powers]

Thank you for taking the time to file a bug report.

Looks like SSH or some other service was already bound to port 22.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I was doing a normal upgrade and this happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Jun  5 10:14:07 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-14 (110 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1695900/+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 1695900] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Joshua Powers]

>From Journal Log:

Jun 05 18:41:17 hostname sshd[1237]: error: Bind to port 22 on 0.0.0.0 failed: 
Address already in use.
Jun 05 18:41:17 hostname sshd[1237]: error: Bind to port 22 on :: failed: 
Address already in use.
Jun 05 18:41:17 hostname sshd[1237]: fatal: Cannot bind any address.

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I was doing a normal upgrade and this happened

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Jun  5 10:14:07 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-14 (110 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1695900/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[Steve Langasek]

** Changed in: debconf (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[Robert David]

Not sure if this is a coincidence or what, but I'm also using a Dell
Docking Station / Port replicator.

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

Title:
  External monitor connecting problem on Intel graphics card

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

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

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

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

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

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

[Giacomo Orlandi]

Version 4.4.0-72-generic seems to be the last version that works for
everyone here, on different systems. I renamed this bug to mention
Intel, but Shay Perlstein above had the same problem on NVidia.

@Kai-Heng could it be the same bug even if on different graphic drivers? Do you 
know if there is any code/module that is used for external monitors regardless 
of the graphics card?
For example this entry from the changelog sounds like it might be related:
  - drm/dp/mst: fix kernel oops when turning off secondary monitor

I should have mentioned that I have this problem using a Dell docking
station, and I have 2 external monitors connected to it, 1 connected
using the display port, the other one using DVI. It wasn't working when
using 2 display ports even before 4.4.0-72-generic.

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

Title:
  External monitor connecting problem on Intel graphics card

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

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

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

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

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

[Touch-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Colin Law]

@Willem, since this bug is specifically about invoking the HUD from
firefox, and it seems from your description that you are not using
firefox and you are not seeing the problem specifically when you open
the HUD, I think your problem does not fit the description of this bug.
You would probably be better to start a new bug.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in firefox source package in Xenial:
  Incomplete
Status in hud source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 1649692] Re: Tracker using 99% disk I/O

[Launchpad Bug Tracker]

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

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

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

Title:
  Tracker using 99% disk I/O

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I setup tracker not to operate when my system is busy. But still it's
  using lots of disk I/O.

  How to regenerate?
  1. Just open/restart your computer 
  2. run: sudo iotop
  3. It will show the disk I/O status, where tracker using 99%

  
  Disk I/O status:
  
https://s6.postimg.org/aqqdulmxt/Screenshot_Wed_Dec_14_2016_02_39_26_GMT_0600_(BD.png

  tracker-preference settings
  
https://s6.postimg.org/p8nl2le8x/Screenshot_Wed_Dec_14_2016_02_40_16_GMT_0600_(BD.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: tracker 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 14 02:43:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-11 (671 days ago)
  InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20141209)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to yakkety on 2016-11-09 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1649692/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[Robert David]

@Kai-Heng
4.4.0-72-generic

As long as I boot with that Kernel, I have no issues.  Every one after
that, just gives me the above issues.

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

Title:
  External monitor connecting problem on Intel graphics card

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

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

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

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

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

[Touch-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Willem Holleder]

Got the same problem on 17.04. I don't use Firefox. Using Thunderbird
and PHPStorm on daily basis. After some time (pretty random) unity-
panel-service takes all available RAM and I need to reboot to correct
the problem.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in firefox source package in Xenial:
  Incomplete
Status in hud source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/987060/+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 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown

[Chris Johnston]

** Tags added: sts

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

Title:
  Stopped (with error) ... messages on encrypted LVM shutdown

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Install (Default + crypted LVM) in Ubuntu Server s390x in Yakkety
  Daily

  Everything seems to work only on shutdown there is a bunch of "fail"
  messages related to the disks from systemd:

  [  OK  ] Stopped Network Time Synchronization.
  [   33.971312] systemd[1]: Stopped (with error) 
/dev/disk/by-id/dm-name-vda2_crypt.
  [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt.
  [   33.971469] systemd[1]: Stopped (with error) 
/dev/disk/by-id/dm-uuid-CRYPT-LUKS1-ef8aced3ceb640fe80c2c700c4504ccb-vda2_crypt.
  [FAILED] Stopped (with error) 
/dev/disk/by-i...40fe80c2c700c4504ccb-vda2_crypt.
  [   33.971595] systemd[1]: Stopped (with error) 
/dev/disk/by-id/lvm-pv-uuid-9hfIOG-dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq.
  [FAILED] Stopped (with error) 
/dev/disk/by-i...dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq.
  [FAILED] Stopped (with error) /dev/mapper/vda2_crypt.
  [FAILED] Stopped (with error) /dev/dm-0.
  [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0.
  [  OK  ] Stopped Create Volatile Files and Directories.
  [  OK  ] Stopped Raise network interfaces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1627950/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Kai Holthaus]

I've installed a system with the daily artful server image, and the
error is not present for me. However, I'm not sure how useful that test
is, given that I didn't experience the error during a fresh install of
xenial.

I've attached the journal from the artful install, and it looks to me
like the steps are now in the right order. Was adding "iscsid.service"
to the "after" and "wants" lines in /lib/systemd/system/open-
iscsi.service the only change that was required? If so, I'd be happy to
test that on my server that's experiencing the issue...

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+attachment/4892287/+files/journal.txt

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

[Jamie Strandboge]

Is this still an issue with 1.2.6-0ubuntu0.16.04.3 in 16.04? I see that
Ken applied the patch I identified in
https://bugzilla.gnome.org/show_bug.cgi?id=767317 to fix
https://bugs.launchpad.net/ubuntu/+source/network-manager-
applet/+bug/1641889, which references a different upstream bug.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[Shay Perlstein]

I jumped to 4.10.1-041001-generic since I failed to go back to 4.4.0-72 which 
used to work, everything is working again as it should without any problem, I 
am now using the latest nvidia driver 381.22 (, also 378.13 worked perfectly 
fine). 
The kernel version definitely makes a difference 

BTW on 4.4.0-79 the log error has disappeared but the issue still
exists, I tested 4.4.0-79 with both nvidia and Nouveau drivers.

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

Title:
  External monitor connecting problem on Intel graphics card

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

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

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

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

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

[Touch-packages] [Bug 1696735] [NEW] package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti

[John Johnson]

Public bug reported:

unknown

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun  8 08:22:46 2017
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-02-12 (481 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: krb5
Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  New

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+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 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[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 krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1696735

Title:
  package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in krb5 package in Ubuntu:
  New

Bug description:
  unknown

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun  8 08:22:46 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (481 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+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 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown

[Chris Johnston]

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/1620
   Importance: Unknown
   Status: Unknown

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

Title:
  Stopped (with error) ... messages on encrypted LVM shutdown

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Install (Default + crypted LVM) in Ubuntu Server s390x in Yakkety
  Daily

  Everything seems to work only on shutdown there is a bunch of "fail"
  messages related to the disks from systemd:

  [  OK  ] Stopped Network Time Synchronization.
  [   33.971312] systemd[1]: Stopped (with error) 
/dev/disk/by-id/dm-name-vda2_crypt.
  [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt.
  [   33.971469] systemd[1]: Stopped (with error) 
/dev/disk/by-id/dm-uuid-CRYPT-LUKS1-ef8aced3ceb640fe80c2c700c4504ccb-vda2_crypt.
  [FAILED] Stopped (with error) 
/dev/disk/by-i...40fe80c2c700c4504ccb-vda2_crypt.
  [   33.971595] systemd[1]: Stopped (with error) 
/dev/disk/by-id/lvm-pv-uuid-9hfIOG-dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq.
  [FAILED] Stopped (with error) 
/dev/disk/by-i...dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq.
  [FAILED] Stopped (with error) /dev/mapper/vda2_crypt.
  [FAILED] Stopped (with error) /dev/dm-0.
  [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0.
  [  OK  ] Stopped Create Volatile Files and Directories.
  [  OK  ] Stopped Raise network interfaces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1627950/+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 1682104] Re: sudo rules based on group membership from freeipa does not work

[Oscar Carlberg]

The problem persists in the most recent 1.8.16-0ubuntu1.4

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

Title:
  sudo rules based on group membership from freeipa does not work

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  When upgrading sudo package in xenial from version 1.8.16-0ubuntu1 to
  1.8.16-0ubuntu1.3, our FreeIPA-based sudo rules suddenly stopped
  working. We have setup a group in FreeIPA called ldap_nopass, and
  configured hbac rules to allow users in this group to run sudo
  (without password / nopasswd). This have been working fine up until
  now when we upgraded the sudo package. Downgrading to 1.8.16-0ubuntu1
  resolves the issue. It also work with 1.8.16-0ubuntu1.3 if we set
  use_fully_qualified_names = False in /etc/sssd/sssd.conf, but this is
  not an option for us.

  This led me to believe this issue is related to upstream bug: 
  https://bugzilla.sudo.ws/show_bug.cgi?id=757

  And most likely is caused by the patchset from 1.3
  https://launchpad.net/ubuntu/+source/sudo/1.8.16-0ubuntu1.3

  Unfortunately, 1.8.16-0ubuntu1.2 binaries seems to be deleted from
  mirrors, so I cannot try this version.

  I've included the auth.log file showing the difference using sudo
  1.8.16-0ubuntu1 vs 1.8.16-0ubuntu1.3. Real username and domain has
  been redacted to user.name and example.com

  Please let me know if any additional information is required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1682104/+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 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system

[amichair]

Thanks for the analysis @atom, I think that explains my issue as well -
I had a long-running rsync in parallel. Once killed, the update worked.

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

Title:
  update-initramfs hangs on upgrade, dpkg unusable, unbootable system

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  At least four users, including myself, are having an issue with
  update-initramfs hanging while updating ubuntu 16.04. The bug has been
  documented while attempting an update to multiple kernel versions (
  4.4.0-24, 4.4.0-62,  4.4.0-63). The bug causes any apt-get update or
  install to fail, and may also lead to an unbootable system.

  User #1 (me):
  $ uname -a
  Linux  4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo apt-get upgrade
  Fetched 1,571 MB in 2min 9s (12.2 MB/s)   
  
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  (Reading database ... 344634 files and directories currently installed.)
  Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ...
  Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for cracklib-runtime (2.9.2-1build2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic

   Uh oh! Let's try to troubleshoot.

  $ sudo killall dpkg
  $ sudo dpkg --configure -a
  Setting up initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: deferring update (trigger activated)
  Setting up base-files (9.4ubuntu4.4) ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  initrd.img(/boot/initrd.img-4.4.0-63-generic
  ) points to /boot/initrd.img-4.4.0-63-generic
   (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  vmlinuz(/boot/vmlinuz-4.4.0-63-generic
  ) points to /boot/vmlinuz-4.4.0-63-generic
   (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic
  ^CFailed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-63-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-4.4.0-63-generic; however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-signed-image-4.4.0-63-generic:
   linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic 
(= 4.4.0-63.84); however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-signed-image-4.4.0-63-generic 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-signed-image-generic:
   linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; 
however:
Package linux-signed-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-signed-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-image-extra-4.4.0-63-generic:
   linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; 
however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-image-extra-4.4.0-63-generic 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   

[Touch-packages] [Bug 1696717] Re: tzdata stills apply DST for Mongolia

[Luis Filipe Domingues]

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

** This bug has been marked a duplicate of bug 1691092
   outdated timezone information for Mongolia

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

Title:
  tzdata stills apply DST for Mongolia

Status in tzdata package in Ubuntu:
  New

Bug description:
  Since 2017 Mongolia does not apply DST time.

  However, on Ubuntu 16.04, the DST time is still applied, so my
  computers are 1h ahead.

  Here you have the output of timedatectl:
Local time: Thu 2017-06-08 20:10:37 ULAST
Universal time: Thu 2017-06-08 11:10:37 UTC
  RTC time: Thu 2017-06-08 11:10:37
 Time zone: Asia/Ulaanbaatar (ULAST, +0900)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  And the same command in Debian Stretch:
Local time: jeu 2017-06-08 19:10:27 +08
Universal time: jeu 2017-06-08 11:10:27 UTC
  RTC time: jeu 2017-06-08 11:10:27
 Time zone: Asia/Ulaanbaatar (+08, +0800)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  The current installed package is:
  tzdata:
Installed: 2016j-0ubuntu0.16.04
Candidate: 2016j-0ubuntu0.16.04

  
  Please remove DST for Ulaanbaatar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1696717/+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 1696717] [NEW] tzdata stills apply DST for Mongolia

[Luis Filipe Domingues]

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

Public bug reported:

Since 2017 Mongolia does not apply DST time.

However, on Ubuntu 16.04, the DST time is still applied, so my computers
are 1h ahead.

Here you have the output of timedatectl:
  Local time: Thu 2017-06-08 20:10:37 ULAST
  Universal time: Thu 2017-06-08 11:10:37 UTC
RTC time: Thu 2017-06-08 11:10:37
   Time zone: Asia/Ulaanbaatar (ULAST, +0900)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

And the same command in Debian Stretch:
  Local time: jeu 2017-06-08 19:10:27 +08
  Universal time: jeu 2017-06-08 11:10:27 UTC
RTC time: jeu 2017-06-08 11:10:27
   Time zone: Asia/Ulaanbaatar (+08, +0800)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

The current installed package is:
tzdata:
  Installed: 2016j-0ubuntu0.16.04
  Candidate: 2016j-0ubuntu0.16.04


Please remove DST for Ulaanbaatar.

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

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

Title:
  tzdata stills apply DST for Mongolia

Status in tzdata package in Ubuntu:
  New

Bug description:
  Since 2017 Mongolia does not apply DST time.

  However, on Ubuntu 16.04, the DST time is still applied, so my
  computers are 1h ahead.

  Here you have the output of timedatectl:
Local time: Thu 2017-06-08 20:10:37 ULAST
Universal time: Thu 2017-06-08 11:10:37 UTC
  RTC time: Thu 2017-06-08 11:10:37
 Time zone: Asia/Ulaanbaatar (ULAST, +0900)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  And the same command in Debian Stretch:
Local time: jeu 2017-06-08 19:10:27 +08
Universal time: jeu 2017-06-08 11:10:27 UTC
  RTC time: jeu 2017-06-08 11:10:27
 Time zone: Asia/Ulaanbaatar (+08, +0800)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  The current installed package is:
  tzdata:
Installed: 2016j-0ubuntu0.16.04
Candidate: 2016j-0ubuntu0.16.04

  
  Please remove DST for Ulaanbaatar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1696717/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[RATAN]

** Changed in: debconf (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Incomplete

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1696710] [NEW] Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[bugproxy]

Public bug reported:

== Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
---Problem Description---
depmod does not handle .TOC symbol on powerpc platforms
 
Contact Information = Douglas Miller  
 
---uname output---
Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = other 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
 
Userspace tool common name: depmod 
 
The userspace tool has the following bit modes: 64 

Userspace rpm: libkmod2:ppc64el

Userspace tool obtained from project website:  na 
 
*Additional Instructions for Douglas Miller :
-Attach ltrace and strace of userspace application.

== Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
kmod package:

# dpkg --list |grep kmod
ii  kmod   22-1ubuntu4  
   ppc64el  tools for managing Linux kernel modules
ii  libkmod2:ppc64el   22-1ubuntu4  
   ppc64el  libkmod shared library

== Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
 I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh install 
and still getting these messages. In the "make modules_install" output I see:

...
  DEPMOD  4.12.0-rc4
depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
ol .TOC.
...

** Affects: ubuntu-power-systems
 Importance: Undecided
 Assignee: Canonical Server Team (canonical-server)
 Status: New

** Affects: kmod (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-150912 severity-medium 
targetmilestone-inin16042

** Tags added: architecture-ppc64le bugnameltc-150912 severity-medium
targetmilestone-inin16042

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: ubuntu => kmod (Ubuntu)

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  New
Status in kmod package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+subscriptions

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

[Touch-packages] [Bug 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[Frank Heimes]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  New
Status in kmod package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+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 1696710] [NEW] Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
---Problem Description---
depmod does not handle .TOC symbol on powerpc platforms
 
Contact Information = Douglas Miller  
 
---uname output---
Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = other 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
 
Userspace tool common name: depmod 
 
The userspace tool has the following bit modes: 64 

Userspace rpm: libkmod2:ppc64el

Userspace tool obtained from project website:  na 
 
*Additional Instructions for Douglas Miller :
-Attach ltrace and strace of userspace application.

== Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
kmod package:

# dpkg --list |grep kmod
ii  kmod   22-1ubuntu4  
   ppc64el  tools for managing Linux kernel modules
ii  libkmod2:ppc64el   22-1ubuntu4  
   ppc64el  libkmod shared library

== Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
 I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh install 
and still getting these messages. In the "make modules_install" output I see:

...
  DEPMOD  4.12.0-rc4
depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
ol .TOC.
...

** Affects: kmod (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-150912 severity-medium 
targetmilestone-inin16042
-- 
Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol .TOC.
https://bugs.launchpad.net/bugs/1696710
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to kmod in Ubuntu.

-- 
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 1380702] Re: No keyboards shortcuts in QT apps

[Elvis Stansvik]

Ah, thanks. Did not know about that page. Thanks for looking into it.

(My primary interest is not actually this fix, but the mouse event
compression SRU that got piggybacked into it:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1598173).

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+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