[Touch-packages] [Bug 1750832] Re: xorg crash after coming from suspend

[Launchpad Bug Tracker]

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

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

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

Title:
  xorg crash after coming from suspend

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The problem i'm facing is, whenever my system revives back from
  suspended state, xorg crashes and i have restart all the applications
  that were running in the previous xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.15.3-041503-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  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.6)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Feb 21 19:42:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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-08-15 (189 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.3-041503-generic 
root=UUID=ae3afa91-6139-4a8a-a15b-39b661535c3a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  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.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 19:23:46 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750832/+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 1751120] Re: Xorg freeze when moving a window between external/internal monitors

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze when moving a window between external/internal monitors

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My mouse cursor would still move, but I couldn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 13:44:42 2018
  DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad T440p [17aa:220e]
  InstallationDate: Installed on 2017-10-23 (121 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20ANCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-01-23 (30 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET70WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751120/+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 1751410] Re: xorg issue

[Launchpad Bug Tracker]

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

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

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

Title:
  xorg issue

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Firefox or Chrome will crash very often.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb 23 22:35:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] 
[1002:9996] (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Richland [Radeon HD 8470D] 
[1458:d000]
  InstallationDate: Installed on 2016-10-29 (482 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88X-D3HP
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Feb 23 22:30:00 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751410/+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 1759836] Re: systemd-udevd consumes 100% of CPU

[Lumar]

The bug is present on my system.
It was temporarily solved with workaround from 
https://dev.solus-project.com/T5224, but I don't use Bluetooth and so don't 
know if it is now working.

* Infos from uname
Linux 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:15:38 UTC 2018 i686 i686 
i686 GNU/Linux
Ubuntu 4.15.0-20.21-generic 4.15.17

* From dmidecode
System Information
Manufacturer: Dell Inc.
Product Name: Vostro 3700
Version: A10

Base Board Information
Manufacturer: Dell Inc.
Product Name: 07VWR8
Version: A10
Features:
Board is a hosting board
Board is replaceable
Type: Motherboard

OEM Strings
String 1: Dell System
String 2: 5[0003]
String 3: 13[PP41L]

BIOS Information
Vendor: Dell Inc.
Version: A10
Release Date: 10/25/2010
Address: 0xF
Runtime Size: 64 kB
ROM Size: 2048 kB
Characteristics:
MCA is supported
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 1.254
Firmware Revision: 1.254

* From /sys/kernel/debug/usb/devices
T:  Bus=01 Lev=03 Prnt=03 Port=02 Cnt=03 Dev#=  7 Spd=12   MxCh= 0
D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=413c ProdID=8160 Rev= 1.73
S:  Manufacturer=Dell Computer Corp
S:  Product=Dell Wireless 365 Bluetooth Module
C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)

* From udevadm
UDEV  [947.284638] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[947.289860] bind 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)
KERNEL[947.290052] unbind   
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb)

* From journalctl
mag 18 17:07:42 upowerd[10489]: unhandled action 'bind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0
mag 18 17:07:42 systemd-udevd[323]: Process 'hid2hci --method=dell  
--devpath=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0' 
failed with exit code 1.
mag 18 17:07:42 upowerd[10489]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0

* From systemd-udevd
'hid2hci --method=dell 
--devpath=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0'(err)
 'error: switching device 
'/sys//devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0' 
failed.'

* From /proc/modules
btusb 40960 0 - Live 0xf8ae7000
btrtl 16384 1 btusb, Live 0xf8957000
btbcm 16384 1 btusb, Live 0xf88ea000
btintel 16384 1 btusb, 

Re: [Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Seth Arnold]

On Fri, May 18, 2018 at 06:01:19PM -, Oliver Grawert wrote:
> well, my subtle hint would point to simply add it to /etc/environment
> here, which would globally cover for everything, would allow us to drop

Note that /etc/environment is only used by PAM-aware services that have
been configured to use pam_env in the corresponding /etc/pam.d/ files.

systemd will not use PAM when launching services.

This might still match your idea of "everything" but I wanted to make
sure.

Thanks

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1772130] [NEW] [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all

[Jorge Machuca]

Public bug reported:

Headphones worked for a while. After restart no sound at all

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jmachuca   7895 F pulseaudio
CurrentDesktop: Unity
Date: Fri May 18 21:20:36 2018
InstallationDate: Installed on 2018-03-22 (57 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jmachuca   7895 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/13/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.44
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8259
dmi.board.vendor: HP
dmi.board.version: 83.71
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.44:bd12/13/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.71:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Omen
dmi.product.name: OMEN by HP Laptop
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug xenial

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

Title:
  [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Headphones worked for a while. After restart no sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmachuca   7895 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 18 21:20:36 2018
  InstallationDate: Installed on 2018-03-22 (57 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmachuca   7895 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.44
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8259
  dmi.board.vendor: HP
  dmi.board.version: 83.71
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.44:bd12/13/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.71:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Omen
  dmi.product.name: OMEN by HP Laptop
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1772130/+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 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Mathieu Trudel-Lapierre]

Verification-doen for xenial: nplan 0.32~16.04.5

Verified that booting a NFS-based remote root system works correctly
when /run/netplan/ens3.yaml is written; 'critical: true' is recognized
as a valid option in the YAML.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+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 1769920] Re: [SRU] Enable support for Rocky Cloud Archive

[Brian Murray]

Hello Corey, or anyone else affected,

Accepted software-properties into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.24.32.3 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: software-properties (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  [SRU] Enable support for Rocky Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Cosmic:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:rocky
 cloud-archive:rocky-proposed

  This will also need to be SRU'ed back to bionic.

  [Impact]
  End users have to manually enable the rocky cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:rocky
  sudo add-apt-repository cloud-archive:rocky-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769920/+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 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration

[Andreas Schildbach]

I'm using Ubuntu, not Xubuntu. I never tried to manually execute the
script. I simply removed the file and rebooted – problem gone.

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

Title:
  Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware
  acceleration

Status in nux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 18.04 on a very plain Intel Skylake
  graphics, hardware acceleration is gone. Glxinfo and System
  Information report 'llvmpipe' (software rasterizer)

  It is caused by the file
  /etc/X11/Xsession.d/50_check_unity_support
  which can be deleted and then this problem goes away.

  > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520
  (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglvnd0 1.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:24:48 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-21 (735 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+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 1752053] Re: nvidia-390 fails to boot graphical display

[claudio@ubuntu]

So, if this bug is marked as "fixed released" and 500 comments further
it's clear it doesn't fix anything, should we open a new bug report?

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1772117] [NEW] xorg server

[jean Marc trony]

Public bug reported:

x11

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: i386
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri May 18 22:55:35 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
InstallationDate: Installed on 2016-10-19 (576 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: LENOVO 6475AG9
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=f2c844dc-cf64-4e07-87c5-50617f11c61e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET46WW (1.16 )
dmi.board.name: 6475AG9
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: L002843
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7UET46WW(1.16):bd09/24/2008:svnLENOVO:pn6475AG9:pvrThinkPadT400:rvnLENOVO:rn6475AG9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 6475AG9
dmi.product.version: ThinkPad T400
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri May 18 22:36:56 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages 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/1772117

Title:
  xorg server

Status in xorg package in Ubuntu:
  New

Bug description:
  x11

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri May 18 22:55:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2016-10-19 (576 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: LENOVO 6475AG9
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=f2c844dc-cf64-4e07-87c5-50617f11c61e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET46WW (1.16 )
  

[Touch-packages] [Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion

[Dan Streetman]

trusty:

root@lp1701023:~# dpkg -l | grep ifupdown
ii  ifupdown 0.7.47.2ubuntu4.4  
amd64high level tools to configure network interfaces
root@lp1701023:~# dpkg -l | grep vlan
ii  vlan 1.9-3ubuntu10.5
amd64user mode programs to enable VLANs on your ethernet devices
root@lp1701023:~# 

I verified comment 19 tests all passed (ifup -a, reboot, hotplug) as
expected for these pkg versions.

I also verified with the e/n/i config from this bug's description does
cause the hang failure as expected (tested with ifup -a).


root@lp1701023:/etc/network/interfaces.d# dpkg -l | grep ifupdown
ii  ifupdown 0.7.47.2ubuntu4.5  
amd64high level tools to configure network interfaces
root@lp1701023:/etc/network/interfaces.d# dpkg -l | grep vlan
ii  vlan 1.9-3ubuntu10.6
amd64user mode programs to enable VLANs on your ethernet devices


With the updated -proposed pkgs, I verified it passes all comment 19 tests 
(ifup -a, reboot, hotplug).

I also verified that the e/n/i config from this bug's description does
not hang, and properly brings up all configured interfaces with the
right config (for ifup -a, reboot, and hotplug).

** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

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

Title:
  (on trusty) version 1.9-3ubuntu10.4 regression blocking boot
  completion

Status in ifupdown package in Ubuntu:
  In Progress
Status in vlan package in Ubuntu:
  Fix Released
Status in ifupdown source package in Trusty:
  Fix Committed
Status in vlan source package in Trusty:
  Fix Committed
Status in ifupdown source package in Xenial:
  Fix Committed
Status in vlan source package in Xenial:
  Fix Committed
Status in ifupdown source package in Artful:
  Fix Committed
Status in vlan source package in Artful:
  Fix Committed
Status in ifupdown source package in Bionic:
  Fix Committed
Status in vlan source package in Bionic:
  Fix Committed
Status in ifupdown package in Debian:
  Fix Released
Status in vlan package in Debian:
  New

Bug description:
  [impact]

  in bug 1573272, the vlan pkg was changed to perform a full ifup inside
  its if-pre-up.d/vlan script.  This allowed correct ordering of ifup
  for a vlan and its raw-device, as previously there was a race
  condition between them (see that bug for details).

  However, this causes hangs during ifup with certain specific configs.
  The reasons are given starting in comment 13.

  The result is a regression for those using the specific ifupdown
  configs; when they try to reboot and/or ifup -a, it will hang trying
  to bring up their network, preventing boot from finishing (or hanging
  before the network is fully configured).

  [test case]

  upgrade to the latest vlan package and configure the system with an
  affected ifupdown config, then reboot.  The reboot will hang while
  trying to bring the network up.

  see the original description below for an example ifupdown config to
  reproduce this, although there are other possible configs that
  will/may trigger this regression.

  [regression potential]

  The fix for this moves the creation of the vlan(s) corresponding to a
  physical raw-device 'hotplug' event out of the udev processing path
  for the raw-device, and into an ifup post script for the raw-device
  ifup.  If this is not done correctly, then any interfaces that are
  hotplugged, and have vlans configured on them, may fail to correctly
  create/configure their vlan(s).

  This change does remove the direct call to ifup from the if-pre-up.d
  (or if-up.d) scripts, so there should not be any regression potential
  for more ifup deadlocks.

  [other info]

  this required both ifupdown and vlan to be patched.  vlan was patched
  to remove the problematic call to ifup from the vlan pre-up script,
  and add a call to create the vlan interface(s) from a new post-up
  script, as well as adding a parameter to vlan-network-interface script
  to handle the call from udev itself differently than a call from
  elsewhere (such as the if-up.d/vlan script).  this works for bootup
  and ifup/ifup -a, but fails for device hotplug because of a bug in
  ifupdown that prevents calling ifquery from an ifup script; that has
  been patched upstream already, and is the only ifupdown change needed
  here.

  
  [original description]

  When upgrading from version 1.9-3ubuntu10.1, a previously working
  machine can't successfully reboot completely.

  ifup is hanging indefinitely, with this process structure (from
  "pstree -a 1299"):

  ifup,1299 -a
    └─run-parts,1501 /etc/network/if-pre-up.d
    

[Touch-packages] [Bug 1772109] Re: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot

[teo1978]

Interestingly, killing the "at-spi2-registr" process has made Xorg's CPU
consumption go down to normal.

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

Title:
  Xorg consuming 50% CPU for no good reason, at-spi2-registr another
  20%, non-stop since boot

Status in xorg package in Ubuntu:
  New

Bug description:
  I have booted the computer about half an hour ago. Since the very
  beginning, I noticed the fan spinning at high spin so I launched
  "top", and noticed that Xorg was consuming about 50% CPU and another
  process called "at-spi2-registr" is consuming another 20%.

  Since then, They have continued consuming that amount of CPU
  constantly, all the time, whether or not I was doing anything. The
  only applications I opened are a terminal where I'm running top and
  the browser where I've been browsing Facebook. Before I launched the
  browser and after I closed it, CPU usage by these processed has never
  gone below 50% and 20% respectively.

  This is fucking ridiculous.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  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: Fri May 18 22:17:40 2018
  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: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (1680 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 18 21:44:15 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772109/+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 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration

[Brian Murray]

The mentioned file,/etc/X11/Xsession.d/50_check_unity_support, should
only run on systems using Xubuntu. Is that what everyone is using?

Additionally, I tried to recreate this by uninstalling unity but
unity_support_test still passes for me.

[  1:24PM 10282 ]  [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ]
 $ /usr/lib/nux/unity_support_test; echo $?
0
[  1:24PM 10283 ]  [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ]
[  1:24PM 10285 ]  [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ]
 $ sudo apt-get remove unity
[sudo] password for bdmurray: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  gtk3-nocsd libgtk3-nocsd0 python3-feedparser session-shortcuts 
unity-scope-calculator unity-scope-chromiumbookmarks unity-scope-colourlovers
  unity-scope-devhelp unity-scope-firefoxbookmarks unity-scope-home 
unity-scope-manpages unity-scope-openclipart unity-scope-texdoc
  unity-scope-virtualbox unity-scope-yelp unity-scope-zotero 
unity-scopes-master-default
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  unity unity-session unity-tweak-tool
0 upgraded, 0 newly installed, 3 to remove and 13 not upgraded.
After this operation, 9,766 kB disk space will be freed.
Do you want to continue? [Y/n] Y
[  1:25PM 10286 ]  [ bdmurray@impulse:~/source-trees/metarelease/ubuntu ]
 $ /usr/lib/nux/unity_support_test; echo $?
0

Is the unity_support_test failing for you all?

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

Title:
  Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware
  acceleration

Status in nux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 18.04 on a very plain Intel Skylake
  graphics, hardware acceleration is gone. Glxinfo and System
  Information report 'llvmpipe' (software rasterizer)

  It is caused by the file
  /etc/X11/Xsession.d/50_check_unity_support
  which can be deleted and then this problem goes away.

  > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520
  (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglvnd0 1.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:24:48 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-21 (735 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+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 1772109] [NEW] Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot

[teo1978]

Public bug reported:

I have booted the computer about half an hour ago. Since the very
beginning, I noticed the fan spinning at high spin so I launched "top",
and noticed that Xorg was consuming about 50% CPU and another process
called "at-spi2-registr" is consuming another 20%.

Since then, They have continued consuming that amount of CPU constantly,
all the time, whether or not I was doing anything. The only applications
I opened are a terminal where I'm running top and the browser where I've
been browsing Facebook. Before I launched the browser and after I closed
it, CPU usage by these processed has never gone below 50% and 20%
respectively.

This is fucking ridiculous.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
NonfreeKernelModules: nvidia_uvm 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  340.104  Thu Sep 14 17:13:13 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
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: Fri May 18 22:17:40 2018
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: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (1680 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri May 18 21:44:15 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 NVIDIA(0): Failed to initiate mode change.
 NVIDIA(0): Failed to complete mode change
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7

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

Title:
  Xorg consuming 50% CPU for no good reason, at-spi2-registr another
  20%, non-stop since boot

Status in xorg package in Ubuntu:
  New

Bug description:
  I have booted the computer about half an hour ago. Since the very
  beginning, I noticed the fan spinning at high spin so I launched
  "top", and noticed that Xorg was consuming about 50% CPU and another
  process called "at-spi2-registr" is consuming another 20%.

  Since then, They have continued consuming that amount of CPU
  constantly, all the time, whether or not I was doing anything. The
  only applications I opened are a terminal where 

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

[Julian Andres Klode]

Oh, you got a working result? I tried aspcud in various variants, but I
don't get any solutions. https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=897330

Of course the autopkgtest-sat-dep package should have versioned
dependencies and/or on the command-line, versions should be specified
IMO.

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

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

Title:
  Non-pinned available package in -proposed not chosen

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid

Bug description:
  In autopkgtest we just had this situation:

  root@humorous-bullfrog:~# cat /etc/apt/preferences
  Package: *
  Pin: release a=bionic
  Pin-Priority: 990

  Package: python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-venv
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-stdlib
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-examples
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-testsuite
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: idle-python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-doc
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995
  root@humorous-bullfrog:~# apt -oDebug::pkgProblemResolver=true full-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (0) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (1) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (1) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (2) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (2) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 15
Removing dh-python:amd64 rather than change python3-distutils:amd64
  Investigating (3) python3:amd64 < 3.6.4-1 @ii mK Ib >
  Broken python3:amd64 Depends on dh-python:amd64 < 3.20180325ubuntu2 @ii mR >
Considering dh-python:amd64 22 as a solution to python3:amd64 40
Added dh-python:amd64 to the remove list
Fixing python3:amd64 via keep of dh-python:amd64
  Investigating (3) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >

[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen

[Paul Gevers]

Hmm, maybe it was just the syntax being wrong. The following line at
least succeeded:

--solver aspcud -o APT::Solver::Strict-Pinning=false -o
APT::Solver::aspcud::Preferences='-removed,-changed,-new,+count(solution
,APT-Pin:=/995/)'

Next up, checking that it does what I want.

Just a worry that came up thinking about the request to aspcud: I think
it is allowed to come up with solutions that don't involve any package
from -proposed/unstable. So I think that if we go this route (and I
think we should/must, not only for the issue encountered in this bug),
autopkgtest must check that packages from the triggers are NOT from
!-proposed/testing.

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

Title:
  Non-pinned available package in -proposed not chosen

Status in Auto Package Testing:
  New
Status in apt package in Ubuntu:
  Invalid

Bug description:
  In autopkgtest we just had this situation:

  root@humorous-bullfrog:~# cat /etc/apt/preferences
  Package: *
  Pin: release a=bionic
  Pin-Priority: 990

  Package: python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-venv
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-stdlib
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-minimal
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-examples
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dev
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-testsuite
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: idle-python3.6
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-doc
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: python3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995

  Package: libpython3.6-dbg
  Pin: release a=bionic-proposed
  Pin-Priority: 995
  root@humorous-bullfrog:~# apt -oDebug::pkgProblemResolver=true full-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (0) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (1) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (1) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15
Added python3-distutils:amd64 to the remove list
Fixing dh-python:amd64 via keep of python3-distutils:amd64
  Investigating (2) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU 
Ib >
  Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 
3.6.5~rc1-1 @ii mK > (< 3.6.5-2)
Considering python3-distutils:amd64 7 as a solution to 
libpython3.6-stdlib:amd64 22
Added python3-distutils:amd64 to the remove list
Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64
  Investigating (2) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib >
  Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii 
mR >
Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 15
Removing dh-python:amd64 rather than change python3-distutils:amd64
  Investigating (3) python3:amd64 < 3.6.4-1 @ii mK Ib >
  Broken python3:amd64 Depends on dh-python:amd64 < 3.20180325ubuntu2 @ii mR >
Considering dh-python:amd64 22 as a solution to python3:amd64 40
Added 

[Touch-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade

[MegaBrutal]

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

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

Title:
  Software rendering is forced after 18.04 upgrade

Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.04, my desktop uses software rendering, no 
matter what I do.
  As far as I know, all necessary packages are installed.
  Formerly I had oibaf installed, but suspecting that this may cause the 
problem, I removed it with ppa-purge. It didn't help.

  First I noticed the problem when I tried to play HD videos.
  It was fine before the upgrade. My hardware is capable for 3D acceleration, 
as it worked on 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 06:13:09 2018
  DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2014-06-10 (1432 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 6474B84
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 6474B84
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T400
  dmi.product.name: 6474B84
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun May 13 06:01:23 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Dimitri John Ledkov]

On 18 May 2018 at 19:01, Oliver Grawert  wrote:
> well, my subtle hint would point to simply add it to /etc/environment
> here, which would globally cover for everything, would allow us to drop
> the profile.d snippet in ubuntu images/installs and to my knowledge
> would even be used by systemd (or am i wrong here ?) ...
>
> (and i think it would even work for zsh)
>

Sorry, I do not have time for subtle hints.

As you are well aware, snapd cannot modify /etc/environment; (not
owned by it, it is freeform text, can contain anything, may or may not
have PATH setting, not-upgradable, so on and so forth)
said file is not used by systemd;
it would not cover things globally;
and specifically it would not cover things across other distributions.

There are reasons why integration snippet was shipped by snapd in
profile.d, and all of those reasons still stand.

And more-over the ethos for snapd packaging is to integrate into as
many systems as possible, in a native way.
Shipping appropriate system-environment-generators will achieve that
not only on Ubuntu classic installs but on any systemd-based Linux
distros too, which my understanding is the scope for the snapd
project.

-- 
Regards,

Dimitri.

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Cosmic)
   Status: Confirmed => Fix Committed

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+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 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)

[Dimitri John Ledkov]

** Description changed:

  Cherrypick
- 
https://github.com/systemd/systemd/commit/3776f9cf00b163eedeb0325691d23df11385cbc5
+ 
https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a
  
  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this CPUID
  information when detecting Xen, and thus it erroneously assumes that the
  guest is running under Hyper-V. This causes Xen-related services (and
  anything else that relies on systemd's VM-detection functionality) to
  fail.
  
  I *believe* this is a regression from systemd 229 as used in Xenial — we
  have at least a few Xen-based VMs that report as Hyper-V via CPUID and
  don't have this issue on that version — but i haven't confirmed that for
  certain.
  
  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:
  
  https://github.com/systemd/systemd/issues/8844
  
  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.
  
  Thanks!
  
  See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573
  
  ---
  
  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  
  % apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10
    Candidate: 237-3ubuntu10
    Version table:
   *** 237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  systemd sometimes misdetects Xen VMs (fixed up-stream)

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  Cherrypick
  
https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a

  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this
  CPUID information when detecting Xen, and thus it erroneously assumes
  that the guest is running under Hyper-V. This causes Xen-related
  services (and anything else that relies on systemd's VM-detection
  functionality) to fail.

  I *believe* this is a regression from systemd 229 as used in Xenial —
  we have at least a few Xen-based VMs that report as Hyper-V via CPUID
  and don't have this issue on that version — but i haven't confirmed
  that for certain.

  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:

  https://github.com/systemd/systemd/issues/8844

  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.

  Thanks!

  See also:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573

  ---

  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  % apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10
    Candidate: 237-3ubuntu10
    Version table:
   *** 237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768104/+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 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"

[Dimitri John Ledkov]

@Daniel van Vugt (vanvugt)

Does pressing Enter causes the system to reboot, after it hangs?

Do you see a plymouth purple screen instructing you to remove
installation media and hit enter?

Do you see a console text message instructing you to "Remove
installation media and reboot" (meaning hard-reset)?

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

** No longer affects: systemd (Ubuntu Bionic)

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (22s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in casper package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in casper source package in Bionic:
  New
Status in gdm3 source package in Bionic:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+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 1762385] Re: dell_wmi: Unknown key codes

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1766542] Re: Installation blocks when the machine is behind a proxy server

[Steve Langasek]

> Significant blockings -
> "Retrieving file 1 of 3", 90 seconds
> "Retrieving file 1 of 1", 32 seconds

Does this mean that in 18.04, the full delay you see is 122 seconds?

Is that considered acceptable, or not?

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  New
Status in ubiquity source package in Bionic:
  New

Bug description:
  When the machine is behind a proxy server, the installation will block
  for a while (several minutes) to retrieve the package lists. The
  timeouts are too long and makes user feels the machine may have some
  problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Dimitri John Ledkov]

Removing systemd, as I believe there is nothing to be changed in systemd
for this fix to land.

Are the affected users fixed with the proposed kernel? Please test
proposed kernel asap! Otherwise the change will be dropped from the
kernel again on xenial =(

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Bionic)

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in laptop-mode-tools source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport 

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Andreas Hasenack]

** Description changed:

  [Impact]
  Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.
  
  The fix is applied upstream, see comment #13.
  
  [Test Case]
  * Create a fresh xenial VM or container and login. Update the apt 
repositories:
  sudo apt update
  
  * Create a local directory and cd into it:
  mkdir test && cd test
  
  * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
  wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript
  
  * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
  sudo sh ./testscript
  (...)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)
  
  * Export this var:
  export LDAPSASL_SECPROPS=none
  
- 
  * Run the actual test script a few more times to confirm the crasH:
- $ ./sasltest 
+ $ ./sasltest
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)
  
  * Install the updated packages from proposed
  
  * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
- $ echo $LDAPSASL_SECPROPS 
+ $ echo $LDAPSASL_SECPROPS
  none
  
  $ ./sasltest
  $
  
  This time the test completes without crashing.
  
+ [Regression Potential]
+ This is SASL authentication, and with kerberos nonetheless (in the case of 
the bug reporter). I suspect not many people deploy this due to its complexity. 
The ones that have such a setup, however, tend to know what they are doing, so 
if they say the problem is fixed for them, I believe it is.
  
- [Regression Potential]
- 
-  * discussion of how regressions are most likely to manifest as a result
- of this change.
- 
-  * It is assumed that any SRU candidate patch is well-tested before
-    upload and has a low overall risk of regression, but it's important
-    to make the effort to think about what ''could'' happen in the
-    event of a regression.
- 
-  * This both shows the SRU team that the risks have been considered,
-    and provides guidance to testers in regression-testing the SRU.
+ About this particular change, it's committed upstream and also in
+ debian, and @rtandy was kind enough to provide a sample test script that
+ exhibits the problem.
  
  [Other Info]
+ Since the fix is applied upstream and in Debian, there shouldn't be 
additional surprises here.
  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
  
  [Original description]
  
  I have a slapd problem on a freshly installed 16.04 machine:
  
  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]
  
  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not occuring.
  
  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1
  
  GDB debug:
  
  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $
   
buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)
  
  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to 

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/345944

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.

  The fix is applied upstream, see comment #13.

  [Test Case]
  * Create a fresh xenial VM or container and login. Update the apt 
repositories:
  sudo apt update

  * Create a local directory and cd into it:
  mkdir test && cd test

  * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
  wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript

  * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
  sudo sh ./testscript
  (...)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Export this var:
  export LDAPSASL_SECPROPS=none

  * Run the actual test script a few more times to confirm the crasH:
  $ ./sasltest
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Install the updated packages from proposed

  * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
  $ echo $LDAPSASL_SECPROPS
  none

  $ ./sasltest
  $

  This time the test completes without crashing.

  [Regression Potential]
  This is SASL authentication, and with kerberos nonetheless (in the case of 
the bug reporter). I suspect not many people deploy this due to its complexity. 
The ones that have such a setup, however, tend to know what they are doing, so 
if they say the problem is fixed for them, I believe it is.

  About this particular change, it's committed upstream and also in
  debian, and @rtandy was kind enough to provide a sample test script
  that exhibits the problem.

  [Other Info]
  Since the fix is applied upstream and in Debian, there shouldn't be 
additional surprises here.

  
  [Original description]

  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not occuring.

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $
   
buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

[Andreas Hasenack]

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

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.

  The fix is applied upstream, see comment #13.

  [Test Case]
  * Create a fresh xenial VM or container and login. Update the apt 
repositories:
  sudo apt update

  * Create a local directory and cd into it:
  mkdir test && cd test

  * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
  wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript

  * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
  sudo sh ./testscript
  (...)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Export this var:
  export LDAPSASL_SECPROPS=none

  * Run the actual test script a few more times to confirm the crasH:
  $ ./sasltest
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Install the updated packages from proposed

  * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
  $ echo $LDAPSASL_SECPROPS
  none

  $ ./sasltest
  $

  This time the test completes without crashing.

  [Regression Potential]
  This is SASL authentication, and with kerberos nonetheless (in the case of 
the bug reporter). I suspect not many people deploy this due to its complexity. 
The ones that have such a setup, however, tend to know what they are doing, so 
if they say the problem is fixed for them, I believe it is.

  About this particular change, it's committed upstream and also in
  debian, and @rtandy was kind enough to provide a sample test script
  that exhibits the problem.

  [Other Info]
  Since the fix is applied upstream and in Debian, there shouldn't be 
additional surprises here.

  
  [Original description]

  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not occuring.

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $
   
buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Dimitri John Ledkov]

** Also affects: klibc (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Seth Forshee (sforshee)
   Status: Fix Released

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

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

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

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

Title:
  FFe: Enable configuring resume offset via sysfs

Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  In Progress

Bug description:
  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Gunnar Hjalmarsson]

Thanks for looking, Łukasz.

Right, it didn't build in PPA for me without those. As regards
'locales', according to the build log it looked for and failed to find
/usr/share/i18n/charmaps. As regards the extra install directory in
d/rules, it's obviously needed if the conditions for running the
subsequent commands are satisfied. Can't explain why it differs from the
archive uploads. I just run "debuild -S" and dput'ed (not from a clean
chroot, though).

I think that $1 is always "configure" at the execution of postinst.
Please note that the original code checks for precisely that. I
struggled a bit to find a way to check whether we are upgrading, and the
proposed way proved to work when I tested. But I'm not a Debian
packaging wizard, and would be just as happy if there is a simpler way
to check for it.

Actually, the fact that keyboard-configuration and g-c-c both write to
/etc/default/keyboard, while they have different ideas of what it should
contain, appears to be a bit odd. My proposal only addresses the most
obvious issue as reported in this bug, i.e. it prevents the keyboard
configuration from being changed without the user having asked for it.

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Oliver Grawert]

well, my subtle hint would point to simply add it to /etc/environment
here, which would globally cover for everything, would allow us to drop
the profile.d snippet in ubuntu images/installs and to my knowledge
would even be used by systemd (or am i wrong here ?) ...

(and i think it would even work for zsh)

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1768232] Re: Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (Resolution 1024x768 after nomodeset, i915 driver issue)

[Shane Semanek]

I have a Dell Optiplex 330 workstation with Intel 82G33/G31 Express
graphics. It ran Ubuntu 16.04, Ubuntu 17.10, and Ubuntu 18.04 beta2
without any issues. When Ubuntu 18.04 was released I did a clean install
and it would boot to the Ubuntu logo screen and stop. I tried several
kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline but the issue
was not resolved.

To resolve the issue I had to disable Wayland in GDM3.

sudo vi /etc/gdm3/custom.conf

Change #WaylandEnable=false to WaylandEnable=false and reboot

Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable-
xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux

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

Title:
  Stuck at ubuntu logo while booting after installing Ubuntu 18.04
  (Resolution 1024x768 after nomodeset, i915 driver issue)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My system stuck at ubuntu logo while booting. To resolve it, I've set
  nomodeset.

  But now it occurs a resolution issue to 1024x768. Here are the
  necessary information:

  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  and

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.

  Intel Graphics Update Tool shows:

  Checking if Intel graphics card available...
    • checking for i915 module in /sys/module
    • i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
    • fetching https://download.01.org/gfx/ilg-config.cfg
    • saving to /home/test/.ilg-config
    • fetched 1626 bytes
    • fetched 9818 bytes
    • fetched 12301 bytes
    • looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 

[Touch-packages] [Bug 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID

[Andreas Hasenack]

It does. If I ask it directly, it responds just fine to my dig query. It
also responds correctly to systemd (did you see the packet capture?).

Why should /etc/hosts have a bip entry? That's a hack when your dns
server doesn't know about you.

The instance was an upgrade, can't remember now if it was artful or
xenial. I can check if that matters.

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

Title:
  Server feature level is now lower than when we began our transaction.
  Restarting with new ID

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd 237-3ubuntu10 from bionic

  There is no /etc/netplan/* file.

  I'm getting some sort of a loop when systemd-resolved tries to resolve
  the hostname of my canonistack instance:

  ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack
  bip.lcy02.canonistack: resolve call failed: All attempts to contact name 
servers or networks failed

  systemd-resolved debug output loops over like this:
  Transaction 36341 is now 19121.
  Cache miss for bip.lcy02.canonistack IN A
  Transaction 19121 for  scope dns on */*.
  Using feature level UDP+EDNS0 for transaction 19121.
  Sending query packet with id 19121.
  Processing incoming packet on transaction 19121. (rcode=SUCCESS)
  Server feature level is now lower than when we began our transaction. 
Restarting with new ID.
  Transaction 19121 is now 17157.
  Cache miss for bip.lcy02.canonistack IN A
  Transaction 17157 for  scope dns on */*.
  Using feature level UDP+EDNS0 for transaction 17157.
  Sending query packet with id 17157.
  Processing incoming packet on transaction 17157. (rcode=SUCCESS)
  Server feature level is now lower than when we began our transaction. 
Restarting with new ID.
  ...

  Packet capture shows a loop like this:
  13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? 
bip.lcy02.canonistack. (50)
  13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 
10.55.32.54 (55)
  13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? 
bip.lcy02.canonistack. (50)
  13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 
10.55.32.54 (55)

  I'm going to attach the full debug output, and the pcap file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Łukasz Zemczak]

Thanks for your patch Gunnar! For now I only had a quick look the
changes, was wondering why the debian/control and debian/rules changes
were needed for the PPA upload. It didn't build without those? I would
expect it to not really differ from what would happen in the archive.

Also, from the glimpse I had I saw you were doing `dpkg --compare-
versions "$2" lt-nl "$PKGVERSION"` in the postinst - was is the reason
for that? I might be missing context, but isn't it enough to just check
for "$1" = "upgrade" to see if we're upgrading?

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Dimitri John Ledkov]

re:single code path

we do have a lot of duplication. I think profile.d is actually good
enough for all the logged in users. However, for now, the
/usr/lib/systemd/system-environment-generators is a special place to
integrate and ensure that environment that systemd creates for units has
everything setup correctly.

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Dimitri John Ledkov]

/etc/profile.d is for the login shells.

the bug is about the environment of systemd units as started by systemd.
That environment is not created / does not parse /etc/profile.d

this new integration is to fix the environment as seen by binaries
spawned by systemd (e.g. cloud-init). Specifically see my example $
systemd-run /usr/bin/env

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Dimitri John Ledkov]

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

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: Confirmed

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

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Confirmed

Bug description:
  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+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 1770557] Re: systemd-resolved should be restarted only on actual DHCP/DNS updates

[Dimitri John Ledkov]

Very nice! I'm sorry you hit this problem, and your analysis and
solution look good. I will work on integrating it.

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

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

Title:
  systemd-resolved should be restarted only on actual DHCP/DNS updates

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  My ISP gives me a DHCP IP with lease time about 2 minutes
  in the script /etc/dhcp/dhclient-enter-hooks.d/resolved , a function 
make_resolv_conf is defined which creates config fragments in resolved.conf.d/ 
, then unconditionally restarts systemd-resolved service
  so, about every 2 minutes, this service is restarted on my system, despite 
the fact that DNS configuration is not changed.
  I would propose an update to the script, which first creates config fragments 
in temporary files, and then it restarts the service only when config is 
changed (or created/removed).
  now going to attach my patch below

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770557/+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 1763575] Re: link_config: autonegotiation is unset or enabled

[Dimitri John Ledkov]

The pull request mentioned was merged as
https://github.com/systemd/systemd/commit/94d4acbe4b496c0f0c4e5e2143426751c8c5f9a9
and is part of v237, and thus was part of systemd 237-3ubuntu8, which is
the systemd version that was installed on the machine the bug report was
reported from.

Irrespective of the found unix stackexchange questions / upstream pull
requests. Can you please describe what is the bug that you are
experiencing? and on which hardware?

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

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

Title:
  link_config: autonegotiation is unset or enabled

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Get that message logged:

  systemd-udevd[401]: link_config: autonegotiation is unset or enabled,
  the speed and duplex are not writable.

  and system settings showing 'wired unmanaged'; that makes network
  speed slowing by 50 %

  Please check that fix has been really merged:

  
https://unix.stackexchange.com/questions/413187/is-systemd-links-handling-of-auto-negotiation-broken
  https://github.com/systemd/systemd/pull/7808/files

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 13 07:11:23 2018
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.30
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.30:bd01/23/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.systemd.journald.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2018-01-03T11:19:10.780935

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1763575/+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 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)

[Dimitri John Ledkov]

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

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

** Description changed:

+ Cherrypick
+ 
https://github.com/systemd/systemd/commit/3776f9cf00b163eedeb0325691d23df11385cbc5
+ 
  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this CPUID
  information when detecting Xen, and thus it erroneously assumes that the
  guest is running under Hyper-V. This causes Xen-related services (and
  anything else that relies on systemd's VM-detection functionality) to
  fail.
  
  I *believe* this is a regression from systemd 229 as used in Xenial — we
  have at least a few Xen-based VMs that report as Hyper-V via CPUID and
  don't have this issue on that version — but i haven't confirmed that for
  certain.
  
  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:
  
  https://github.com/systemd/systemd/issues/8844
  
  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.
  
  Thanks!
  
  See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573
  
  ---
  
  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  
  % apt-cache policy systemd
  systemd:
-   Installed: 237-3ubuntu10
-   Candidate: 237-3ubuntu10
-   Version table:
-  *** 237-3ubuntu10 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 237-3ubuntu10
+   Candidate: 237-3ubuntu10
+   Version table:
+  *** 237-3ubuntu10 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  systemd sometimes misdetects Xen VMs (fixed up-stream)

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  Cherrypick
  
https://github.com/systemd/systemd/commit/3776f9cf00b163eedeb0325691d23df11385cbc5

  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this
  CPUID information when detecting Xen, and thus it erroneously assumes
  that the guest is running under Hyper-V. This causes Xen-related
  services (and anything else that relies on systemd's VM-detection
  functionality) to fail.

  I *believe* this is a regression from systemd 229 as used in Xenial —
  we have at least a few Xen-based VMs that report as Hyper-V via CPUID
  and don't have this issue on that version — but i haven't confirmed
  that for certain.

  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:

  https://github.com/systemd/systemd/issues/8844

  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.

  Thanks!

  See also:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573

  ---

  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  % apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10
    Candidate: 237-3ubuntu10
    Version table:
   *** 237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768104/+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 1772057] [NEW] Upgrade to ubuntu18.04 failed

[rjwinslow]

Public bug reported:

Could not install '/tmp/apt-dpkg-install-Wboy1K/148-firefox-locale-
en_60.0.1+build2-0ubuntu0.18.04.1_amd64.deb'

The upgrade will continue but the '/tmp/apt-dpkg-install-Wboy1K/148
-firefox-locale-en_60.0.1+build2-0ubuntu0.18.04.1_amd64.deb' package may
not be in a working state. Please consider submitting a bug report about
it.

cannot copy extracted data for './usr/share/doc/firefox-locale-
en/copyright' to '/usr/share/doc/firefox-locale-en/copyright.dpkg-new':
unexpected end of file or stream


upgrading from 17.10

rjw@rjw-MS-7721:~$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.1
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 18 11:32:07 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-09-17 (243 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: apt
UpgradeStatus: Upgraded to bionic on 2018-05-18 (0 days ago)

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


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

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

Title:
  Upgrade to ubuntu18.04 failed

Status in apt package in Ubuntu:
  New

Bug description:
  Could not install '/tmp/apt-dpkg-install-Wboy1K/148-firefox-locale-
  en_60.0.1+build2-0ubuntu0.18.04.1_amd64.deb'

  The upgrade will continue but the '/tmp/apt-dpkg-install-Wboy1K/148
  -firefox-locale-en_60.0.1+build2-0ubuntu0.18.04.1_amd64.deb' package
  may not be in a working state. Please consider submitting a bug report
  about it.

  cannot copy extracted data for './usr/share/doc/firefox-locale-
  en/copyright' to '/usr/share/doc/firefox-locale-en/copyright.dpkg-
  new': unexpected end of file or stream

  
  upgrading from 17.10

  rjw@rjw-MS-7721:~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 18 11:32:07 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-17 (243 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1772057/+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 1771353] Re: Server feature level is now lower than when we began our transaction. Restarting with new ID

[Dimitri John Ledkov]

Does the upstream DNS server actually know about bip.lcy02.canonistack?

If it doesn't, what sort of a response are you expecting?

Why /etc/hosts does not have bip & bip.lcy02.canonistack set?

Is this a fresh instance, or an upgrade?

in bionic, cloud-init should have configured your instance using
netplan, not eni.

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

Title:
  Server feature level is now lower than when we began our transaction.
  Restarting with new ID

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd 237-3ubuntu10 from bionic

  There is no /etc/netplan/* file.

  I'm getting some sort of a loop when systemd-resolved tries to resolve
  the hostname of my canonistack instance:

  ubuntu@bip:~$ systemd-resolve bip.lcy02.canonistack
  bip.lcy02.canonistack: resolve call failed: All attempts to contact name 
servers or networks failed

  systemd-resolved debug output loops over like this:
  Transaction 36341 is now 19121.
  Cache miss for bip.lcy02.canonistack IN A
  Transaction 19121 for  scope dns on */*.
  Using feature level UDP+EDNS0 for transaction 19121.
  Sending query packet with id 19121.
  Processing incoming packet on transaction 19121. (rcode=SUCCESS)
  Server feature level is now lower than when we began our transaction. 
Restarting with new ID.
  Transaction 19121 is now 17157.
  Cache miss for bip.lcy02.canonistack IN A
  Transaction 17157 for  scope dns on */*.
  Using feature level UDP+EDNS0 for transaction 17157.
  Sending query packet with id 17157.
  Processing incoming packet on transaction 17157. (rcode=SUCCESS)
  Server feature level is now lower than when we began our transaction. 
Restarting with new ID.
  ...

  Packet capture shows a loop like this:
  13:38:32.293524 IP 10.55.32.54.53786 > 10.55.32.1.53: 46096+ [1au] A? 
bip.lcy02.canonistack. (50)
  13:38:32.293753 IP 10.55.32.1.53 > 10.55.32.54.53786: 46096* 1/0/0 A 
10.55.32.54 (55)
  13:38:32.294026 IP 10.55.32.54.53786 > 10.55.32.1.53: 64494+ [1au] A? 
bip.lcy02.canonistack. (50)
  13:38:32.294249 IP 10.55.32.1.53 > 10.55.32.54.53786: 64494* 1/0/0 A 
10.55.32.54 (55)

  I'm going to attach the full debug output, and the pcap file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771353/+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 9999] Re: cfdisk crashes if terminal size is too small

[Ubuntu QA Website]

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

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

** Tags added: package-qa-testing

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

Title:
  cfdisk crashes if terminal size is too small

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  I've tried to run cfdisk in a narrow (less than 40 columns) gnome-terminal 
window,
  and cfdisk crashed.

  If the user doesn't have rights to read the device, the crash doesn't occur, 
because
  the program merely displays an error message. It can be reproduced only when
  actually
  seeing the partition layout of a device.

  The problem is caused by some (unsafe) usage of sprintf. The patch I'm going 
to
  attach
  changes most unsafe sprintf calls to snprintf, and it looks like the bug is 
solved.

  The considered util-linux version is 2.12h-3ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug//+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Oliver Grawert]

i meant to say above is that it would be nice to find a way that covers
all use-cases with one code path (sorry, just noticed what i wrote wasnt
clear in that regard)

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1772051] [NEW] piuparts report problems about systemd

[Balint Reczey]

Public bug reported:

Running piuparts fails on systemd package:
 dget http://launchpadlibrarian.net/366689472/systemd_237-3ubuntu10_amd64.deb
 sudo piuparts -d bionic systemd_237-3ubuntu10_amd64.deb

...
4m28.6s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', 
'--purge', 'systemd']
4m28.6s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'dpkg', '--purge', '--pending']
4m28.7s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', 
'--purge', '--pending']
4m28.7s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'dpkg', '--remove', '--pending']
4m28.7s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', 
'--remove', '--pending']
4m28.7s DEBUG: Starting command: ['lsof', '-w', '+D', '/tmp/tmpf5kGNh']
4m29.1s DEBUG: Command failed (status=1), but ignoring error: ['lsof', '-w', 
'+D', '/tmp/tmpf5kGNh']
4m29.4s ERROR: WARN: Broken symlinks:
  /etc/localtime -> /usr/share/zoneinfo/Etc/UTC
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service -> 
/lib/systemd/system/systemd-resolved.service
  /etc/systemd/system/multi-user.target.wants/systemd-resolved.service -> 
/lib/systemd/system/systemd-resolved.service
  /etc/systemd/system/multi-user.target.wants/ondemand.service -> 
/lib/systemd/system/ondemand.service
4m29.4s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'dpkg-divert', '--list']
4m29.4s DUMP: 
  diversion of /usr/share/man/man1/sh.1.gz to 
/usr/share/man/man1/sh.distrib.1.gz by dash
  diversion of /bin/sh to /bin/sh.distrib by dash
4m29.4s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'dpkg-divert', '--list']
4m29.4s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'apt-get', 'clean']
4m29.4s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'apt-get', 
'clean']
4m30.7s DEBUG: Modified(uid, gid, mode, size, target): /etc/resolv.conf (0, 0, 
- 100644, 38, None) != (0, 0, l 120777, 39, 
../run/systemd/resolve/stub-resolv.conf)
4m30.7s DEBUG: Modified(uid, gid, mode, size, target): /var/log/tallylog (0, 0, 
- 100600, 6464, None) != (0, 0, - 100600, 6592, None)
4m30.8s ERROR: FAIL: Package purging left files on system:
  /etc/systemd/system/dbus-org.freedesktop.resolve1.service -> 
/lib/systemd/system/systemd-resolved.service  not owned
  /etc/systemd/system/multi-user.target.wants/   not owned
  /etc/systemd/system/multi-user.target.wants/ondemand.service -> 
/lib/systemd/system/ondemand.service   not owned
  /etc/systemd/system/multi-user.target.wants/systemd-resolved.service -> 
/lib/systemd/system/systemd-resolved.service   not owned
  /var/log/apt/eipp.log.xz   not owned
  /var/log/journal/  not owned

4m30.8s ERROR: FAIL: After purging files have been modified:
  /etc/resolv.conf   not owned
  /var/log/tallylog  not owned

4m30.8s ERROR: FAIL: Installation and purging test.
4m31.2s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'umount', '/proc']
4m31.2s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'umount', 
'/proc']
4m31.2s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'umount', '/dev/pts']
4m31.2s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'umount', 
'/dev/pts']
4m31.2s DEBUG: Starting command: ['rm', '-rf', '--one-file-system', 
'/tmp/tmpf5kGNh']
4m31.4s DEBUG: Command ok: ['rm', '-rf', '--one-file-system', '/tmp/tmpf5kGNh']
4m31.4s DEBUG: Removed directory tree at /tmp/tmpf5kGNh
4m31.4s ERROR: piuparts run ends.


I already proposed a fix for /var/log/journal/ at 
https://salsa.debian.org/debian/piuparts/merge_requests/1 , but most of the 
rest should be fixed in systemd.

piuparts run on Debian's systemd_238-4_amd64.deb in sid passes.

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

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

Title:
  piuparts report problems about systemd

Status in systemd package in Ubuntu:
  New

Bug description:
  Running piuparts fails on systemd package:
   dget http://launchpadlibrarian.net/366689472/systemd_237-3ubuntu10_amd64.deb
   sudo piuparts -d bionic systemd_237-3ubuntu10_amd64.deb

  ...
  4m28.6s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', 
'--purge', 'systemd']
  4m28.6s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'dpkg', '--purge', '--pending']
  4m28.7s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', 
'--purge', '--pending']
  4m28.7s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 
'dpkg', '--remove', '--pending']
  4m28.7s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', 
'--remove', '--pending']
  4m28.7s DEBUG: Starting command: ['lsof', '-w', '+D', '/tmp/tmpf5kGNh']
  4m29.1s DEBUG: Command failed (status=1), but ignoring 

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

[Oliver Grawert]

snapd ships a snippet in /etc/profile.d that sets the PATH to /snap/bin
and should theoretically work for all login shells (except for zsh which
doesn't respect the profile.d standard) ... bug 1640514 and bug 1659719
are related.

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

  [Testcase]

  $ systemd-run /usr/bin/env
  $ journalctl -e | grep PATH

  Output should contain /snap/bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1772041] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 25

[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 ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1772041

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 25

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upugrading from Xubuntu 17.10 to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 18 09:09:13 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 25
  InstallationDate: Installed on 2016-03-04 (804 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 25
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1772041/+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 1772041] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 25

[Jeff]

Public bug reported:

Upugrading from Xubuntu 17.10 to 18.04.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 18 09:09:13 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 25
InstallationDate: Installed on 2016-03-04 (804 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 25
UpgradeStatus: Upgraded to bionic on 2018-05-18 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 25

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Upugrading from Xubuntu 17.10 to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 18 09:09:13 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 25
  InstallationDate: Installed on 2016-03-04 (804 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 25
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1772041/+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 1771858] Re: /snap/bin not in default PATH for units

[Dimitri John Ledkov]

** Description changed:

  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.
  
  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).
+ 
+ Since v232 systemd provides support for environment generators, snapd
+ should package/ship a snippet that injects the correct snapd path into
+ systemd environment.
+ 
+ E.g.:
+ 
+ $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
+ $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
+ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
+ 
+ Something similar can be done for user-environment-generators too. Note
+ that user-environment-generators can generate unique variables per user.
+ 
+ Note please use /usr/lib path, as it appears that /lib/systemd path is
+ not working atm. Will check if that needs to be fixed up.

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

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

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

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

** Description changed:

  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.
  
  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).
  
  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.
  
  E.g.:
  
  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
  
  Something similar can be done for user-environment-generators too. Note
  that user-environment-generators can generate unique variables per user.
  
  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.
+ 
+ systemd in xenial does not support system-environment-generators, thus
+ we probably need to upload a patch to change the DEFAULT_PATH compiled
+ in default there.

** Summary changed:

- /snap/bin not in default PATH for units
+ /snap/bin not in default PATH for units, snapd should ship 
system-environment-generators to inject /snap/bin into $PATH

** Description changed:

  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.
  
  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).
  
  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.
  
  E.g.:
  
  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
  
  Something similar can be done for user-environment-generators too. Note
  that user-environment-generators can generate unique variables per user.
  
  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.
  
  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.
+ 
+ [Testcase]
+ 
+ $ systemd-run /usr/bin/env
+ $ journalctl -e | grep PATH
+ 
+ Output should contain /snap/bin

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts 

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units

[Dimitri John Ledkov]

** Description changed:

  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.
+ 
+ Specifically, this is evident by e.g. $ systemd-run env. Or any other
+ daemons that spawn shell scripts (e.g. cloud-init metadata acquired
+ shell hooks, etc.).

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

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

Status in snapd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in snapd source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed
Status in snapd source package in Bionic:
  New
Status in systemd source package in Bionic:
  Won't Fix
Status in snapd source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).

  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.

  E.g.:

  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd

  Something similar can be done for user-environment-generators too.
  Note that user-environment-generators can generate unique variables
  per user.

  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.

  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1772025] Re: package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no package named 'libssl1.1' is installed, cannot configure

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

Title:
  package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no
  package named 'libssl1.1' is installed, cannot configure

Status in openssl package in Ubuntu:
  New

Bug description:
  When upgrading from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1 1.1.0g-2ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 18 14:22:48 2018
  DuplicateSignature:
   package:libssl1.1:1.1.0g-2ubuntu4
   Unpacking python3-minimal (3.6.5-3) over (3.6.3-0ubuntu2) ...
   dpkg: error processing package libssl1.1 (--configure):
no package named 'libssl1.1' is installed, cannot configure
  ErrorMessage: no package named 'libssl1.1' is installed, cannot configure
  InstallationDate: Installed on 2017-04-07 (405 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: openssl
  Title: package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no 
package named 'libssl1.1' is installed, cannot configure
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1772025/+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 1772025] [NEW] package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no package named 'libssl1.1' is installed, cannot configure

[Yunior Luis]

Public bug reported:

When upgrading from 17.10 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libssl1.1 1.1.0g-2ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 18 14:22:48 2018
DuplicateSignature:
 package:libssl1.1:1.1.0g-2ubuntu4
 Unpacking python3-minimal (3.6.5-3) over (3.6.3-0ubuntu2) ...
 dpkg: error processing package libssl1.1 (--configure):
  no package named 'libssl1.1' is installed, cannot configure
ErrorMessage: no package named 'libssl1.1' is installed, cannot configure
InstallationDate: Installed on 2017-04-07 (405 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: openssl
Title: package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no package 
named 'libssl1.1' is installed, cannot configure
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no
  package named 'libssl1.1' is installed, cannot configure

Status in openssl package in Ubuntu:
  New

Bug description:
  When upgrading from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1 1.1.0g-2ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 18 14:22:48 2018
  DuplicateSignature:
   package:libssl1.1:1.1.0g-2ubuntu4
   Unpacking python3-minimal (3.6.5-3) over (3.6.3-0ubuntu2) ...
   dpkg: error processing package libssl1.1 (--configure):
no package named 'libssl1.1' is installed, cannot configure
  ErrorMessage: no package named 'libssl1.1' is installed, cannot configure
  InstallationDate: Installed on 2017-04-07 (405 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: openssl
  Title: package libssl1.1 1.1.0g-2ubuntu4 failed to install/upgrade: no 
package named 'libssl1.1' is installed, cannot configure
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1772025/+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 1715319] Re: [IPV6] DHCP client gets 128 subnet mask instead of any other that defined

[Launchpad Bug Tracker]

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  [IPV6] DHCP client gets 128 subnet mask instead of any other that
  defined

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  After configuring DHCP server (with and without RADVD), the client
  gets ipv6 address in range that was defined, or preserved. But the
  subnetmask of the address is 128 no matter what was the definition.

  Steps to reproduce

  1.Install packages:
  #apt-get install -y *dhcp*
  #apt-get install radvd

  2.Define DHCP and RADVD files:

  #vim /etc/dhcp/dhcpd6.conf
  authoritative;
  default-lease-time 600;
  max-lease-time 7200;
  log-facility local7;
  subnet6 ::/64 {
  option dhcp6.name-servers ::;
  range6 ::1 ::100;
  }

  #vim /etc/radvd.conf
  interface enp5s0f0
  {
  AdvSendAdvert on;
  MinRtrAdvInterval 3;
  MaxRtrAdvInterval 10;
  prefix ::/64 {
  AdvOnLink on;
  AdvAutonomous on;
  AdvRouterAddr on;
  };
  };

  
  3.
  # sysctl net.ipv6.conf.ens3.forwarding
  net.ipv6.conf.ens3.forwarding = 1

  4.Create empty server data base file and bring up DHCP server:
  #echo "" >  /tmp/dhcp6.lease
  # dhcpd -6 -cf /etc/dhcp/dhcpd6.conf -lf /tmp/dhcpd6.leases enp5s0f0

  5.Define client interface in /etc/network/interfaces file:
  #vim  /etc/network/interfaces
  auto enp6s0f0
  iface enp6s0f0 inet6 dhcp

  6.Start client and check the ip:
  #ifdown 
  #ifup
  #ifconfig enp6s0f0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1715319/+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 1772023] [NEW] Mobile broadband has IPv6 disabled by default

[Erno Kuusela]

Public bug reported:

To fix this, I had to go to "Mobile broadband settings", click the
gearwheel icon, spot the "IPv6 settings" tab and change Method from
Ignore to Automatic.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: modemmanager 1.6.8-2ubuntu1
Uname: Linux 4.16.7-041607-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 18 16:34:25 2018
InstallationDate: Installed on 2018-04-25 (22 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
SourcePackage: modemmanager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Mobile broadband has IPv6 disabled by default

Status in modemmanager package in Ubuntu:
  New

Bug description:
  To fix this, I had to go to "Mobile broadband settings", click the
  gearwheel icon, spot the "IPv6 settings" tab and change Method from
  Ignore to Automatic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: modemmanager 1.6.8-2ubuntu1
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 18 16:34:25 2018
  InstallationDate: Installed on 2018-04-25 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1772023/+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 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

[Dimitri John Ledkov]

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

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

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771791/+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 1771858] Re: /snap/bin not in default PATH for units

[Dimitri John Ledkov]

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

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

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

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

Title:
  /snap/bin not in default PATH for units

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  New

Bug description:
  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771858/+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 1642514] Re: sched: Match-all classifier is missing in xenial

[Michel Galle]

my previous comment is a mail mistake. sorry.

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1772014] Re: netcat-openbsd does not allow setting source port

[Aki Rossi]

Oh, and this is Ubuntu 18.04, and package version 1.187-1.

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

Title:
  netcat-openbsd does not allow setting source port

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  When connecting to a remote host, both the command-line help and man-
  page state that specifying `-p` will set the local port number.
  However, when I actually attempt to do it, only the usage text is
  printed:

  $ nc.openbsd -p 12345 localhost 12345
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  This appears to be caused by an erroneous check on line 541 of
  netcat.c, introduced by `misc-failures-and-features.patch`. If I
  remove the check or undo the patch completely, the source port is set
  correctly, but remains bound after I close the connection. Meanwhile,
  netcat-traditional works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1772014/+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 1767201] Re: KVPM pam_unix(sudo:auth): auth could not identify password for user

[Marc Deslauriers]

** Information type changed from Public Security to Public

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

Title:
  KVPM pam_unix(sudo:auth): auth could not identify password for user

Status in kvpm package in Ubuntu:
  New
Status in sudo package in Ubuntu:
  Invalid

Bug description:
  Can't launch KVPM in Kubuntu 18.04 beta
  App is installed and gives password screen then fails

  Linux MadMax 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvpm/+bug/1767201/+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 1763102] Re: Multiple memory corruptions in objdump (binuitils-2.30-15ubuntu1)

[Marc Deslauriers]

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

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

Title:
  Multiple memory corruptions in objdump (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  Dear all,
  The following binutils objdump memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./objdump --dwarf-check 
-C -g -f -dwarf -x $file
  ```

  
  We can verify those issues for objdump binuitils-2.30-15ubuntu1 (Ubuntu 
16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763102/+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 1763101] Re: OOM-Bug in cxxfilt (binuitils-2.30-15ubuntu1)

[Marc Deslauriers]

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

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

Title:
  OOM-Bug in cxxfilt (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  Dear all,
  The following binutils cxxfilt OOM bug was found by a modified version of the 
kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the input and 
an ASAN report.

  Steps to reproduce:

  Build current verison of binutils:

  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./cxxfilt -t < oom
  ```

  We can verify this issue for cxxfilt binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils") on an Intel(R)
  Core(TM) i7-6700 CPU @ 3.40GHz server machine with 32GB RAM.

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763101/+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 1763099] Re: Stack-Overflow in nm-new (binuitils-2.30-15ubuntu1)

[Marc Deslauriers]

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

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

Title:
  Stack-Overflow in nm-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  Dear all,
  The following binutils nm-new Stack-Overflow was found by a modified version 
of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the 
crashing input and an ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=true:allow_addr2line=true ./nm-new a -C -l 
--synthetic $file
  ```

  
  We can verify this issue for nm-new binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 
LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763099/+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 1760355] Re: Segmentation fault while converting an empty svg

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

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

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

Title:
  Segmentation fault while converting an empty svg

Status in librsvg package in Ubuntu:
  Confirmed

Bug description:
  gdb -q --args rsvg crashed2.svg test.png
  Reading symbols from rsvg...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /usr/bin/rsvg crashed2.svg test.png
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  (rsvg:14399): librsvg-CRITICAL **: rsvg_handle_set_size_callback:
  assertion 'handle != NULL' failed

  Program received signal SIGSEGV, Segmentation fault.
  0x77bc55b0 in rsvg_handle_get_dimensions () from 
/usr/lib/x86_64-linux-gnu/librsvg-2.so.2
  (gdb) backtrace
  #0  0x77bc55b0 in rsvg_handle_get_dimensions () at 
/usr/lib/x86_64-linux-gnu/librsvg-2.so.2
  #1  0x004025d3 in  ()
  #2  0x766d0830 in __libc_start_main (main=
  0x401960, argc=3, argv=0x7fffe568, init=, 
fini=, rtld_fini=, stack_end=0x7fffe558) at 
../csu/libc-start.c:291
  #3  0x00402989 in  ()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1760355/+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 1762418] Re: Multiple heap-buffer-overflow in tiff-4.0.9

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

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

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

Title:
  Multiple heap-buffer-overflow in tiff-4.0.9

Status in tiff package in Ubuntu:
  Confirmed

Bug description:
  Dear all, 
  The following tiff2ps memory issues were found by a modified version of the 
kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing 
inputs, each ASAN report and each ASAN report in "halt_on_error=false" mode to 
this bug report. To reproduce those memory issues, execute an ASAN build of 
tiff2ps with the crashing inputs as the first argument (./tiff2ps 
). 

  We can verify those issues for 4.0.9-4ubuntu1 (Ubuntu 16.04.4 LTS /
  sources from "pull-lp-source tiff").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1762418/+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 1758555] Re: Segmentation fault at rsvg-convert:2414

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

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

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

Title:
  Segmentation fault at rsvg-convert:2414

Status in librsvg package in Ubuntu:
  Confirmed

Bug description:
  librsvg throws a segmentation fault when an tried to convert an empty
  svg using rsvg-convert.

  Details:
  $ echo > empty.svg
  $cat empty.svg

  $rsvg-convert empty.svg

  (rsvg-convert:4850): librsvg-CRITICAL **: rsvg_handle_set_size_callback: 
assertion 'handle != NULL' failed
  Segmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1758555/+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 1763094] Re: Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

[Marc Deslauriers]

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

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

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

Title:
  Multiple memory corruption in ld-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Confirmed
Status in binutils source package in Bionic:
  Confirmed

Bug description:
  Dear all,
  The following binutils ld-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./ld-new $file
  ```

  We can verify those issues for ld-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763094/+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 1763096] Re: Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

[Marc Deslauriers]

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

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

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

Title:
  Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Confirmed
Status in binutils source package in Bionic:
  Confirmed

Bug description:
  Dear all,
  The following binutils as-new memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./as-new $file
  ```

  We can verify those issues for as-new binuitils-2.30-15ubuntu1 (Ubuntu
  16.04.4 LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763096/+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 1763098] Re: Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1)

[Marc Deslauriers]

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

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

Title:
  Multiple memory corruption in gprof (binuitils-2.30-15ubuntu1)

Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  Dear all,
  The following binutils gprof memory corruptions were found by a modified 
version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have 
attached the crashing inputs and each ASAN report.

  Steps to reproduce:

  Build current verison of binutils:
  ```
  pull-lp-source binutils
  cd binutils-2.30
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" 
LDFLAGS="-fsanitize=address" ./configure
  CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address 
-ggdb" CXXFLAGS="-fsanitize=address
  -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make
  ```

  Run inputs under ASAN:

  ```
  ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./gprof $file
  ```

  
  We can verify those issues for gprof binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 
LTS / sources from "pull-lp-source bintuils").

  Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr-
  Universität Bochum)

  Best regards,
  Sergej Schumilo

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

[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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1769753

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  the upgrade to 16.04 from 14.04 failed and when i try to run in safe /
  upstart mode get error trying to dpkg configure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-122-generic 4.4.0-122.146
  ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rashmi 3240 F pulseaudio
   /dev/snd/controlC0:  rashmi 3240 F pulseaudio
  Date: Tue May  8 02:07:22 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=f960b016-fcba-4be0-a6e0-dff0bc45898a
  InstallationDate: Installed on 2015-12-08 (881 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-101-generic 
root=UUID=bb3e505f-a292-46d5-a41f-7c30458b4184 ro quiet splash radeon.modeset=0 
nouveau.modeset=0 init=/sbin/upstart
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  StagingDrivers: rts5139
  Title: package linux-image-4.4.0-122-generic 4.4.0-122.146 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0GGKVJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/25/2015:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0GGKVJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  the upgrade to 16.04 from 14.04 failed and when i try to run in safe /
  upstart mode get error trying to dpkg configure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-122-generic 4.4.0-122.146
  ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rashmi 3240 F pulseaudio
   /dev/snd/controlC0:  rashmi 3240 F pulseaudio
  Date: Tue May  8 02:07:22 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=f960b016-fcba-4be0-a6e0-dff0bc45898a
  InstallationDate: Installed on 2015-12-08 (881 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-101-generic 
root=UUID=bb3e505f-a292-46d5-a41f-7c30458b4184 ro quiet splash radeon.modeset=0 
nouveau.modeset=0 init=/sbin/upstart
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  StagingDrivers: rts5139
  Title: package linux-image-4.4.0-122-generic 4.4.0-122.146 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0GGKVJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/25/2015:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0GGKVJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769753/+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 1772014] [NEW] netcat-openbsd does not allow setting source port

[Aki Rossi]

Public bug reported:

When connecting to a remote host, both the command-line help and man-
page state that specifying `-p` will set the local port number. However,
when I actually attempt to do it, only the usage text is printed:

$ nc.openbsd -p 12345 localhost 12345
usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
   [-m minttl] [-O length] [-P proxy_username] [-p source_port]
   [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w timeout]
   [-X proxy_protocol] [-x proxy_address[:port]]  [destination] [port]

This appears to be caused by an erroneous check on line 541 of netcat.c,
introduced by `misc-failures-and-features.patch`. If I remove the check
or undo the patch completely, the source port is set correctly, but
remains bound after I close the connection. Meanwhile, netcat-
traditional works as expected.

** Affects: netcat-openbsd (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When connecting to a remote host, both the command-line help and man-
  page state that specifying `-p` will set the local port number. However,
  when I actually attempt to do it, only the usage text is printed:
  
- $ nc.openbsd -p 12345 localhost 12345
- usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
- [-m minttl] [-O length] [-P proxy_username] [-p source_port]
- [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
- [-X proxy_protocol] [-x proxy_address[:port]]   [destination] 
[port]
+ $ nc.openbsd -p 12345 localhost 12345
+ usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
+    [-m minttl] [-O length] [-P proxy_username] [-p source_port]
+    [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
+    [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]
  
  This appears to be caused by an erroneous check on line 541 of netcat.c,
  introduced by `misc-failures-and-features.patch`. If I remove the check
  or undo the patch completely, the source port is set correctly, but
  remains bound after I close the connection. Meanwhile, netcat-
  traditional works as expected.

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

Title:
  netcat-openbsd does not allow setting source port

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  When connecting to a remote host, both the command-line help and man-
  page state that specifying `-p` will set the local port number.
  However, when I actually attempt to do it, only the usage text is
  printed:

  $ nc.openbsd -p 12345 localhost 12345
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  This appears to be caused by an erroneous check on line 541 of
  netcat.c, introduced by `misc-failures-and-features.patch`. If I
  remove the check or undo the patch completely, the source port is set
  correctly, but remains bound after I close the connection. Meanwhile,
  netcat-traditional works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1772014/+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 1642514] Re: sched: Match-all classifier is missing in xenial

[Michel Galle]

Do you have a device impacted by that bug ?


On 18/05/2018 11:27, Nicolas Dichtel wrote:
> Any news for the iproute2 part?
>

-- 
Michel Galle
IT
tel: +33 6 03 05 51 47
http://www.6wind.com/

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1760910] Re: Gdebi crash in Ubuntu Studio 18.04

[Darin]

Let me know if this is a different bug and I will file another report,
but I think that it's the same.

I open a .deb with gdebi-gtk. The GUI opens. I click "Install" and gdebi
simply closes.

If I open a terminal and type gdebi-gtk path/to/deb.deb it opens the deb
in the GUI and when I hit install, it actually installs.

The method of adding gksu above doesn't work for me and most others
because gksu is deprecated and not installed in Ubuntu anymore by
default. It's a good workaround for those who can use it but it still
need fixing.

I'm using gdebi 0.9.5.7+nmu2 and Xubuntu 18.04 (upgraded from 17.10 if
that makes any difference).

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

Title:
  Gdebi crash in Ubuntu Studio 18.04

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Gdebi opens normal, but when you click install package, it closes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10
  Uname: Linux 4.15.0-13-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Apr  3 12:31:17 2018
  InstallationDate: Installed on 2018-03-29 (4 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180328)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1760910/+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 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

Thanks a lot Eric and Brian for handling the SRU process.
I just tested the packages initramfs-tools and initramfs-tools-bin version 
0.103ubuntu4.11, from trusty-proposed, following the test procedure of this 
LP's description.

Everything is working fine, so I'll mark this as verification-done.

Cheers,


Guilherme

** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

Status in initramfs-tools:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When creating the initramfs image, mkinitramfs has multiple options on
  how to include modules. The default (and most common) one is the
  "MODULES=most", which includes the majority of filesystem modules and
  all the block device drivers. One other option is "MODULES=dep", which
  tries to descend in the sysfs hierarchy and guess modules to add, with
  the goal of reduce the size of initramfs.

  For the MODULES=dep case, the initramfs-tools hook-functions script
  cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
  the sysfs lookup, so it does not build the initram disk.

  Upstream solution is composed of at least 2 patches (it's a series,
  but the 2 below are really the needed ones):

  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic

  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device

  Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
  It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.

  [Test Case]
  1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.

  (lsblk output of my test env:

  nvme0n1 259:0010G  0 disk
  └─nvme0n1p1 259:1010G  0 part
    └─md0   9:0010G  0 raid1 /
  nvme1n1 259:2010G  0 disk
  └─nvme1n1p1 259:3010G  0 part
    └─md0   9:0010G  0 raid1 /
  )

  2. Once system is booted, modify the "/etc/initramfs-
  tools/initramfs.conf", replacing "MODULES=most" to "MODULES=dep".

  3. Update your initramfs by running something like:
  "update-initramfs -u -k "

  The initramfs creating procedure will fail, unless the patch from this
  LP is present.

  [Regression Potential]
  If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).

  [Other Info]
  * This issue is based on Debian bug #785147: 
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

  * Only Trusty is affected, Xenial and late contains the full fix as
  mentioned above :

  $ git describe --contains  8ac52dc0
  v0.121_rc1~11

  $ git describe --contains 3cb744c9
  v0.121_rc1~11

  $ rmadison initramfs-tools

   initramfs-tools | 0.103ubuntu4| trusty   | source, all
   ==> initramfs-tools | 0.103ubuntu4.10 | trusty-updates   | source, all
   initramfs-tools | 0.122ubuntu8| xenial   | source, all
   initramfs-tools | 0.122ubuntu8.11 | xenial-updates   | source, all
   initramfs-tools | 0.125ubuntu12   | artful   | source, all
   initramfs-tools | 0.125ubuntu12.1 | artful-updates   | source, all
   initramfs-tools | 0.130ubuntu3| bionic   | source, all
   initramfs-tools | 0.130ubuntu6| cosmic   | source, all

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1752053] Re: nvidia-390 fails to boot graphical display

[ulyses]

The only working solution for me for the Nvidia graphic card problem in
Ubuntu 18.04, was to follow the instructions from this page:

https://medium.com/@emtudo/ubuntu-18-04-travamento-com-placa-nvidia-
3720dfe7410a

and then start the system through recovery mode.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 847496] Re: software-properties-gtk crashed with DBusException in call_blocking(): com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy: com.ubuntu.softwareproperties.applychan

[lesley lopez]

** Description changed:

  software-properties-gtk crashed with DBusException in call_blocking():
  com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy:
  com.ubuntu.softwareproperties.applychanges
  
  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: software-properties-gtk 0.81.9
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Sun Sep 11 22:20:20 2011
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110911)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-properties-gtk
  ProcEnviron:
-  SHELL=/bin/bash
-  PATH=(custom, no user)
-  LANGUAGE=pt_BR:pt:en
-  LANG=pt_BR.UTF-8
+  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANGUAGE=pt_BR:pt:en
+  LANG=pt_BR.UTF-8
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with DBusException in call_blocking(): 
com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy: 
com.ubuntu.softwareproperties.applychanges
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

Title:
  software-properties-gtk crashed with DBusException in call_blocking():
  com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy:
  com.ubuntu.softwareproperties.applychanges

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties-gtk crashed with DBusException in call_blocking():
  com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy:
  com.ubuntu.softwareproperties.applychanges

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: software-properties-gtk 0.81.9
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  Date: Sun Sep 11 22:20:20 2011
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110911)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-properties-gtk
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=pt_BR:pt:en
   LANG=pt_BR.UTF-8
  PythonArgs: ['/usr/bin/software-properties-gtk']
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with DBusException in call_blocking(): 
com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy: 
com.ubuntu.softwareproperties.applychanges
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/847496/+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 1771981] [NEW] Sync opus 1.3~beta+20180518-1 (main) from Debian sid (main)

[Oibaf]

Public bug reported:

Please sync opus 1.3~beta+20180518-1 (main) from Debian sid (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Merge with Debian; remaining changes:
- Convert to Debhelper 9 with a simpler rules file.
- Build using dh-autoreconf.
- Add a watch file.
- debian/control: close some Lintian errors.
  - Pre-depend on multiarch-support.
  - Add ${misc:Depends} to package dependencies.
- Convert to debian source format 3.0 (quilt).
- Run the tests.

This release brings a lot of quality improvemets since the very old 1.1.2
upstream release in Ubuntu.

The Debian changelog has this explanation about debian bug #810258, which had
the Ubuntu changes being dropped.

  * Use dh compat 9, not because it actually brings anything new which we need
here, but it hushes the increasingly insistent warnings about deprecated
compat levels, and is a baseline supported by all of the releases we still
need to be able to support.  I'm going to say this Closes: #810258, since
the rest of the 'modernisation' there mostly isn't helpful.  We've already
been running the tests since the very first release, we release directly
from upstream git and maintain upstream patches there, so format 3(quilt)
adds nothing but pain, and we have upstream build and install targets that
are designed to cleanly separate the -arch specific and -indep components,
so regressing to make those codependent isn't very appealing either.  It
would have also broken support for building where m-a wasn't supported,
though that's less of a problem today than it was previously.

Thanks.

Changelog entries since current cosmic version 1.1.2-1ubuntu1:

opus (1.3~beta+20180518-1) unstable; urgency=medium

  * Fix the CELT input NaN test.

 -- Ron Lee <r...@debian.org>  Fri, 18 May 2018 05:04:27 +0930

opus (1.3~beta+20180516-1) unstable; urgency=medium

  * Snapshot from 652c4559f593d3aad78bd5c85a216eeae7859429 as a preview of
patches pending for the 1.3 release.  The main motivation for doing this
now is to pull in the fix for the PLC regression introduced just before
1.2~alpha2, which Closes: #898690, and to get some broader testing on the
new hardening checks before flipping the switch to enable those by default
upstream.
  * Fix celt_pitch_xcorr() ARM jump table compiling error for a bug introduced
in 1.2-rc1.
  * Better rate allocation for stereo SILK in hybrid mode.
  * Add RNN for VAD and speech/music classification.
  * Fixing bandwidth detection for 24 kHz analysis.
  * Enable RFC 8251 changes by default.
  * Better tuning for low-bitrate music.
  * Don't set _FORTIFY_SOURCE and -fstack-protector as part of the packaging
anymore, the upstream build system will add them where they are supported
and needed now.
  * Build with --enable-hardening, which isn't related to the compile options
above, but instead includes additional opus-specific runtime sanity checks
which are cheap and certain enough to use in production builds.
  * Use dh compat 9, not because it actually brings anything new which we need
here, but it hushes the increasingly insistent warnings about deprecated
compat levels, and is a baseline supported by all of the releases we still
need to be able to support.  I'm going to say this Closes: #810258, since
the rest of the 'modernisation' there mostly isn't helpful.  We've already
been running the tests since the very first release, we release directly
from upstream git and maintain upstream patches there, so format 3(quilt)
adds nothing but pain, and we have upstream build and install targets that
are designed to cleanly separate the -arch specific and -indep components,
so regressing to make those codependent isn't very appealing either.  It
would have also broken support for building where m-a wasn't supported,
though that's less of a problem today than it was previously.

 -- Ron Lee <r...@debian.org>  Thu, 17 May 2018 16:07:39 +0930

opus (1.2.1-1) unstable; urgency=medium

  * Fixes a bug in surround encoding causing very bad quality on loud signals
beyond a certain amplitude.
  * Speech quality improvements especially in the 12-24 kbit/s range.
  * Music quality improvements in the 32-48 kb/s range.
  * More aggressive use of wider speech bandwidth, including fullband speech
starting at 14 kbit/s.
  * Improved VBR encoding for hybrid mode.
  * SILK CBR improvements.
  * DTX support for CELT mode.
  * Support for directly encoding packets up to 120 ms.
  * Improves quality on files with powerful tones that cause MDCT leakage.
  * Fixes for speech/music detection at the very beginning of files.
  * Fixes an issue where the encoder can misdetect that the signal is SWB
instead of FB, lowpassing the signal.

 -- Ron Lee <r...@debian.org>  Thu, 28 Sep 2017 01:48:45 +0930

opus (1.2~alpha2-1) unstable; urgency=medium

  

[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial

[Nicolas Dichtel]

Any news for the iproute2 part?

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

Title:
  sched: Match-all classifier is missing in xenial

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This is implemented in linux v4.8 by the following upstream patch:
  bf3994d2ed31 ("net/sched: introduce Match-all classifier")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31

  The backport is straightforward. It's useful in combination with
  clsact qdisc (see bug #1642510).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Tom]

@bernadette, it baffels me. Today my Xps 15, 9560 works flawlessly fast
and nimble. I also nailed the power drain and now have ~5W running on
battery, see https://github.com/stockmind/dell-xps-9560-ubuntu-
respin/issues/8

Makes me thinking... what BIOS version do you have ? I run 1.9.4

** Bug watch added: github.com/stockmind/dell-xps-9560-ubuntu-respin/issues #8
   https://github.com/stockmind/dell-xps-9560-ubuntu-respin/issues/8

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1766542] Re: Installation blocks when the machine is behind a proxy server

[Robert Liu]

Image: ubuntu-18.04-desktop-amd64.iso

Significant blockings -
"Retrieving file 1 of 3", 90 seconds
"Retrieving file 1 of 1", 32 seconds

The behavior is different from 16.04.

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  New
Status in ubiquity source package in Bionic:
  New

Bug description:
  When the machine is behind a proxy server, the installation will block
  for a while (several minutes) to retrieve the package lists. The
  timeouts are too long and makes user feels the machine may have some
  problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1766542] Re: Installation blocks when the machine is behind a proxy server

[Robert Liu]

Here is how I setup the environment:
1. prepare a broadband gateway. This time I use LEDE with VirtualBox. I can 
upload the VM image if necessary.
2. add a firewall rule on the gateway: all http/https traffic from LAN port 
will be redirected to a IP which is not used by any machine.
3. install Ubuntu and check the behavior.

I can reproduce the issue with this environment. Even though, I'm not
sure if this is exactly the same with the customer's environment.

@Steve, Yes, We are using oem-config mode. With the normal mode, because
it uses less archives and apt operations, the blocking time is shorter.
Please see my following comments, I'll provide my results of the
official 16.04 and 18.04 image.

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  New
Status in ubiquity source package in Bionic:
  New

Bug description:
  When the machine is behind a proxy server, the installation will block
  for a while (several minutes) to retrieve the package lists. The
  timeouts are too long and makes user feels the machine may have some
  problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1766542] Re: Installation blocks when the machine is behind a proxy server

[Robert Liu]

Image: ubuntu-16.04.4-desktop-amd64.iso

Significant blockings -
"Retrieving file 1 of 93", 30 seconds
"Retrieving file 1 of 31", 3 minutes

** Attachment added: "var-log-installer-16_04.tgz"
   
https://bugs.launchpad.net/oem-priority/+bug/1766542/+attachment/5141168/+files/var-log-installer-16_04.tgz

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  New
Status in ubiquity source package in Bionic:
  New

Bug description:
  When the machine is behind a proxy server, the installation will block
  for a while (several minutes) to retrieve the package lists. The
  timeouts are too long and makes user feels the machine may have some
  problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1771733] Re: bluetooth device disappears after several minutes of use

[Rob]

I have executed the command suggested by vanvugt for one week, but to
complicate matters further, I have been able to use my mouse for about
an hour now... I don't know how to troubleshoot this issue, but I will
update if I have any complications from this point forward... I just
replaced the batteries in my mouse, but that doesn't explain the loss of
*ALL* bluetooth hardware functionality until several reboots
later...right? Even with dead mouse batteries, surely my computer should
not report that there is no bluetooth hardware available. Please note
that bluetooth became available again *without* rebooting, I just hadn't
touched anything for several hours.

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Re: bluetooth device disappears after several minutes of use

[Daniel van Vugt]

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

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Lspci.txt

[Rob]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1771733/+attachment/5141143/+files/Lspci.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] getfacl.txt

[Rob]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141150/+files/getfacl.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcModules.txt

[Rob]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141148/+files/ProcModules.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] UdevDb.txt

[Rob]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1771733/+attachment/5141149/+files/UdevDb.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcCpuinfo.txt

[Rob]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141144/+files/ProcCpuinfo.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcEnviron.txt

[Rob]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141146/+files/ProcEnviron.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcInterrupts.txt

[Rob]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141147/+files/ProcInterrupts.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcCpuinfoMinimal.txt

[Rob]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141145/+files/ProcCpuinfoMinimal.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Dependencies.txt

[Rob]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141142/+files/Dependencies.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Re: bluetooth device disappears after several minutes of use

[Rob]

apport information

** Tags added: apport-collected bionic

** Description changed:

  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-date.
  
  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after several
  minutes of use, I find that my mouse has disconnected, and I no longer
  have a bluetooth icon in the top right status indicator. Then, when I
  open bluetooth settings, the window reads "No bluetooth found: Plug in a
  dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus
  UX305CA.
  
- This is my first bug report so please let me know if I've left out any
- important details and I will provide them as soon as possible. Thanks
- for all your hard work with Ubuntu Budgie!
+ This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: Budgie:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-15 (3 days ago)
+ InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. UX305CA
+ Package: bluez 5.48-0ubuntu3
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/08/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX305CA.300
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX305CA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: UX
+ dmi.product.name: UX305CA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN 
+   RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
+   TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141141/+files/CurrentDmesg.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  

[Touch-packages] [Bug 1771733] Re: bluetooth device disappears after several minutes of use

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1771733

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any
  important details and I will provide them as soon as possible. Thanks
  for all your hard work with Ubuntu Budgie!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Re: bluetooth device disappears after several minutes of use

[fossfreedom]

Ok. So not a TLP  issue. Subscribing to the bluez package. But may also
be kernel related.

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

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any
  important details and I will provide them as soon as possible. Thanks
  for all your hard work with Ubuntu Budgie!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[maryh]

http://buy.rvmiller.com

Mary Hamilton

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

Title:
  at least 3 reinstalls due to no onshut down or restart. msg  start up
  sometimes, tried boot repair,something was missing, sorry I can't
  remember terminology.  Problems started with  specialized downloads.
  Sound recorder(bad)sound converter,pixel swapper, great apps. I was
  thinking my att router has been compromised via win 10 updates..

Status in gcc-4.8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 over a year using with all updates worked great, then the
  Libre Office Writer went fooey,several re-installs,fixed.Then, I
  thought all my photos were getting shared live maybe via Libre Ofiice
  app

   Then  Firefox sync caused me a lot of grief when I installed it on
  two win10 desktops with Sync Not syncing now tho.

  I swapped the mouse, which doesn't want to function well. Got firefox
  straight maybe, then Ubuntu started hanging on restart or shut down. I
  tried running a boot repair, it said my registry was missing. I tried
  for a clean install, but I think all it did was add a copy. No
  reinstall would shut down.Tried a different version,same problem. I
  have an att router & have been installing updates et al, on 2 other
  desktops. As soon as I get a Win 10 going, something seems to stop
  working on Ubuntu. I prefer Ubuntu for multiple reasons. Win 10 seems
  to be a barebones with a big buynow catalog or surf the win10 web.
  However, it has a working Sound recorder, & AIO dell usb XP
  printer,fax etc.

   Also, I have a Nook reader with lots of apps I don't use. I've
  started using the OverDrive only app, as the google library
  chromeconnection kept me confused. added new windows, froze books,etc.
  It is wifi which I leave on continuously.

  I just learned Sudo init O. Used it one time. Worked fine.  These
  "bugs" seem to be attempts to wreak havoc,  I have copies of my
  files/photos on DVD, which I download to desktop when I re-install.

  So sorry. I break things worse trying to repair them many times, but
  I'm experienced at starting over, just don't like to. I am trying to
  avoid wiping the hd, reformatting, etc. Very time consuming for a
  little old lady pushing 70. Time is precious, but so is money,lol, so
  I do it myself.This bug reequest popped up, so maybe you can connect
  something from others with similar occurances.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cpp-4.8 4.8.2-19ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Feb  6 18:53:42 2016
  DuplicateSignature: package:cpp-4.8:4.8.2-19ubuntu1:cannot copy extracted 
data for './usr/bin/cpp-4.8' to '/usr/bin/cpp-4.8.dpkg-new': unexpected end of 
file or stream
  ErrorMessage: cannot copy extracted data for './usr/bin/cpp-4.8' to 
'/usr/bin/cpp-4.8.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gcc-4.8
  Title: package cpp-4.8 4.8.2-19ubuntu1 failed to install/upgrade: cannot copy 
extracted data for './usr/bin/cpp-4.8' to '/usr/bin/cpp-4.8.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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