[Touch-packages] [Bug 1760934] Re: Sound not working on HP x2 10-p030nl - Realtek rt5640

[Launchpad Bug Tracker]

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

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

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

Title:
  Sound not working on HP x2 10-p030nl - Realtek rt5640

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Audio doesn't work on every kernel I tried. I also used this
  https://github.com/plbossart/UCM, but this results in a pulseaudio
  crash. See this for more information:
  https://github.com/plbossart/UCM/issues/27

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  Uname: Linux 4.16.0-rc6+ x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
  CurrentDesktop: KDE
  Date: Tue Apr  3 19:19:35 2018
  InstallationDate: Installed on 2018-03-27 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827C
  dmi.board.vendor: HP
  dmi.board.version: 93.23
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.30:bd10/25/2017:svnHP:pnHPx2Detachable10-p0XX:pvr:rvnHP:rn827C:rvr93.23:cvnHP:ct32:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP x2 Detachable 10-p0XX
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1762142] Re: Please help me, i need an graphic driver that works on my notebook!

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

Title:
  Please help me, i need an graphic driver that works on my notebook!

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My graphic driver works not correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-119.143~14.04.1-generic 4.4.114
  Uname: Linux 4.4.0-119-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr  8 10:19:54 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] 
[1002:7942] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c034]
  InstallationDate: Installed on 2018-04-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R59P/R60P/R61P
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-119-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 09YI
  dmi.board.name: R59P/R60P/R61P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr09YI:bd09/26/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR59P/R60P/R61P:pvr05YI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR59P/R60P/R61P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
  dmi.product.name: R59P/R60P/R61P
  dmi.product.version: 05YI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 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: Sun Apr  8 09:34:08 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1761849] Re: Radiance title bar is a lot bigger in fullscreen than Ambiance

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Radiance title bar is a lot bigger in fullscreen than Ambiance

Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  Ubuntu 18.04 Beta 1
  Radiance title bar is relay huge, see screenshots below;

  Ambiance:
  https://i.imgur.com/Q31yqx9.png

  Radiance:
  https://i.imgur.com/SYL0U7y.png

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

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

[Touch-packages] [Bug 1762027] Re: unmet dependencies

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

Title:
  unmet dependencies

Status in xorg package in Ubuntu:
  Expired

Bug description:
   xserver-xorg-video-intel : Depends: xorg-video-abi-20
  Depends: xserver-xorg-core (>= 2:1.17.99.902)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr  7 18:05:38 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82G965 Integrated Graphics Controller 
[8086:514d]
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=42c3ea72-41c7-4bb4-9405-334a0711c62d ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: MQ96510J.86A.1676.2007.0413.0149
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG965SS
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD41678-308
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrMQ96510J.86A.1676.2007.0413.0149:bd04/13/2007:svnOEGStone:pn:pvr:rvnIntelCorporation:rnDG965SS:rvrAAD41678-308:cvn:ct3:cvr:
  dmi.sys.vendor: OEGStone
  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.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: Sat Apr  7 17:56:16 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputDell Dell USB Entry Keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   VGA-1
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1775756] [NEW] package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Mauricio Grueso]

Public bug reported:

hello excuse me my english , the procees of the update boot looder (init
ram) is not working

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
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.2
Architecture: amd64
Date: Thu Jun  7 22:39:49 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-01-07 (516 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
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: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package initramfs-tools 0.130ubuntu3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  hello excuse me my english , the procees of the update boot looder
  (init ram) is not working

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  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.2
  Architecture: amd64
  Date: Thu Jun  7 22:39:49 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-01-07 (516 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1775593] Re: X server crashes with SIGBUS when resuming from suspend

[Daniel van Vugt]

Thanks for the bug report. The crash file shows:

Stacktrace:
 #0  0x5631c45681f1 in  ()
 #1  0x5631c45694f1 in LogVMessageVerbSigSafe ()
 #2  0x5631c45681a9 in ErrorFSigSafe ()
 #3  0x5631c455b892 in xorg_backtrace ()
 #4  0x5631c455f649 in  ()
 #5  0x7f5f09769890 in  () at 
/lib/x86_64-linux-gnu/libpthread.so.0
 #6  0x7f5f068397d0 in  () at 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
 #7  0x5631c446e572 in xf86CrtcSetModeTransform ()
 #8  0x5631c4475c62 in  ()
 #9  0x5631c44b9a32 in RRCrtcSet ()
 #10 0x5631c44bb2b3 in ProcRRSetCrtcConfig ()
 ...

but that may be inaccurate without proper retracing.

Please follow the instructions 1,6,7 from here:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment


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

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  X server crashes with SIGBUS when resuming from suspend

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Every night I suspend my laptop and resume it in the morning. At least
  once a week, the X server crashes with SIGBUS when resuming from
  suspend.

  I scoured systemd journals and all logs under /var/log, and this was
  the only suspicious message I found:

  [ 59358.134] (EE) /dev/dri/card0: failed to set DRM interface version
  1.4: Permission denied

  As my graphics card uses driver i915, I installed xserver-xorg-video-
  intel-dbg but couldn't find any package with debugging symbols for
  xserver-xorg-core, so running 'sudo gdb --core=/core' only yielded
  this:

  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGBUS, Bus error.
  #0  0x5631c45681f1 in ?? ()
  [Current thread is 1 (LWP 1016)]
  (gdb) bt
  #0  0x5631c45681f1 in ?? ()
  #1  0x0001 in ?? ()
  #2  0x5631c5a03350 in ?? ()
  #3  0x0001 in ?? ()
  #4  0x5631c4596ec5 in ?? ()
  #5  0x7f5f0974e2a0 in ?? ()
  #6  0x7f5f093e5977 in ?? ()
  #7  0x in ?? ()

  I'm attaching apport's crash report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Jun  7 08:56:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04b0]
  InstallationDate: Installed on 2018-04-28 (39 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash 
systemd.legacy_systemd_cgroup_controller=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 08FDW5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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-server/+bug/1775593/+subscriptions

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Daniel van Vugt]

There hasn't been a bluez update to 16.04 since last year. And here
hasn't been a kernel update to 16.04 since last month; the same goes for
linux-firmware.

So I'm not sure what changed for you Zero. Are you using 16.04?

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 

[Touch-packages] [Bug 1775723] [NEW] Resolved resolution delay when interacting with dnsmasq

[Pavel Stratil]

Public bug reported:

After hitting a problem with lxd on a server install (see
https://github.com/lxc/lxd/issues/4631) I was adviced by Stéphane Graber
to report a bug here. The gist of the bug is the following:

- lxd snap uses internally dnsmasq
- the 18.04 server install defaults to using systemd-resolved
- upon (re)boot, the lxd stap fails to start because of systemd-resolved not 
resolving shortly after boot. 

To keep this bug report short, please kindly refer to
https://github.com/lxc/lxd/issues/4631 for a complete set of logs and a
"how to replicate" guide.

Thanks for looking into this, 
cheers, Pavel

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


** Tags: dnsmasq lxd systemd-resolved

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

Title:
  Resolved resolution delay when interacting with dnsmasq

Status in systemd package in Ubuntu:
  New

Bug description:
  After hitting a problem with lxd on a server install (see
  https://github.com/lxc/lxd/issues/4631) I was adviced by Stéphane
  Graber to report a bug here. The gist of the bug is the following:

  - lxd snap uses internally dnsmasq
  - the 18.04 server install defaults to using systemd-resolved
  - upon (re)boot, the lxd stap fails to start because of systemd-resolved not 
resolving shortly after boot. 

  To keep this bug report short, please kindly refer to
  https://github.com/lxc/lxd/issues/4631 for a complete set of logs and
  a "how to replicate" guide.

  Thanks for looking into this, 
  cheers, Pavel

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

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

[Touch-packages] [Bug 1356222] Re: [MIR] fcitx and related packages

[Matthias Klose]

ok, then closing all these as won't fix.

** Changed in: fcitx-anthy (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: fcitx-chewing (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: fcitx-googlepinyin (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: fcitx-m17n (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: fcitx-sunpinyin (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: fcitx-table-extra (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: fcitx-table-other (Ubuntu)
   Status: Fix Committed => Won't Fix

** Changed in: libgooglepinyin (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  [MIR] fcitx and related packages

Status in extra-cmake-modules package in Ubuntu:
  Fix Released
Status in fcitx package in Ubuntu:
  Fix Released
Status in fcitx-anthy package in Ubuntu:
  Won't Fix
Status in fcitx-chewing package in Ubuntu:
  Won't Fix
Status in fcitx-cloudpinyin package in Ubuntu:
  Fix Released
Status in fcitx-configtool package in Ubuntu:
  Fix Released
Status in fcitx-googlepinyin package in Ubuntu:
  Won't Fix
Status in fcitx-hangul package in Ubuntu:
  Fix Released
Status in fcitx-m17n package in Ubuntu:
  Won't Fix
Status in fcitx-qimpanel package in Ubuntu:
  Fix Released
Status in fcitx-qt5 package in Ubuntu:
  Fix Released
Status in fcitx-sunpinyin package in Ubuntu:
  Won't Fix
Status in fcitx-table-extra package in Ubuntu:
  Won't Fix
Status in fcitx-table-other package in Ubuntu:
  Won't Fix
Status in fcitx-unikey package in Ubuntu:
  Fix Released
Status in libgooglepinyin package in Ubuntu:
  Won't Fix
Status in presage package in Ubuntu:
  Fix Released
Status in tinyxml package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  Currently in universe

  [Rationale]
  Fcitx is a replacement candidate for IBus

  [Security: ]
  CVE entries: none
  Security history: none
  Any binaries running as root or suid/sgid ? Any daemons ?
  -- all running as per user session, and /usr/bin/fcitx and 
/usr/bin/fcitx-qimpanel will run as daemon, /usr/bin/fcitx-dbus-watcher will be 
pulled up when fcitx is running.
  Network activity: does it open any port ? Does it handle incoming network 
data ?
  -- fcitx-cloudpinyin deals with network data by using libcurl and 
interact with remote API from several user-choosable providers.
  Does it directly (not through a library) process binary (video, audio, etc) 
or structured (PDF, etc) data ?
  -- no, it doesn't
  Any source code review performed ? (The approver will do a quick and shallow 
check.)
  -- no.

  [Quality Assurance]
  Package works out of the box with no prompting.
  There is no reproducible major bugs in Ubuntu and Debian.
  Upstream is active.
  Package is team maintained at Debian, and is the same people working on 
Debian and Ubuntu.

  Upstream bug tracker: https://github.com/fcitx/fcitx
  Hardware: Does this package deal with hardware and if so how exotic is it ?
  -- no
  Is there a test suite in the upstream source or packaging ? Is it enabled to 
run in the build ?
  -- yes, some fundamental tests

  [UI standards]
  User-visible strings are internationalized using standard gettext system ?
  -- yes
  Package with translatable strings builds a PO template during package 
build ?
  -- yes
  End-user applications ship a desktop file?
  -- fcitx and fcitx-ui-qimpanel do.

  [Standards Compliance]
  FHS and Debian Policy compliant.
  Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities 
?
  -- package is using debhelper,

  [Maintenance]
  Desktop Team will take care of them

  [Dependencies]
  librime and brise are for fcitx-rime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/extra-cmake-modules/+bug/1356222/+subscriptions

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

[Touch-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-6.0 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-6.0/1:6.0-1ubuntu2~16.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: llvm-toolchain-6.0 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

[Touch-packages] [Bug 1775661] Re: package python2-minimal (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in package python-minimal 2.

[Matthias Klose]

fixed in -2

** Changed in: python-defaults (Ubuntu)
   Status: New => Fix Released

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

Title:
  package python2-minimal (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also
  in package python-minimal 2.7.15-1

Status in python-defaults package in Ubuntu:
  Fix Released

Bug description:
  the system fail, just it. I don't know about this...

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: python2-minimal (not installed)
  Uname: Linux 4.16.13-041613-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Thu Jun  7 13:36:03 2018
  DuplicateSignature:
   package:python2-minimal:(not installed)
   Unpacking python2-minimal (2.7.15-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/python2-minimal_2.7.15-1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
  ErrorMessage: trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which 
is also in package python-minimal 2.7.15-1
  InstallationDate: Installed on 2018-06-03 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180602)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha0ubuntu1
  SourcePackage: python-defaults
  Title: package python2-minimal (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763822] Re: package software-properties-common 0.96.24.28 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Brian Murray]

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  package software-properties-common 0.96.24.28 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 127

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Package crash after log in

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: software-properties-common 0.96.24.28
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 13 17:34:14 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2017-04-13 (364 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.28 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
127
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (0 days ago)

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

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

[Touch-packages] [Bug 1768379] Re: failed 16.04 LTS -> 18.04 LTS upgrade

[Julian Andres Klode]

Minimal test case, unpacking python3-minimal and python3-apt from artful
on xenial:


root@lp1768379:~# dpkg --unpack 
/home/jak/Downloads/python3-minimal_3.6.3-0ubuntu2_amd64.deb 
(Reading database ... 25653 files and directories currently installed.)
Preparing to unpack .../python3-minimal_3.6.3-0ubuntu2_amd64.deb ...
Unpacking python3-minimal (3.6.3-0ubuntu2) over (3.5.1-3) ...
Processing triggers for man-db (2.7.5-1) ...
root@lp1768379:~# dpkg --unpack 
/home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb 
(Reading database ... 25653 files and directories currently installed.)
Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ...
/var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: 
py3clean: not found
dpkg: warning: subprocess old pre-removal script returned error exit status 127
dpkg: trying script from the new package instead ...
/var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
dpkg: error processing archive 
/home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 127
/var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb

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

Title:
  failed 16.04 LTS -> 18.04 LTS upgrade

Status in python3-defaults package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install
  failure:

  Fetched 2,320 MB in 6s (27.8 MB/s)

  Upgrading
  Inhibiting until Ctrl+C is pressed...
  Fetched 0 B in 0s (0 B/s) 

  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  (Reading database ... 373383 files and directories currently installed.)
  Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ...
  Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  Setting up base-files (10.1ubuntu2) ...
  Installing new version of config file /etc/debian_version ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Updating /etc/profile to current default.
  motd-news.service is a disabled or a static unit, not starting it.
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../debianutils_4.8.4_amd64.deb ...
  Unpacking debianutils (4.8.4) over (4.7) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up debianutils (4.8.4) ...
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
  Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up bash (4.4.18-2ubuntu1) ...
  Installing new version of config file /etc/bash.bashrc ...
  Installing new version of config file /etc/skel/.profile ...
  update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide 
/usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to 

[Touch-packages] [Bug 1775713] [NEW] printer does not print ink even though it is detected

[Ronald Ramsey]

Public bug reported:

USB printer model Epson ET-4500 detects the desktop it is connected to,
but when printing a piece of paper the printer only spits out plain
paper with no ink.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4ubuntu0.4
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun  7 17:37:23 2018
InstallationDate: Installed on 2016-10-12 (603 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: device for EpsonET-4500: 
usb://EPSON/ET-4500%20Series?serial=573937593033313180=1
MachineType: Dell Inc. OptiPlex 780
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EpsonET-4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EpsonET-4500.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=03b2da64-2d26-4809-b705-f42bd7d8a473 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0C27VV
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/11/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA02:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 780
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apparmor apport-bug xenial

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

Title:
  printer does not print ink even though it is detected

Status in cups package in Ubuntu:
  New

Bug description:
  USB printer model Epson ET-4500 detects the desktop it is connected
  to, but when printing a piece of paper the printer only spits out
  plain paper with no ink.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun  7 17:37:23 2018
  InstallationDate: Installed on 2016-10-12 (603 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for EpsonET-4500: 
usb://EPSON/ET-4500%20Series?serial=573937593033313180=1
  MachineType: Dell Inc. OptiPlex 780
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EpsonET-4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EpsonET-4500.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=03b2da64-2d26-4809-b705-f42bd7d8a473 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0C27VV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/11/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA02:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 879838] Re: Keyboard Layout "Germany Neo 2": Mod4 does not work if used as secondary keyboard layout

[Jens]

Working output with xkbcomp $DISPLAY

** Attachment added: "output-neo2-working.xkb"
   
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+attachment/5149978/+files/output-neo2-working.xkb

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

Title:
  Keyboard Layout "Germany Neo 2": Mod4 does not work if used as
  secondary keyboard layout

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is,
  Mod4) don't work. To reproduce this bug, do the following:

  1: Neo 2 as primary keyboard layout
  - start gnome-keyboard-properties
  - Click "Add..."
  - Select Country: "Germany" and Variants: "Germany Neo 2"
  - Select "Germany Neo 2" and move it to the top of the list.
  Try to use Neo Layer 4 or 6. E.g. type the number "4" which is "Mod4" and "n" 
in Neo ("<" and "j" in standard German QWERTZ layout) or move the cursor left 
using "Mod4" and "i" ("AltGr" and "s" in QWERTZ layot).  Works as expected.

  2: Neo as secondary layout
  - Now add "Germany Eliminate dead keys" to the list and move it to the top
  - Use "Neo 2" as secondary layout
  - Click "Options" and select "Scroll lock" (or any other) as "Key(s) to 
change layout"
  Now switch to Neo using the selected key and try to type "4" or move the 
curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is, 
you will be typing an "n" instead of a "4" and an "i" instead of moving the 
cursor left). 

  Choosing other keys for layout change or turning the compose key
  on/off does not change anything. Neither does applying "Neo 2" as
  primary layout system wide and using "Germany Eliminate dead keys"
  with "Neo 2" as a secondary keyboard layout as local user.

  Applying the patch suggested on neo-layout.org for a similar problem
  (http://wiki.neo-layout.org/ticket/174) does not have any effect.

  Description:  Ubuntu 11.04
  Release:  11.04
  xkb-data: 2.1-1ubuntu3

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

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

[Touch-packages] [Bug 879838] Re: Keyboard Layout "Germany Neo 2": Mod4 does not work if used as secondary keyboard layout

[Jens]

Not working export with xkbcomp $DISPLAY

** Attachment added: "output-neo2-not-working.xkb"
   
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+attachment/5149977/+files/output-neo2-not-working.xkb

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

Title:
  Keyboard Layout "Germany Neo 2": Mod4 does not work if used as
  secondary keyboard layout

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is,
  Mod4) don't work. To reproduce this bug, do the following:

  1: Neo 2 as primary keyboard layout
  - start gnome-keyboard-properties
  - Click "Add..."
  - Select Country: "Germany" and Variants: "Germany Neo 2"
  - Select "Germany Neo 2" and move it to the top of the list.
  Try to use Neo Layer 4 or 6. E.g. type the number "4" which is "Mod4" and "n" 
in Neo ("<" and "j" in standard German QWERTZ layout) or move the cursor left 
using "Mod4" and "i" ("AltGr" and "s" in QWERTZ layot).  Works as expected.

  2: Neo as secondary layout
  - Now add "Germany Eliminate dead keys" to the list and move it to the top
  - Use "Neo 2" as secondary layout
  - Click "Options" and select "Scroll lock" (or any other) as "Key(s) to 
change layout"
  Now switch to Neo using the selected key and try to type "4" or move the 
curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is, 
you will be typing an "n" instead of a "4" and an "i" instead of moving the 
cursor left). 

  Choosing other keys for layout change or turning the compose key
  on/off does not change anything. Neither does applying "Neo 2" as
  primary layout system wide and using "Germany Eliminate dead keys"
  with "Neo 2" as a secondary keyboard layout as local user.

  Applying the patch suggested on neo-layout.org for a similar problem
  (http://wiki.neo-layout.org/ticket/174) does not have any effect.

  Description:  Ubuntu 11.04
  Release:  11.04
  xkb-data: 2.1-1ubuntu3

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

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

[Touch-packages] [Bug 879838] Re: Keyboard Layout "Germany Neo 2": Mod4 does not work if used as secondary keyboard layout

[Jens]

I just hit this bug too and can confirm it for 17.10 and 18.04.

However, there is an easy workaround: Make sure Neo2 is the only layout
in your XKB keymap. The easiest way would be to have just one layout.
Another solution for me is to have exactly 4 layouts and Neo2 is the
4th. Checking with "xkbcomp $DISPLAY output.xkb" both ways lead to the
same keymap.

I will attach a working and non working xkbcomp output. Maybe someone
with more experience can diff these and find the root cause.

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

Title:
  Keyboard Layout "Germany Neo 2": Mod4 does not work if used as
  secondary keyboard layout

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is,
  Mod4) don't work. To reproduce this bug, do the following:

  1: Neo 2 as primary keyboard layout
  - start gnome-keyboard-properties
  - Click "Add..."
  - Select Country: "Germany" and Variants: "Germany Neo 2"
  - Select "Germany Neo 2" and move it to the top of the list.
  Try to use Neo Layer 4 or 6. E.g. type the number "4" which is "Mod4" and "n" 
in Neo ("<" and "j" in standard German QWERTZ layout) or move the cursor left 
using "Mod4" and "i" ("AltGr" and "s" in QWERTZ layot).  Works as expected.

  2: Neo as secondary layout
  - Now add "Germany Eliminate dead keys" to the list and move it to the top
  - Use "Neo 2" as secondary layout
  - Click "Options" and select "Scroll lock" (or any other) as "Key(s) to 
change layout"
  Now switch to Neo using the selected key and try to type "4" or move the 
curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is, 
you will be typing an "n" instead of a "4" and an "i" instead of moving the 
cursor left). 

  Choosing other keys for layout change or turning the compose key
  on/off does not change anything. Neither does applying "Neo 2" as
  primary layout system wide and using "Germany Eliminate dead keys"
  with "Neo 2" as a secondary keyboard layout as local user.

  Applying the patch suggested on neo-layout.org for a similar problem
  (http://wiki.neo-layout.org/ticket/174) does not have any effect.

  Description:  Ubuntu 11.04
  Release:  11.04
  xkb-data: 2.1-1ubuntu3

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

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

[Touch-packages] [Bug 1768379] Re: failed 16.04 LTS -> 18.04 LTS upgrade

[Matthias Klose]

please be careful with pre-dependencies. These tend to break other stuff
... why do you think that the pre-dependency will solve things here?

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

Title:
  failed 16.04 LTS -> 18.04 LTS upgrade

Status in python3-defaults package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install
  failure:

  Fetched 2,320 MB in 6s (27.8 MB/s)

  Upgrading
  Inhibiting until Ctrl+C is pressed...
  Fetched 0 B in 0s (0 B/s) 

  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  (Reading database ... 373383 files and directories currently installed.)
  Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ...
  Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  Setting up base-files (10.1ubuntu2) ...
  Installing new version of config file /etc/debian_version ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Updating /etc/profile to current default.
  motd-news.service is a disabled or a static unit, not starting it.
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../debianutils_4.8.4_amd64.deb ...
  Unpacking debianutils (4.8.4) over (4.7) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up debianutils (4.8.4) ...
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
  Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up bash (4.4.18-2ubuntu1) ...
  Installing new version of config file /etc/bash.bashrc ...
  Installing new version of config file /etc/skel/.profile ...
  update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide 
/usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ...
  Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ...
  Selecting previously unselected package libcom-err2:amd64.
  Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ...
  Unpacking libcom-err2:amd64 (1.44.1-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu10) ...
  Setting up libcom-err2:amd64 (1.44.1-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu10) ...
  (Reading database ... 373391 files and directories currently installed.)
  Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ...
  Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ...
  Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ...
  Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ...
  Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ...
  Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) 
...
  Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ...
  Unpacking libkrb5-3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../liblzma5_5.2.2-1.3_amd64.deb ...
  De-configuring 

[Touch-packages] [Bug 1775700] [NEW] development package calls for .la in Libs but not provided

[Jorge Rivera]

Public bug reported:

The package config info files for libgstreamer-plugins-bad1.0-dev v1.8.x

gstreamer-bad-audio-1.0.pc
gstreamer-bad-base-1.0.pc
gstreamer-bad-video-1.0.pc

Calls for these libraries:

...
Libs: -L${libdir} ${libdir}/libgstbadaudio-1.0.la
...

However, the package does not include the .la files listed.

Removing the .la files from the .pc file allows for successful
compilation of some projects, but if they are required for some reason,
they should be included in the package.

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  development package calls for .la in Libs but not provided

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  The package config info files for libgstreamer-plugins-bad1.0-dev
  v1.8.x

  gstreamer-bad-audio-1.0.pc
  gstreamer-bad-base-1.0.pc
  gstreamer-bad-video-1.0.pc

  Calls for these libraries:

  ...
  Libs: -L${libdir} ${libdir}/libgstbadaudio-1.0.la
  ...

  However, the package does not include the .la files listed.

  Removing the .la files from the .pc file allows for successful
  compilation of some projects, but if they are required for some
  reason, they should be included in the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1775700/+subscriptions

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

[Touch-packages] [Bug 1772632] Re: Backport packages for 16.04.5 HWE stack

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.91-2~16.04.1 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: libdrm (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Backport packages for 16.04.5 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-6.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New
Status in xserver-xorg-video-intel source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.5 ***

  A minor update, only xserver sync, some driver updates plus a newer
  Mesa.

  Mesa needs llvm-toolchain-6.0 and libclc, libdrm, updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.83 to 2.4.91
  - amdgpu: new pci-ids, bugfixes
  - intel: new pci-ids
  - drm: some new ioctl's
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  llvm-toolchain-6.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-6 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.5 to 1.19.6+git 
include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.5. Tracking bug for 
the bugfix release (bionic) is bug 1772607

  [Other info]

  build order: [libdrm, llvm-toolchain-6.0], [libclc, xorg-server], mesa

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

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

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

[David Britton]

For landscape, we will try systemctl reboot, and systemctl -f reboot,
this warning in the manpage:

Warning: specifying --force twice with any of these operations might result
   in data loss.

seems like something we don't want to do with managed machines.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

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

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

[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

[Timo Aaltonen]

please check if libnvidia-gl-390 is installed:

apt-cache policy libnvidia-gl-390

and if so, this is a dupe of 1770913, you want libegl-mesa0 and libglx-
mesa0 installed instead..

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/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: B85M-D3V-A
  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:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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-1ubuntu2
  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/1752938/+subscriptions

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

[Touch-packages] [Bug 1772607] Re: Mesa 18.0.5 stable release

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted libglvnd into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.1 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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: libglvnd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Mesa 18.0.5 stable release

Status in libglvnd package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libglvnd source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point 
release of the series.

  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems.

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

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

[Touch-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted libdrm into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.91-2~16.04.1 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: libdrm (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

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

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

[Touch-packages] [Bug 1775676] Re: file is not showing in a good format

[Seth Arnold]

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

Title:
  file is not showing in a good format

Status in xorg package in Ubuntu:
  New

Bug description:
  all my files are not shpoing well

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Jun  7 18:55:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:172a]
  InstallationDate: Installed on 2018-05-26 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=ff2e3855-9d5d-4ca8-abf2-661b693284ca ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.20
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.20:bd09/05/2011:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard
  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.1.1-0~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.1-0~b~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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/1775676/+subscriptions

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

[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

[Jean-Baptiste Lallement]

** Tags added: rls-bb-incoming

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

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/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: B85M-D3V-A
  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:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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-1ubuntu2
  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/1752938/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] Re: Sync opus 1.3~beta+20180518-1 (main) from Debian sid (main)

[Jeremy Bicha]

Matthias, since you've done "recent" merges for this package, what do
you think about syncing here?

** Tags added: cosmic upgrade-software-version

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

Title:
  Sync opus 1.3~beta+20180518-1 (main) from Debian sid (main)

Status in opus package in Ubuntu:
  New

Bug description:
  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   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   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.
* 

[Touch-packages] [Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * Unattended-upgrades fails to autoremove packages after installing
+ updates or fails to install updates due to a parallel process acquiring
+ apt or dpkg lock while u-u is running.
+ 
+ [Test Case]
+ 
+  * Set up a system with packages (> 30) to be upgraded. In case of
+ Bionic -security has a low number of updates, thus set up the system to
+ install -updates to have more packages for u-u to upgrade:
+ 
+  echo 'Unattended-Upgrade::Allowed-Origins::
+ "${distro_id}:${distro_codename}-updates";' >
+ /etc/apt/apt.conf.d/51-updates
+ 
+  * Set up two shells to run commands in parallel
+  * In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run 
--verbose --debug
+  * After u-u started run the following command in shell "B":
+  while sleep 1; do python3 -c 'import apt; import apt_pkg; 
print(apt_pkg.pkgsystem_lock())' ; done
+  * Observe the following exception repeated while running u-u and True being 
printed after u-u is finished:
+ ...
+ Traceback (most recent call last):
+   File "", line 1, in 
+ apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
+ Traceback (most recent call last):
+   File "", line 1, in 
+ apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
+ True
+ Traceback (most recent call last):
+   File "", line 1, in 
+ apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
+ True
+ True
+ True
+ True
+ ...
+ 
+ [Regression Potential WIP]
+ 
+  * Unattended-upgrade may crash
+ 
+ [Original Bug Text]
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unattended-upgrades.  This problem was most recently seen with
  version 0.90, the problem page at
  https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
  contains more details.

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

Title:
  /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin
  /unattended-
  upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * Unattended-upgrades fails to autoremove packages after installing
  updates or fails to install updates due to a parallel process
  acquiring apt or dpkg lock while u-u is running.

  [Test Case]

   * Set up a system with packages (> 30) to be upgraded. In case of
  Bionic -security has a low number of updates, thus set up the system
  to install -updates to have more packages for u-u to upgrade:

   echo 'Unattended-Upgrade::Allowed-Origins::
  "${distro_id}:${distro_codename}-updates";' >
  /etc/apt/apt.conf.d/51-updates

   * Set up two shells to run commands in parallel
   * In shell "A" run sudo apt update && sudo unattended-upgrade --dry-run 
--verbose --debug
   * After u-u started run the following command in shell "B":
   while sleep 1; do python3 -c 'import apt; import apt_pkg; 
print(apt_pkg.pkgsystem_lock())' ; done
   * Observe the following exception repeated while running u-u and True being 
printed after u-u is finished:
  ...
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  Traceback (most recent call last):
File "", line 1, in 
  apt_pkg.Error: E:Could not get lock /var/lib/dpkg/lock - open (11: Resource 
temporarily unavailable), E:Unable to lock the administration directory 
(/var/lib/dpkg/), is another process using it?
  True
  True
  True
  True
  ...

  [Regression Potential WIP]

   * Unattended-upgrade may crash

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unattended-upgrades.  This problem was most recently seen
  with version 0.90, the problem page at
  https://errors.ubuntu.com/problem/19f99745d7dce5aea118eb31bfffcbdcdf238c4f
  contains more details.

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

-- 
Mailing list: 

[Touch-packages] [Bug 1770965] Re: After upgrade and reboot, the lightdm display manager does not start

[Brian Murray]

"It turns out that the problem is caused by lightdm: When its
configuration points to a not-installed greeter, it fails to load." <-
It'd be good if this were fixed in lightdm.

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

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

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Critical => High

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

Title:
  After upgrade and reboot, the lightdm display manager does not start

Status in lightdm package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  Upon the upgrade, lightdm-kde-greeter was removed as it has become
  obsolete. That leaves the user with a system that hangs.

  I rebooted using system-recovery, and installed lightdm-gtk-greeter
  using aptitude. However, this greeter was not enabled in lightdm.conf.
  Also, the greeter was not configured with the background image for
  this release. I had to do these actions manually. Only then did
  lightdm start properly and with a nice background.

  For most users this problem will leave the system unusable forever,
  and should therefore be avoided. The obsolete greeter should be
  replaced with a suitable greeter.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  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
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Sun May 13 16:30:51 2018
  InstallationDate: Installed on 2013-02-05 (1922 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2018-05-13 12:28:57.668250
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

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

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

[Touch-packages] [Bug 1768379] Re: failed 16.04 LTS -> 18.04 LTS upgrade

[Brian Murray]

python3-minimal should predepend on whatever the current version of
python3 minimal is e.g. python3.6-minimal.

** Changed in: python3-defaults (Ubuntu)
   Status: New => Triaged

** Changed in: python3-defaults (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  failed 16.04 LTS -> 18.04 LTS upgrade

Status in python3-defaults package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install
  failure:

  Fetched 2,320 MB in 6s (27.8 MB/s)

  Upgrading
  Inhibiting until Ctrl+C is pressed...
  Fetched 0 B in 0s (0 B/s) 

  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  (Reading database ... 373383 files and directories currently installed.)
  Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ...
  Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  Setting up base-files (10.1ubuntu2) ...
  Installing new version of config file /etc/debian_version ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Updating /etc/profile to current default.
  motd-news.service is a disabled or a static unit, not starting it.
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../debianutils_4.8.4_amd64.deb ...
  Unpacking debianutils (4.8.4) over (4.7) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up debianutils (4.8.4) ...
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
  Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up bash (4.4.18-2ubuntu1) ...
  Installing new version of config file /etc/bash.bashrc ...
  Installing new version of config file /etc/skel/.profile ...
  update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide 
/usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ...
  Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ...
  Selecting previously unselected package libcom-err2:amd64.
  Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ...
  Unpacking libcom-err2:amd64 (1.44.1-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu10) ...
  Setting up libcom-err2:amd64 (1.44.1-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu10) ...
  (Reading database ... 373391 files and directories currently installed.)
  Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ...
  Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ...
  Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ...
  Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ...
  Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ...
  Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) 
...
  Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ...
  Unpacking libkrb5-3:amd64 

[Touch-packages] [Bug 1775664] [NEW] package procps 2:3.3.10-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[martin]

Public bug reported:

i dont know enough but this is automatically generated

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.4
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu Jun  7 21:56:09 2018
DpkgHistoryLog:
 Start-Date: 2018-06-07  21:55:52
 Commandline: aptdaemon role='role-commit-packages' sender=':1.91'
 Upgrade: libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.2, 2.4.42+dfsg-2ubuntu3.3), 
git-man:amd64 (1:2.7.4-0ubuntu1.3, 1:2.7.4-0ubuntu1.4), liblouis9:amd64 
(2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.3), snapd:amd64 (2.32.3.2, 2.32.9), 
libelf1:amd64 (0.165-3ubuntu1, 0.165-3ubuntu1.1), git:amd64 
(1:2.7.4-0ubuntu1.3, 1:2.7.4-0ubuntu1.4), python3-louis:amd64 
(2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.3), libexempi3:amd64 (2.2.2-2, 
2.2.2-2ubuntu0.1), liblouis-data:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.3)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-03-07 (822 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: procps
Title: package procps 2:3.3.10-4ubuntu2.4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package procps 2:3.3.10-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in procps package in Ubuntu:
  New

Bug description:
  i dont know enough but this is automatically generated

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Jun  7 21:56:09 2018
  DpkgHistoryLog:
   Start-Date: 2018-06-07  21:55:52
   Commandline: aptdaemon role='role-commit-packages' sender=':1.91'
   Upgrade: libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.2, 
2.4.42+dfsg-2ubuntu3.3), git-man:amd64 (1:2.7.4-0ubuntu1.3, 
1:2.7.4-0ubuntu1.4), liblouis9:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.3), 
snapd:amd64 (2.32.3.2, 2.32.9), libelf1:amd64 (0.165-3ubuntu1, 
0.165-3ubuntu1.1), git:amd64 (1:2.7.4-0ubuntu1.3, 1:2.7.4-0ubuntu1.4), 
python3-louis:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.3), libexempi3:amd64 
(2.2.2-2, 2.2.2-2ubuntu0.1), liblouis-data:amd64 (2.6.4-2ubuntu0.1, 
2.6.4-2ubuntu0.3)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-07 (822 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Steve Langasek]

The error complains that files will be overwritten, but this code runs
in the systemd-shim postrm script, which is after systemd-shim's files
have been removed from disk.  What does 'dpkg -S /usr/share/dbus-1
/system-services/org.freedesktop.systemd1.service' report in this
situation?

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

** Changed in: systemd-shim (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/1773859

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  Incomplete
Status in systemd source package in Bionic:
  New
Status in systemd-shim source package in Bionic:
  New

Bug description:
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1775661] Re: package python2-minimal (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in package python-minimal 2.

[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 python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1775661

Title:
  package python2-minimal (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also
  in package python-minimal 2.7.15-1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  the system fail, just it. I don't know about this...

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: python2-minimal (not installed)
  Uname: Linux 4.16.13-041613-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Thu Jun  7 13:36:03 2018
  DuplicateSignature:
   package:python2-minimal:(not installed)
   Unpacking python2-minimal (2.7.15-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/python2-minimal_2.7.15-1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
  ErrorMessage: trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which 
is also in package python-minimal 2.7.15-1
  InstallationDate: Installed on 2018-06-03 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180602)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha0ubuntu1
  SourcePackage: python-defaults
  Title: package python2-minimal (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[Brian Murray]

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

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

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

** Changed in: kubuntu-settings (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: ubuntu-gnome-default-settings (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: ubuntu-mate-artwork (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Invalid
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Invalid
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Invalid
Status in budgie-artwork source package in Artful:
  Fix Released
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  

[Touch-packages] [Bug 1775661] [NEW] package python2-minimal (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in package python-minimal

[Andre Leemax]

Public bug reported:

the system fail, just it. I don't know about this...

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: python2-minimal (not installed)
Uname: Linux 4.16.13-041613-generic x86_64
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
Date: Thu Jun  7 13:36:03 2018
DuplicateSignature:
 package:python2-minimal:(not installed)
 Unpacking python2-minimal (2.7.15-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/python2-minimal_2.7.15-1_amd64.deb (--unpack):
  trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
ErrorMessage: trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is 
also in package python-minimal 2.7.15-1
InstallationDate: Installed on 2018-06-03 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180602)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu3
 apt  1.7.0~alpha0ubuntu1
SourcePackage: python-defaults
Title: package python2-minimal (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic package-conflict

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

Title:
  package python2-minimal (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also
  in package python-minimal 2.7.15-1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  the system fail, just it. I don't know about this...

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: python2-minimal (not installed)
  Uname: Linux 4.16.13-041613-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Thu Jun  7 13:36:03 2018
  DuplicateSignature:
   package:python2-minimal:(not installed)
   Unpacking python2-minimal (2.7.15-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/python2-minimal_2.7.15-1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
  ErrorMessage: trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which 
is also in package python-minimal 2.7.15-1
  InstallationDate: Installed on 2018-06-03 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180602)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha0ubuntu1
  SourcePackage: python-defaults
  Title: package python2-minimal (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/man/man1/pyclean.1.gz', which is also in 
package python-minimal 2.7.15-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1616448] Re: [MIR] qtsensors-opensource-src

[Matthias Klose]

that got demoted again

** Changed in: qtsensors-opensource-src (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  [MIR] qtsensors-opensource-src

Status in qtsensors-opensource-src package in Ubuntu:
  Won't Fix

Bug description:
  Availability: In universe, builds for all archs.

  Rationale: A goal for Ubuntu 16.10 is to have unity8 installed by
  default as an optional session. qtsensors is part of the stack that is
  needed for this goal. Qtsensors was already in main earlier when
  qtwebkit was, bug #1192567.

  Security: No known security history. No daemons or services.

  Quality assurance: No bugs open in Debian. A bug about certain tests
  failing on builders is in Ubuntu (those tests only work in local
  installations and are disabled with a patch). The latest upstream
  stable LTS version is part of yakkety and upcoming Debian release. For
  yakkety, we will not upgrade to Qt 5.7 but stay with the 5.6 LTS.

  Dependencies: All binary dependencies are in main.

  Standard compliance: Packaging seems compliant with 1 lintian warning.

  Maintenance: Qt Company maintains qtsensors as an official module in
  Qt. Qt 5.6 will be supported for bug and security fixes for three
  years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsensors-opensource-src/+bug/1616448/+subscriptions

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

[Touch-packages] [Bug 1621216] Re: [MIR] geoclue-2.0

[Mathieu Trudel-Lapierre]

Unsubscribing ~ubuntu-mir: the MIR for geoclue-2.0 and iio-sensor-prxoy
are done, geoclue needs looking at (it's assigned, as per Steve's
comment). The MIR team does not need any additional visibility on this
since geoclue has already been demoted to universe.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is a bug assignee.
https://bugs.launchpad.net/bugs/1621216

Title:
  [MIR] geoclue-2.0

Status in geoclue package in Ubuntu:
  New
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in iio-sensor-proxy package in Ubuntu:
  Fix Released

Bug description:
  libqt5positioning5 now recommends geoclue-2.0

  +qtlocation-opensource-src (5.6.0-1) experimental; urgency=medium
  +
  +  [ Lisandro Damián Nicanor Pérez Meyer ]
  +  * New upstream release.
  +- Bump Qt build dependencies.
  +  * Make qtlocation5-examples depend on qml-module-qtpositioning.
  +  * Make libqt5positioning5 recommend geoclue-2.0. It will connect to it by
  +using dbus.

  geoclue-2.0 was previously in main see the MIR for it in bug #1388294.

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

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

[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport

[Frank Heimes]

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssl package in Ubuntu:
  New

Bug description:
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and
  upstream code are not affected ).

  Original LP ticket : 
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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]

** Changed in: nux (Ubuntu)
 Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)

** Changed in: nux (Ubuntu)
Milestone: None => ubuntu-18.04.1

-- 
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 1613267] Re: [MIR] maliit-framework

[Matthias Klose]

no phone and tablet images anymore

** Changed in: maliit-framework (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  [MIR] maliit-framework

Status in maliit-framework package in Ubuntu:
  Won't Fix

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8 and ubuntu-keyboard

  [Security]
   * No known security issues at this time. Additional patches have been added 
to provide enhanced security when running in a Mir based environment by only 
allowing focused applications to access the on-screen keyboard.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Only missing dependencies are gles variants of libqt5gui5-gles and 
libqt5quick5-gles (the non-gles variants are already in main and are the first 
choice for these dependencies)

  [Standards compliance]
   * This package uses qmake. This package doesn't provide a UI itself, this is 
handled via additional plugin packages (such as ubuntu-keyboard), which contain 
translations.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
and tablet images

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

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

[Touch-packages] [Bug 1768379] Re: failed 16.04 LTS -> 18.04 LTS upgrade

[Brian Murray]

** Also affects: python3-defaults (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python3-defaults (Ubuntu)
Milestone: None => ubuntu-18.04.1

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

Title:
  failed 16.04 LTS -> 18.04 LTS upgrade

Status in python3-defaults package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install
  failure:

  Fetched 2,320 MB in 6s (27.8 MB/s)

  Upgrading
  Inhibiting until Ctrl+C is pressed...
  Fetched 0 B in 0s (0 B/s) 

  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
  (Reading database ... 373383 files and directories currently installed.)
  Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ...
  Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  Setting up base-files (10.1ubuntu2) ...
  Installing new version of config file /etc/debian_version ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Updating /etc/profile to current default.
  motd-news.service is a disabled or a static unit, not starting it.
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../debianutils_4.8.4_amd64.deb ...
  Unpacking debianutils (4.8.4) over (4.7) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up debianutils (4.8.4) ...
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ...
  Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up bash (4.4.18-2ubuntu1) ...
  Installing new version of config file /etc/bash.bashrc ...
  Installing new version of config file /etc/skel/.profile ...
  update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide 
/usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
  (Reading database ... 373388 files and directories currently installed.)
  Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ...
  Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ...
  Selecting previously unselected package libcom-err2:amd64.
  Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ...
  Unpacking libcom-err2:amd64 (1.44.1-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu10) ...
  Setting up libcom-err2:amd64 (1.44.1-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu10) ...
  (Reading database ... 373391 files and directories currently installed.)
  Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ...
  Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ...
  Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ...
  Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ...
  Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ...
  Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) 
...
  Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ...
  Unpacking libkrb5-3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ...
  Preparing to unpack .../liblzma5_5.2.2-1.3_amd64.deb ...
  

[Touch-packages] [Bug 1775307] Re: Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * Unattended-upgrades fails to install updates when adjusting
+ candidates is needed.
+ 
+ [Test Case]
+ 
+ Note that only 1.2ubuntu1 is affected. Earlier releases either did not
+ crash or did not adjust candidates due to LP: #1775292. To reproduce the
+ crash Cosmic's u-u 1.2ubuntu1 needs to be installed.
+ 
+  * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
+  * Observe no line with "adjusting candidate version: " or a crash with buggy 
u-u versions
  ...
  adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15
  adjusting candidate version: zfs-test=0.7.5-1ubuntu15
  adjusting candidate version: zfs-zed=0.7.5-1ubuntu15
  adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1928, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1554, in main
  allowed_origins=allowed_origins)
File "/usr/bin/unattended-upgrade", line 122, in __init__
  apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__
  self.open(progress)
File "/usr/bin/unattended-upgrade", line 152, in open
  self.adjust_candidates()
File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates
  for pkgname, candidate in self._get_candidates_to_adjust():
- ValueError: too many values to unpack (expected 2)
+ ValueError: too many values to unpack (expected 2) * Install fixed u-u version
+ 
+  * Run sudo unattended-upgrade --dry-run --verbose --debug
+  * Observe lines "adjusting candidate version: " and no crash
+ 
+ [Regression Potential]
+ 
+  * Unattended-upgrade may crash when adjusting candidates preventing
+ upgrades to be installed

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

Title:
  Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1
  version

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Unattended-upgrades fails to install updates when adjusting
  candidates is needed.

  [Test Case]

  Note that only 1.2ubuntu1 is affected. Earlier releases either did not
  crash or did not adjust candidates due to LP: #1775292. To reproduce
  the crash Cosmic's u-u 1.2ubuntu1 needs to be installed.

   * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
   * Observe no line with "adjusting candidate version: " or a crash with buggy 
u-u versions
  ...
  adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15
  adjusting candidate version: zfs-test=0.7.5-1ubuntu15
  adjusting candidate version: zfs-zed=0.7.5-1ubuntu15
  adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1928, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1554, in main
  allowed_origins=allowed_origins)
File "/usr/bin/unattended-upgrade", line 122, in __init__
  apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__
  self.open(progress)
File "/usr/bin/unattended-upgrade", line 152, in open
  self.adjust_candidates()
File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates
  for pkgname, candidate in self._get_candidates_to_adjust():
  ValueError: too many values to unpack (expected 2) * Install fixed u-u version

   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting candidate version: " and no crash

  [Regression Potential]

   * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

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

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

[Touch-packages] [Bug 1770965] Re: After upgrade and reboot, the lightdm display manager does not start

[Brian Murray]

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

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

Title:
  After upgrade and reboot, the lightdm display manager does not start

Status in lightdm package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  Upon the upgrade, lightdm-kde-greeter was removed as it has become
  obsolete. That leaves the user with a system that hangs.

  I rebooted using system-recovery, and installed lightdm-gtk-greeter
  using aptitude. However, this greeter was not enabled in lightdm.conf.
  Also, the greeter was not configured with the background image for
  this release. I had to do these actions manually. Only then did
  lightdm start properly and with a nice background.

  For most users this problem will leave the system unusable forever,
  and should therefore be avoided. The obsolete greeter should be
  replaced with a suitable greeter.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  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
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Sun May 13 16:30:51 2018
  InstallationDate: Installed on 2013-02-05 (1922 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptlog:
   Log time: 2018-05-13 12:28:57.668250
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

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

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

[Touch-packages] [Bug 1775292] Re: Unattended-upgrades stopped adjusting candidates in 1.1

[Balint Reczey]

** Description changed:

  [Impact]
  
-  * Unattended-upgrades may fail to install an update when the highest
+  * Unattended-upgrades may fail to install an update when the highest
  version of a package to be updated exists in an origin u-u is not
  allowed to pull packages from.
  
  [Test Case]
  
-  * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
-  * Observe no line with "adjusting candidate version: " with buggy u-u version
-  * Install fixed u-u version
-  * Run sudo unattended-upgrade --dry-run --verbose --debug
-  * Observe no line with "adjusting candidate version: " with buggy u-u version
+  * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
+  * Observe no line with "adjusting candidate version: " with buggy u-u version
+  * Install fixed u-u version
+  * Run sudo unattended-upgrade --dry-run --verbose --debug
+  * Observe lines "adjusting candidate version: "
  
  [Regression Potential]
  
-  * Unattended-upgrade may crash when adjusting candidates preventing
+  * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

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

Title:
  Unattended-upgrades stopped adjusting candidates in 1.1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Unattended-upgrades may fail to install an update when the highest
  version of a package to be updated exists in an origin u-u is not
  allowed to pull packages from.

  [Test Case]

   * Run sudo apt update && sudo unattended-upgrade --dry-run --verbose --debug
   * Observe no line with "adjusting candidate version: " with buggy u-u version
   * Install fixed u-u version
   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting candidate version: "

  [Regression Potential]

   * Unattended-upgrade may crash when adjusting candidates preventing
  upgrades to be installed

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

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

[Touch-packages] [Bug 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

[Brian Murray]

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: In Progress => Invalid

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Status: In Progress => Invalid

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

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in xorg source package in Bionic:
  Fix Released

Bug description:
  [Testcase]

  1. Launch xenial lxd container
  2. install x11-common upstart
  3. do-release-upgrade to bionic
  4. Upgrade to bionic removes upstart
  5. upgrade to new x11-common, make sure the upstart snippets are gone from 
disk: /etc/X11/Xsession.d/00upstart
  /etc/X11/Xsession.d/99upstart
  6. for the new release-upgrader, check that upstart is purged, if user 
selects to remove packages at the end of the do-release-upgrade.

  
  After an upgrade from Xenial to Bionic the session fails to start and returns 
immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

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

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

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Brian Murray]

** Changed in: systemd-shim (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: systemd-shim (Ubuntu Bionic)
Milestone: None => ubuntu-18.04.1

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd-shim source package in Bionic:
  New

Bug description:
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1488425] Re: [MIR] ubuntu-download-manager

[Mathieu Trudel-Lapierre]

Unsubscribing ~ubuntu-mir; this package was promoted, and later removed
from the archive.

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

Title:
  [MIR] ubuntu-download-manager

Status in Canonical System Image:
  In Progress
Status in ubuntu-download-manager package in Ubuntu:
  Fix Released

Bug description:
  webbrowser-app (in main) currently has a non-explicit runtime dependency on 
ubuntu-download-manager, which is in universe.
  This has been working until now because the desktop version of the app 
doesn’t make use of the QML API for the download manager, only the version for 
touch devices does (and ubuntu-download-manager is part of the touch seed).
  With convergence in mind, the desktop version needs to start using that QML 
API, so the runtime dependency needs to be made explicit. Hence the need for 
ubuntu-download-manager to be included in main.
  It is likely that other applications will have the same kind of requirements 
in the near future too.

  ubuntu-download-manager is actively being developed and maintained,
  upstream tracks their bugs at
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/.

  All its build and runtime dependencies are already in main.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488425/+subscriptions

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

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Brian Murray]

** Tags added: xenial2bionic

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd-shim source package in Bionic:
  New

Bug description:
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Zero]

Not sure if this is the same problem. Everything was working perfectly
until the massive update that came out last night. Now cannot find
internal Atheros BT adapter in Blueman-applet. It appears to allow me to
enable BT. Lights on but no one home. Linux firmware looks borked.

user@UX32VD:~$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
3: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no


user@UX32VD:~$ dmesg | grep Blue
[2.999406] Bluetooth: Core ver 2.21
[2.999422] Bluetooth: HCI device and connection manager initialized
[2.999425] Bluetooth: HCI socket layer initialized
[2.999428] Bluetooth: L2CAP socket layer initialized
[2.999434] Bluetooth: SCO socket layer initialized
[3.020951] Bluetooth: hci0: don't support firmware rome 0x1102
[3.028458] Bluetooth: hci0: don't support firmware rome 0x1102
[4.600699] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[4.600704] Bluetooth: BNEP filters: protocol multicast
[4.600709] Bluetooth: BNEP socket layer initialized


user@UX32VD:~$ lspci -knn | grep Net -A2; lsusb 
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network 
Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-size Mini 
PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
Bus 002 Device 004: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 
4.0
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS 
webcam
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card 
Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if 

[Touch-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer details to help improving Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.19

---
ubuntu-release-upgrader (1:18.04.19) bionic; urgency=medium

  * Add upgrade telemetry information (LP: #1755456)
  * Updated translations

 -- Didier Roche   Thu, 03 May 2018 15:55:34 +0200

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [ffe] Optional recording/sending of installer details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Released

Bug description:
  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.

  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's
  review and approval before sending.

  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade
  without this ubuntu-release-upgrade versinon)

  [Impact]
   * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
   * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
   * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
   * The telemetry is reported by all existing UI.
   * What we send is:
 - From (distro we ugprade from)
 - Type of installer (GTK, KDE, non interactive, text…)
 - If third party ressources were used (but not the list of those external 
repos)
 - Original installation media
 - Stages of installation indexed by their relative time duration

  
  [Test Case]
   * Install ubuntu-release-upgrade on an artful machine
   * Run an upgrade from artful to bionic
   * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.

  [Regression Potential]

   * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
   * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.

  ---

  The topic has been discussed on the ubuntu-devel@ list, see
  https://lists.ubuntu.com/archives/ubuntu-
  devel/2018-February/040139.html

  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review those informations
  - the desktop settings should have a control to change the option later on

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

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

[Touch-packages] [Bug 1755456] Update Released

[Łukasz Zemczak]

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

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

Title:
  [ffe] Optional recording/sending of installer details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Released

Bug description:
  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.

  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's
  review and approval before sending.

  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade
  without this ubuntu-release-upgrade versinon)

  [Impact]
   * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
   * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
   * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
   * The telemetry is reported by all existing UI.
   * What we send is:
 - From (distro we ugprade from)
 - Type of installer (GTK, KDE, non interactive, text…)
 - If third party ressources were used (but not the list of those external 
repos)
 - Original installation media
 - Stages of installation indexed by their relative time duration

  
  [Test Case]
   * Install ubuntu-release-upgrade on an artful machine
   * Run an upgrade from artful to bionic
   * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.

  [Regression Potential]

   * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
   * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.

  ---

  The topic has been discussed on the ubuntu-devel@ list, see
  https://lists.ubuntu.com/archives/ubuntu-
  devel/2018-February/040139.html

  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review those informations
  - the desktop settings should have a control to change the option later on

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

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

[Touch-packages] [Bug 1773012] Re: kernel bugs in bionic are reported about linux-signed and package hook doesn't run

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.9-0ubuntu7.2

---
apport (2.20.9-0ubuntu7.2) bionic; urgency=medium

  * apport/ui.py: Include ProblemType in reports which are updated as
package hooks may expect the report to have a ProblemType. (LP: #1766794)
  * test/test_ui.py: modify run_crash_kernel test to account for the fact
that linux-image-$kvers-$flavor is now built from the linux-signed
source package on amd64 and ppc64el. (LP: #1766740)
  * data/general-hooks/ubuntu.py: Don't display a messy error if python or
python3 is not installed. (LP: #1769262)
  * debian/apport.links: source_linux-signed.py -> source_linux.py package
hook (LP: #1773012)
  * data/package-hooks/source_linux.py: Redirect bugs filed about the
linux-signed source package to linux. (LP: #1773012)

 -- Brian Murray   Wed, 30 May 2018 15:19:49 -0700

** Changed in: apport (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  kernel bugs in bionic are reported about linux-signed and package hook
  doesn't run

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  During the development of bionic the linux-image-$kvers-$flavor
  package was changed from being built from the linux package to the
  linux-signed package, however apport was not updated in bionic for
  this change. Subsequently, the apport package hook for linux doesn't
  run for linux-signed bug reports. Additionally, the kernel team would
  like reports about linux-signed redirected to the linux package.

  Test Case
  -
  1) In a terminal run 'ubuntu-bug linux-image-4.15.0-20-generic'
  2) In the crash report dialog observe the following:
    a) The source package is linux-signed
    b) ProcFB is not included

  With the version of the package from -proposed the source package will
  be linux and ProcFB will be included. Also test 'ubuntu-bug linux-
  image-generic' to and check to see that the crash report contains the
  same information as above.

  Regression Potential
  
  The code that redirects bugs from linux-signed to linux was written and that 
change, if it were bad, could negatively affect bugs reported about the 
linux-meta package. So it'd be good to test that process by running 'ubuntu-bug 
linux-image-generic' with the -proposed version of the package.

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

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

[Touch-packages] [Bug 1766794] Update Released

[Łukasz Zemczak]

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

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

Title:
  apport-collect doesn't create a ProblemType in the report

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  Running 'sudo apport-collect BUGID' on 18.04 and then selecting 'V:
  View report' results in Tracebacks.

  [Test Case]
  1) ssh to a system running bionic
  2) run apport-collect 1766787
  3) say yes that you want to update a bug report that isn't yours
  4) Choose to view the report
  5) Observe the following Traceback

  ERROR: hook /usr/share/apport/general-hooks/generic.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/generic.py", line 90, in add_info
  if report['ProblemType'] == 'Crash':
File "/usr/lib/python3.6/collections/__init__.py", line 991, in __getitem__
  raise KeyError(key)
  KeyError: 'ProblemType'

  With the version of the package from -proposed you will not see the
  Traceback.

  [Regression Potential]
  The change is just to stop removing the ProblemType from the created report 
so there really isn't a chance of a regression.

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

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

[Touch-packages] [Bug 1773012] Update Released

[Łukasz Zemczak]

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

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

Title:
  kernel bugs in bionic are reported about linux-signed and package hook
  doesn't run

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  During the development of bionic the linux-image-$kvers-$flavor
  package was changed from being built from the linux package to the
  linux-signed package, however apport was not updated in bionic for
  this change. Subsequently, the apport package hook for linux doesn't
  run for linux-signed bug reports. Additionally, the kernel team would
  like reports about linux-signed redirected to the linux package.

  Test Case
  -
  1) In a terminal run 'ubuntu-bug linux-image-4.15.0-20-generic'
  2) In the crash report dialog observe the following:
    a) The source package is linux-signed
    b) ProcFB is not included

  With the version of the package from -proposed the source package will
  be linux and ProcFB will be included. Also test 'ubuntu-bug linux-
  image-generic' to and check to see that the crash report contains the
  same information as above.

  Regression Potential
  
  The code that redirects bugs from linux-signed to linux was written and that 
change, if it were bad, could negatively affect bugs reported about the 
linux-meta package. So it'd be good to test that process by running 'ubuntu-bug 
linux-image-generic' with the -proposed version of the package.

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

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

[Touch-packages] [Bug 1766740] Re: apport autopkgtest regression due to kernel packaging changes

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.9-0ubuntu7.2

---
apport (2.20.9-0ubuntu7.2) bionic; urgency=medium

  * apport/ui.py: Include ProblemType in reports which are updated as
package hooks may expect the report to have a ProblemType. (LP: #1766794)
  * test/test_ui.py: modify run_crash_kernel test to account for the fact
that linux-image-$kvers-$flavor is now built from the linux-signed
source package on amd64 and ppc64el. (LP: #1766740)
  * data/general-hooks/ubuntu.py: Don't display a messy error if python or
python3 is not installed. (LP: #1769262)
  * debian/apport.links: source_linux-signed.py -> source_linux.py package
hook (LP: #1773012)
  * data/package-hooks/source_linux.py: Redirect bugs filed about the
linux-signed source package to linux. (LP: #1773012)

 -- Brian Murray   Wed, 30 May 2018 15:19:49 -0700

** Changed in: apport (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  apport autopkgtest regression due to kernel packaging changes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  In bionic, linux-image-$kvers-$flavor is now built from the linux-signed 
source package on amd64, not from the linux source package.  This now causes a 
test to fail in the apport test suite:

  [...]
  ==
  FAIL: test_run_crash_kernel (__main__.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
    File "./test_ui.py", line 1305, in test_run_crash_kernel
  self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % 
se
  lf.ui.crashdb.latest_id())
  AssertionError: 'http://linux-signed.bugs.example.com/5' != 
'http://linux.bugs.e
  xample.com/5'
  - http://linux-signed.bugs.example.com/5
  ? ---
  + http://linux.bugs.example.com/5

  --
  Ran 70 tests in 79.815s

  FAILED (failures=1)
  [...]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz)

  This test needs to be fixed to know about the packaging change.

  Note that this packaging change is expected to soon be SRUed back to
  all Ubuntu releases, so apport's testsuite change should also be
  SRUed.

  [Test case]
  This passes if the autopkgtests pass.

  [Regression potential]
  The test could be changed to pass while leaving underlying issues in the 
code.  This has probably not happened here.

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

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

[Touch-packages] [Bug 1769262] Update Released

[Łukasz Zemczak]

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

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

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launch update-manager
  2) kill update-manager
  3) view the crash report

  With the version of apport in the archive you will see messy
  PythonDetails like below. With the version of apport from -proposed
  you will instead see:

  PythonDetails: N/A

  [Regression Potential]
  The fix for this also modified the code which creates Python3Details so we 
should ensure that Python3Details is not broken.

  Original Description
  
  In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:

  PythonDetails: /root/Error: command ['which', 'python'] failed with
  exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

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

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

[Touch-packages] [Bug 1769262] Re: PythonDetails contains an error message if python not installed

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.9-0ubuntu7.2

---
apport (2.20.9-0ubuntu7.2) bionic; urgency=medium

  * apport/ui.py: Include ProblemType in reports which are updated as
package hooks may expect the report to have a ProblemType. (LP: #1766794)
  * test/test_ui.py: modify run_crash_kernel test to account for the fact
that linux-image-$kvers-$flavor is now built from the linux-signed
source package on amd64 and ppc64el. (LP: #1766740)
  * data/general-hooks/ubuntu.py: Don't display a messy error if python or
python3 is not installed. (LP: #1769262)
  * debian/apport.links: source_linux-signed.py -> source_linux.py package
hook (LP: #1773012)
  * data/package-hooks/source_linux.py: Redirect bugs filed about the
linux-signed source package to linux. (LP: #1773012)

 -- Brian Murray   Wed, 30 May 2018 15:19:49 -0700

** Changed in: apport (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launch update-manager
  2) kill update-manager
  3) view the crash report

  With the version of apport in the archive you will see messy
  PythonDetails like below. With the version of apport from -proposed
  you will instead see:

  PythonDetails: N/A

  [Regression Potential]
  The fix for this also modified the code which creates Python3Details so we 
should ensure that Python3Details is not broken.

  Original Description
  
  In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:

  PythonDetails: /root/Error: command ['which', 'python'] failed with
  exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

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

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

[Touch-packages] [Bug 1766740] Update Released

[Łukasz Zemczak]

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

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

Title:
  apport autopkgtest regression due to kernel packaging changes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  In bionic, linux-image-$kvers-$flavor is now built from the linux-signed 
source package on amd64, not from the linux source package.  This now causes a 
test to fail in the apport test suite:

  [...]
  ==
  FAIL: test_run_crash_kernel (__main__.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
    File "./test_ui.py", line 1305, in test_run_crash_kernel
  self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % 
se
  lf.ui.crashdb.latest_id())
  AssertionError: 'http://linux-signed.bugs.example.com/5' != 
'http://linux.bugs.e
  xample.com/5'
  - http://linux-signed.bugs.example.com/5
  ? ---
  + http://linux.bugs.example.com/5

  --
  Ran 70 tests in 79.815s

  FAILED (failures=1)
  [...]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz)

  This test needs to be fixed to know about the packaging change.

  Note that this packaging change is expected to soon be SRUed back to
  all Ubuntu releases, so apport's testsuite change should also be
  SRUed.

  [Test case]
  This passes if the autopkgtests pass.

  [Regression potential]
  The test could be changed to pass while leaving underlying issues in the 
code.  This has probably not happened here.

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

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

[Touch-packages] [Bug 1766794] Re: apport-collect doesn't create a ProblemType in the report

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.9-0ubuntu7.2

---
apport (2.20.9-0ubuntu7.2) bionic; urgency=medium

  * apport/ui.py: Include ProblemType in reports which are updated as
package hooks may expect the report to have a ProblemType. (LP: #1766794)
  * test/test_ui.py: modify run_crash_kernel test to account for the fact
that linux-image-$kvers-$flavor is now built from the linux-signed
source package on amd64 and ppc64el. (LP: #1766740)
  * data/general-hooks/ubuntu.py: Don't display a messy error if python or
python3 is not installed. (LP: #1769262)
  * debian/apport.links: source_linux-signed.py -> source_linux.py package
hook (LP: #1773012)
  * data/package-hooks/source_linux.py: Redirect bugs filed about the
linux-signed source package to linux. (LP: #1773012)

 -- Brian Murray   Wed, 30 May 2018 15:19:49 -0700

** Changed in: apport (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  apport-collect doesn't create a ProblemType in the report

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released

Bug description:
  Running 'sudo apport-collect BUGID' on 18.04 and then selecting 'V:
  View report' results in Tracebacks.

  [Test Case]
  1) ssh to a system running bionic
  2) run apport-collect 1766787
  3) say yes that you want to update a bug report that isn't yours
  4) Choose to view the report
  5) Observe the following Traceback

  ERROR: hook /usr/share/apport/general-hooks/generic.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/generic.py", line 90, in add_info
  if report['ProblemType'] == 'Crash':
File "/usr/lib/python3.6/collections/__init__.py", line 991, in __getitem__
  raise KeyError(key)
  KeyError: 'ProblemType'

  With the version of the package from -proposed you will not see the
  Traceback.

  [Regression Potential]
  The change is just to stop removing the ProblemType from the created report 
so there really isn't a chance of a regression.

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

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

[Touch-packages] [Bug 1775566] Re: networkd not applying config - missing events?

[ Christian Ehrhardt ]

I identified that systems I spawn as q35 right away work.
Only those where the initial cloud init runs as i440fx and then I change them 
to q35 are affected.

I compared configurations and eventually had even my converted instance
running, to the point that it was hard to tell why.

I found that the root cause is this difference in config:
BAD:
network:
version: 2
ethernets:
enp3:
dhcp4: true
match:
macaddress: 52:54:00:ba:23:d6
set-name: enp3

GOOD:
network:
version: 2
ethernets:
enp1s0:
dhcp4: true
match:
macaddress: 52:54:00:ba:23:d6
set-name: enp1s0

Now yes, the device is enp1s0 at the moment:
$ dmesg | grep enp
[0.898280] virtio_net virtio0 enp1s0: renamed from eth0

But according to the netplan spec this should not matter right?
It has a match so the upper name is just an id.
And set-name can be whatever we want.

Bad case networkd files:
$ tail /run/systemd/network/10-netplan-enp3.*
==> /run/systemd/network/10-netplan-enp3.link <==
[Match]
MACAddress=52:54:00:ba:23:d6

[Link]
Name=enp3
WakeOnLan=off

==> /run/systemd/network/10-netplan-enp3.network <==
[Match]
MACAddress=52:54:00:ba:23:d6
Name=enp3

[Network]
DHCP=ipv4

[DHCP]
UseMTU=true
RouteMetric=100


Good case networkd files:
$ tail /run/systemd/network/10-netplan-enp1s0.*
==> /run/systemd/network/10-netplan-enp1s0.link <==
[Match]
MACAddress=52:54:00:ba:23:d6

[Link]
Name=enp1s0
WakeOnLan=off

==> /run/systemd/network/10-netplan-enp1s0.network <==
[Match]
MACAddress=52:54:00:ba:23:d6
Name=enp1s0

[Network]
DHCP=ipv4

[DHCP]
UseMTU=true
RouteMetric=100

Cloud init generating them right the first time makes it work.
If we go in with the old names it fails, while according to the man page it 
should not.
So is it an issue in netplan or more in networkd I'm not sure - leaving it to 
the owners of the packages.

** Changed in: netplan.io (Ubuntu)
   Status: Invalid => 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/1775566

Title:
  networkd not applying config - missing events?

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  TL;DR:
  - networkd config written by netplan
  - it seems we can eliminate netplan from this and still have the issue
  - networkd seems to miss the event of the devices and therefore consider them 
unmanaged
  - rebinding them makes it work
  - the way to trigger this I found so far are q35 KVM guests (PCIe), but 
there might be more

  ---

  I miss some hidden trigger of "netplan apply" to understand the
  following case.

  I have kvm guests, you can spawn your own one to reproduce via:
   $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
   $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
     virsh start bionic-netplan

  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
   ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:68:4b:62

  I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
     If there are match: rules, then the ID field is a purely opaque name which 
is only being used
     for references from definitions of compound devices in the config

  And I found it works just fine when I run "sudo netplan apply".

  This was odd, so to summarize up to here:
  - PCIe based virt guest
  - netplan egenrated config not working after (re)boot
  - "netplan apply" makes it working

  I disabled any cloud init things as recommended by the comment
    /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
    network: {config: disabled}
  So that I can rely on my netplan yaml to stay as is.
  I tried various things but so far can't find what magic "netplan apply" does 
which is missing to my boot.

  I checked after reboot the devices are considered unmanaged by networkctl
  $ networkctl list
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier unmanaged
    2 enp0s3   ether  off 

[Touch-packages] [Bug 1775566] Re: networkd not applying config - missing events?

[ Christian Ehrhardt ]

Since we ruled out netplan, mark it invalid.
Focus on systemd-networkd for now.

** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

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

Title:
  networkd not applying config - missing events?

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  TL;DR:
  - networkd config written by netplan
  - it seems we can eliminate netplan from this and still have the issue
  - networkd seems to miss the event of the devices and therefore consider them 
unmanaged
  - rebinding them makes it work
  - the way to trigger this I found so far are q35 KVM guests (PCIe), but 
there might be more

  ---

  I miss some hidden trigger of "netplan apply" to understand the
  following case.

  I have kvm guests, you can spawn your own one to reproduce via:
   $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
   $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
     virsh start bionic-netplan

  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
   ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:68:4b:62

  I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
     If there are match: rules, then the ID field is a purely opaque name which 
is only being used
     for references from definitions of compound devices in the config

  And I found it works just fine when I run "sudo netplan apply".

  This was odd, so to summarize up to here:
  - PCIe based virt guest
  - netplan egenrated config not working after (re)boot
  - "netplan apply" makes it working

  I disabled any cloud init things as recommended by the comment
    /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
    network: {config: disabled}
  So that I can rely on my netplan yaml to stay as is.
  I tried various things but so far can't find what magic "netplan apply" does 
which is missing to my boot.

  I checked after reboot the devices are considered unmanaged by networkctl
  $ networkctl list
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier unmanaged
    2 enp0s3   ether  off unmanaged

  But the config was generated:
  $ ll /run/systemd/network/
  total 32
  drwxr-xr-x  2 root root 200 Jun  7 09:02 ./
  drwxr-xr-x 22 root root 500 Jun  7 09:02 ../
  -rw-r--r--  1 root root  69 Jun  7 09:02 10-netplan-enp0s3.link
  -rw-r--r--  1 root root 104 Jun  7 09:02 10-netplan-enp0s3.network

  I checked the log and saw that apply restarts networkd.
  So I thought might just restart networkd, so I ran
   $ sudo systemctl restart systemd-networkd.service
  But things stayed as-is without the config being picked up.

  With some nice discussion and help on IRC I also tried to disable netplan and 
check if this is networkd only.
  # make this static networkd
  $ sudo cp /run/systemd/network/10-netplan-enp0s* /etc/systemd/network/
  # no netplan config
  $ sudo mv /etc/netplan/* /root

  That was supposed to show if networkd itself (or its config files) had issues.
  And with that it still did not work, so is the error in networkd instead?
  If so what magic thing does "netplan apply" do to fix it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1775566/+subscriptions

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

[Touch-packages] [Bug 1775566] Re: networkd not applying config - missing events?

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  networkd not applying config - missing events?

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  TL;DR:
  - networkd config written by netplan
  - it seems we can eliminate netplan from this and still have the issue
  - networkd seems to miss the event of the devices and therefore consider them 
unmanaged
  - rebinding them makes it work
  - the way to trigger this I found so far are q35 KVM guests (PCIe), but 
there might be more

  ---

  I miss some hidden trigger of "netplan apply" to understand the
  following case.

  I have kvm guests, you can spawn your own one to reproduce via:
   $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
   $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
     virsh start bionic-netplan

  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
   ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:68:4b:62

  I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
     If there are match: rules, then the ID field is a purely opaque name which 
is only being used
     for references from definitions of compound devices in the config

  And I found it works just fine when I run "sudo netplan apply".

  This was odd, so to summarize up to here:
  - PCIe based virt guest
  - netplan egenrated config not working after (re)boot
  - "netplan apply" makes it working

  I disabled any cloud init things as recommended by the comment
    /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
    network: {config: disabled}
  So that I can rely on my netplan yaml to stay as is.
  I tried various things but so far can't find what magic "netplan apply" does 
which is missing to my boot.

  I checked after reboot the devices are considered unmanaged by networkctl
  $ networkctl list
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier unmanaged
    2 enp0s3   ether  off unmanaged

  But the config was generated:
  $ ll /run/systemd/network/
  total 32
  drwxr-xr-x  2 root root 200 Jun  7 09:02 ./
  drwxr-xr-x 22 root root 500 Jun  7 09:02 ../
  -rw-r--r--  1 root root  69 Jun  7 09:02 10-netplan-enp0s3.link
  -rw-r--r--  1 root root 104 Jun  7 09:02 10-netplan-enp0s3.network

  I checked the log and saw that apply restarts networkd.
  So I thought might just restart networkd, so I ran
   $ sudo systemctl restart systemd-networkd.service
  But things stayed as-is without the config being picked up.

  With some nice discussion and help on IRC I also tried to disable netplan and 
check if this is networkd only.
  # make this static networkd
  $ sudo cp /run/systemd/network/10-netplan-enp0s* /etc/systemd/network/
  # no netplan config
  $ sudo mv /etc/netplan/* /root

  That was supposed to show if networkd itself (or its config files) had issues.
  And with that it still did not work, so is the error in networkd instead?
  If so what magic thing does "netplan apply" do to fix it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1775566/+subscriptions

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

[Touch-packages] [Bug 1775593] [NEW] X server crashes with SIGBUS when resuming from suspend

[Paulo Marcel Coelho Aragão]

Public bug reported:

Every night I suspend my laptop and resume it in the morning. At least
once a week, the X server crashes with SIGBUS when resuming from
suspend.

I scoured systemd journals and all logs under /var/log, and this was the
only suspicious message I found:

[ 59358.134] (EE) /dev/dri/card0: failed to set DRM interface version
1.4: Permission denied

As my graphics card uses driver i915, I installed xserver-xorg-video-
intel-dbg but couldn't find any package with debugging symbols for
xserver-xorg-core, so running 'sudo gdb --core=/core' only yielded this:

Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGBUS, Bus error.
#0  0x5631c45681f1 in ?? ()
[Current thread is 1 (LWP 1016)]
(gdb) bt
#0  0x5631c45681f1 in ?? ()
#1  0x0001 in ?? ()
#2  0x5631c5a03350 in ?? ()
#3  0x0001 in ?? ()
#4  0x5631c4596ec5 in ?? ()
#5  0x7f5f0974e2a0 in ?? ()
#6  0x7f5f093e5977 in ?? ()
#7  0x in ?? ()

I'm attaching apport's crash report.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Jun  7 08:56:01 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04b0]
InstallationDate: Installed on 2018-04-28 (39 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Inspiron N5110
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash 
systemd.legacy_systemd_cgroup_controller=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 08FDW5
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "apport crash report when X crashed with SIGBUS"
   
https://bugs.launchpad.net/bugs/1775593/+attachment/5149744/+files/_usr_lib_xorg_Xorg.0.crash

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

Title:
  X server crashes with SIGBUS when resuming from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Every night I suspend my laptop and resume it in the morning. At least
  once a week, the X server crashes with SIGBUS when resuming from
  suspend.

  I scoured systemd journals and all logs under /var/log, and this was
  the only suspicious message I found:

  [ 59358.134] (EE) /dev/dri/card0: failed to set DRM interface version
  1.4: Permission denied

  As my graphics card uses driver i915, I installed xserver-xorg-video-
  intel-dbg but couldn't find any package with debugging symbols for
  xserver-xorg-core, so running 'sudo gdb --core=/core' only yielded
  this:

  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGBUS, Bus error.
  #0  0x5631c45681f1 in ?? ()
  [Current thread is 1 (LWP 1016)]
  (gdb) bt
  #0  0x5631c45681f1 in ?? ()
  #1  0x0001 in ?? ()
  #2  0x5631c5a03350 in ?? ()
  #3  0x0001 in ?? ()
  #4  0x5631c4596ec5 in ?? ()
  #5  0x7f5f0974e2a0 in ?? ()
  #6  

[Touch-packages] [Bug 1775566] Re: networkd not applying config - missing events?

[ Christian Ehrhardt ]

I thought I might have oversimplified PCIe setup for q35 too much when I
tried to compare to i440fx (where this works AFAICS).

But  adding libvirts default devices for this case did not change anything.
For documentation purposes still here the difference how to add those as 
attachment.

The easiest way thou is to let libvirt do all that.
To do so copy the uvtool template
 $ cp /usr/share/uvtool/libvirt/template.xml q35-template.xml
 # Then edit the type line to be
 hvm

When spawning with uvtool and this template you'll get the full proper defaults.
 $ uvt-kvm create --template /home/paelzer/q35-template.xml --password ubuntu 
bionic-q35-normal-extended arch=amd64 release=bionic label=daily

For this bug here it makes no difference, with the full set of pci roots and 
stuff available the event is still missed.
(the extended setup is required for e..g hotplugging)

** Patch added: "diff of trivial and extended q35 setup"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1775566/+attachment/5149743/+files/extend-q35-pcie.diff

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

Title:
  networkd not applying config - missing events?

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  TL;DR:
  - networkd config written by netplan
  - it seems we can eliminate netplan from this and still have the issue
  - networkd seems to miss the event of the devices and therefore consider them 
unmanaged
  - rebinding them makes it work
  - the way to trigger this I found so far are q35 KVM guests (PCIe), but 
there might be more

  ---

  I miss some hidden trigger of "netplan apply" to understand the
  following case.

  I have kvm guests, you can spawn your own one to reproduce via:
   $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
   $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
     virsh start bionic-netplan

  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
   ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:68:4b:62

  I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
     If there are match: rules, then the ID field is a purely opaque name which 
is only being used
     for references from definitions of compound devices in the config

  And I found it works just fine when I run "sudo netplan apply".

  This was odd, so to summarize up to here:
  - PCIe based virt guest
  - netplan egenrated config not working after (re)boot
  - "netplan apply" makes it working

  I disabled any cloud init things as recommended by the comment
    /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
    network: {config: disabled}
  So that I can rely on my netplan yaml to stay as is.
  I tried various things but so far can't find what magic "netplan apply" does 
which is missing to my boot.

  I checked after reboot the devices are considered unmanaged by networkctl
  $ networkctl list
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier unmanaged
    2 enp0s3   ether  off unmanaged

  But the config was generated:
  $ ll /run/systemd/network/
  total 32
  drwxr-xr-x  2 root root 200 Jun  7 09:02 ./
  drwxr-xr-x 22 root root 500 Jun  7 09:02 ../
  -rw-r--r--  1 root root  69 Jun  7 09:02 10-netplan-enp0s3.link
  -rw-r--r--  1 root root 104 Jun  7 09:02 10-netplan-enp0s3.network

  I checked the log and saw that apply restarts networkd.
  So I thought might just restart networkd, so I ran
   $ sudo systemctl restart systemd-networkd.service
  But things stayed as-is without the config being picked up.

  With some nice discussion and help on IRC I also tried to disable netplan and 
check if this is networkd only.
  # make this static networkd
  $ sudo cp /run/systemd/network/10-netplan-enp0s* /etc/systemd/network/
  # no netplan config
  $ sudo mv /etc/netplan/* /root

  That was supposed to show if networkd itself (or its config files) had issues.
  And with that it still did not work, so is the error in networkd 

[Touch-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer details to help improving Ubuntu

[Didier Roche]

Done upgrade testing, and everything is as expected.

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

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

Title:
  [ffe] Optional recording/sending of installer details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Committed

Bug description:
  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.

  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's
  review and approval before sending.

  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade
  without this ubuntu-release-upgrade versinon)

  [Impact]
   * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
   * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
   * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
   * The telemetry is reported by all existing UI.
   * What we send is:
 - From (distro we ugprade from)
 - Type of installer (GTK, KDE, non interactive, text…)
 - If third party ressources were used (but not the list of those external 
repos)
 - Original installation media
 - Stages of installation indexed by their relative time duration

  
  [Test Case]
   * Install ubuntu-release-upgrade on an artful machine
   * Run an upgrade from artful to bionic
   * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.

  [Regression Potential]

   * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
   * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.

  ---

  The topic has been discussed on the ubuntu-devel@ list, see
  https://lists.ubuntu.com/archives/ubuntu-
  devel/2018-February/040139.html

  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review those informations
  - the desktop settings should have a control to change the option later on

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

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

[Touch-packages] [Bug 1775566] Re: networkd not applying config written by netplan on boot in q35 (PCIe) KVM guests

[ Christian Ehrhardt ]

Even "netplan apply" with NO yaml file fixes it.
So running in the static networkd config (with the files I copied formerly 
created by netplan as outlied above).

Then with debug enabled it does:
$ networkctl list
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 enp0s3   ether  off unmanaged 

$ sudo netplan --debug apply
DEBUG:no netplan generated networkd configuration exists
DEBUG:no netplan generated NM configuration exists
DEBUG:replug enp0s3: unbinding virtio0 from /sys/bus/virtio/drivers/virtio_net
DEBUG:replug enp0s3: rebinding virtio0 to /sys/bus/virtio/drivers/virtio_net

$ networkctl list
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  8 enp3 ether  routableconfigured


So I did after a reboot:
echo virtio0 | sudo tee /sys/bus/virtio/drivers/virtio_net/virtio0/driver/unbind
echo virtio0 | sudo tee /sys/bus/virtio/drivers/virtio_net/bind

$ networkctl list
IDX LINK TYPE   OPERATIONAL SETUP 
  6 enp3 ether  routableconfigured

So it is working after the replug - adn this replug was the magic done by 
"netplan apply".
Now why this fails with just a static networkd config - I don't know.
But I'd say it is a networkd bug right?

The former event existed on boot
[0.726055] virtio_net virtio0 enp0s3: renamed from eth0
This is the one networkd should have picked up.
[  481.972268] virtio_net virtio0 enp3: renamed from eth0
[  481.983710] IPv6: ADDRCONF(NETDEV_UP): enp3: link is not ready
[  482.976135] IPv6: ADDRCONF(NETDEV_CHANGE): enp3: link becomes ready

I don't know where/how to adress this further, but I hope the repro and
debug helps to fix this.

** Summary changed:

- networkd not applying config written by netplan on boot in q35 (PCIe) KVM 
guests
+ networkd not applying config - missing events?

** Description changed:

  Hi,
- I miss some hidden trigger of "netplan apply" to understand the following 
case.
+ 
+ TL;DR:
+ - networkd config written by netplan
+ - it seems we can eliminate netplan from this and still have the issue
+ - networkd seems to miss the event of the devices and therefore consider them 
unmanaged
+ - rebinding them makes it work
+ - the way to trigger this I found so far are q35 KVM guests (PCIe), but 
+   there might be more
+ 
+ ---
+ 
+ I miss some hidden trigger of "netplan apply" to understand the
+ following case.
  
  I have kvm guests, you can spawn your own one to reproduce via:
-  $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
-  $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily
+  $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
+  $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily
  
  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
-virsh start bionic-netplan
+    virsh start bionic-netplan
  
  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.
  
  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
-  ethernets:
- ens3:
- dhcp4: true
- match:
- macaddress: 52:54:00:68:4b:62
+  ethernets:
+ ens3:
+ dhcp4: true
+ match:
+ macaddress: 52:54:00:68:4b:62
  
  I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
-If there are match: rules, then the ID field is a purely opaque name which 
is only being used 
-for references from definitions of compound devices in the config
+    If there are match: rules, then the ID field is a purely opaque name which 
is only being used
+    for references from definitions of compound devices in the config
  
  And I found it works just fine when I run "sudo netplan apply".
- 
  
  This was odd, so to summarize up to here:
  - PCIe based virt guest
  - netplan egenrated config not working after (re)boot
  - "netplan apply" makes it working
  
- 
  I disabled any cloud init things as recommended by the comment
-   /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-   network: {config: disabled}
+   /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
+   network: {config: disabled}

[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From sankar...@in.ibm.com 2018-06-07 06:47 EDT---
Hi there,

Now Network Manager(NM) is able to manage the devices with the following 
changes.
Change the contents of the file 
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf to

[keyfile]
unmanaged-devices=none


from

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan


and restart NM(service network-manager restart) did the trick.

Why it didn't work earlier:
We added interfaces to the file /etc/network/interfaces.
So NM is not able to manage the interfaces updated in the said file.

When we removed the interfaces from the above file, It started working.

Is this approach correct ??

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

Title:
  Network Manager is not able to manage the devices on Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
   
  ---uname output---
  Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = z14 s390 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
  2. Configure a network device and login to the partition through ssh.
  3. Now you can see the following output
  root@(none):~# nmcli d s
  DEVICE  TYPE  STATE  CONNECTION
  eth0ethernet  unmanaged  --
  eth1ethernet  unmanaged  --
  lo  loopback  unmanaged  --
   
  Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: NetworkManager --version 1.10.4

  Userspace tool obtained from project website:  na 
   

  Some more information about the issue:

  Network device has been configured manually after the image is up from 
Support Element(SE):
  - znetconf -a 
  - cat /sys/bus/ccwgroup/drivers/qeth//if_name
  - ifconfig   netmask 255.255.255.0
  - route add default gw  
  - SSH service has been configured
  
  This helped us to login to the Lpar. In Lpar
  - output of znetconf -c
  Device IDs TypeCard Type  CHPID Drv. Name 
State
  
-
  0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 
online
  0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000  D0 qeth eth1 
online

  - output of nmcli c s
  root@(none):~# nmcli c s
  NAME  UUID  TYPE  DEVICE
  
  - output of nmcli d s
  root@(none):~# nmcli d s
  DEVICE  TYPE  STATE  CONNECTION
  eth0ethernet  unmanaged  --
  eth1ethernet  unmanaged  --
  lo  loopback  unmanaged  --
  
  * The above output shows that devices are not managed by nmcli
  
  After some investigation we found couple of suggestions like
  1. Ubuntu(version <17.04): Creating an empty 
file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and 
restarting NM,
 solved the issue.
 
  2. Ubuntu(version 17.10): Copying the said 
file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the 
 "unmanaged-devices" to none, resolved the issue.

  * link for reference: https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1638842

  For the latest version(18.04), none of the above solutions worked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions

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

[Touch-packages] [Bug 1774982] Re: X.Org upgrade resulted in screen, graphics card & input device not detected

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  X.Org upgrade resulted in screen, graphics card & input device not
  detected

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ever since an X.Org upgrade, both my Ubuntu and Mint machines fail to
  detect my screen, graphics card, and input device correctly.This
  happened to both machines at the same time after an upgrade. Running
  my Ubuntu machine in low-graphics mode works, but I have yet to even
  resolve the issue on my Mint machine. I assume this report contains
  log files, but I include info. from the xserver log file, below, which
  contains the following info. on module ABI versions, and the following
  errors, and warnings:

  Module ABI versions:
  X.Org ANSI C Emulation:0.4
  X.Org Video Driver: 20.0
  X.Org XInput drive:22.1
  X.Org Server Extension:9.0
  (++) using VT number 7

  (EE) /dev/dri/card0: failed to set DRM interface version 1.4:
  Permission denied

  (WW) Falling back to old probe method for modesetting
  (WW) Falling back to old probe method for fbdev
  (WW) Falling back to old probe method for vesa

  (EE) intel(0):[drm] failed to set drm interface version Permission denied [13]
  (EE) intel(0): Failed to claim DRM device
  (ii) UnloadModule: "intel"
  (EE) Screen(s)found, but none have a usable configuration
  (EE) Fatal server error
  (EE) Please consult the X.Org Foundation support at http://wiki.x.org for help
  (EE) Please also check the log file "/var/log/Xorg.0.log" for additional info.
  (EE) Server terminated w/error(1). Closing log file

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  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: Mon Jun  4 06:52:55 2018
  DistUpgraded: 2016-08-21 11:26:30,537 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420]
 Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0420]
  InstallationDate: Installed on 2015-03-24 (1168 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. OptiPlex 780
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=82224d43-e3b0-4b70-b588-ea0bfdceb405 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-21 (651 days ago)
  dmi.bios.date: 11/03/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 03NVJ6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/03/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn03NVJ6:rvrA02:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.
  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.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: Tue May 22 07:18:58 2018
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1773744] Re: Desktop session crash

[Daniel van Vugt]

Sami,

Please also tell us what bug IDs were created by:
  ubuntu-bug _usr_bin_gnome-shell.1000.crash
  ubuntu-bug _usr_bin_Xwayland.1000.crash
  ubuntu-bug _usr_lib_xorg_Xorg.1000.crash

You might find them here:
  https://bugs.launchpad.net/~/+reportedbugs?orderby=-id=0

If you don't then please have a look at
https://errors.ubuntu.com/user/ID where ID is the contents of the
machine's /var/lib/whoopsie/whoopsie-id file. If you find any relevant
crash reports there then please provide links to them here.

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

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

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

Title:
  Desktop session crash

Status in Ubuntu:
  Incomplete

Bug description:
  If I connect third monitor to my Ubuntu PC, the whole graphical
  display session crashes. Additionally, the login does not show texts
  correctly. The texts are mostly missing.

  The errors happend with both Wayland and X.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 28 10:15:54 2018
  DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [1002:6771] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X 
OEM] [103c:90b8]
  InstallationDate: Installed on 2016-11-22 (551 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago)
  dmi.bios.date: 09/09/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.18
  dmi.board.asset.tag: CZC3427KBP
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3427KBP
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.sys.vendor: Hewlett-Packard
  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 1:18.0.1-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/+bug/1773744/+subscriptions

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

[Touch-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland

[Daniel van Vugt]

** Description changed:

+ WORKAROUND:
+ 
+ Edit /etc/gdm3/custom.conf and uncomment:
+   #WaylandEnable=false
+ 
+ ---
+ 
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
- --- 
+ ---
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen with
  nouveau + Wayland

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND:

  Edit /etc/gdm3/custom.conf and uncomment:
#WaylandEnable=false

  ---

  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  ---
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1774265] Re: Heavy flicker/flashing on external monitors using resolutions higher than 1920x1080

[Daniel van Vugt]

According to JournalErrors.txt you're using the nouveau X driver. So
reassigning...

** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu)

** Tags added: nouveau

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

Title:
  Heavy flicker/flashing on external monitors using resolutions higher
  than 1920x1080

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

Bug description:
  Laptop model: Lenovo P51 20HH0011US
  OS: Fresh install from USB ‘Ubuntu GNOME 16.04.4 LTS’
  Monitors: Dell U2415b at 1920x1200, Asus PB278 at 2560x1440

  Expected behavior: We install Ubuntu 16.04.4, plug in additional
  monitors and those monitors work at the native resolution.

  Actual behavior: This one is going to be hard to describe. But when we plug 
in a monitor, that monitor will flicker/flash extremely fast. With both HDMI 
and miniDP outputs. Most of the company has two external monitors and when we 
plug in a second monitor one or both of the external monitors flickered on 14 
of the 15 machines that we tested. We also tested with 20 or so monitors 
through our process of trying to isolate the problem. I will leave links of the 
video that we took of the issue. From the online preview you cannot tell what 
the problem is, but if you download the videos and play them with VLC or 
something locally, you should be able to see what we are talking about. 
  
https://drive.google.com/file/d/1oZQwIf8uaUEytQPQdihIy3eCpVRLe7-T/view?usp=sharing
  
https://drive.google.com/file/d/1eBrfXouqXhddobGHZijM_G4qNIKiLtaI/view?usp=sharing

  
  We have noticed that if we change the resolution down to 1920x1080 the issue 
goes away. 

  The monitors do not flicker on other models of Lenovo’s that we have tried. 
They also do not flicker with the same computer but running Windows or on any 
macbook that we have tried. The other weird issue is that once the monitor 
starts flickering, it stays flickering for about an hour even without a 
computer plugged into it or if we plug in a different computer that did not 
make that monitor flicker before it was plugged into a P51 running Ubuntu gnome 
16.04.4. 
  Our current workaround is to install Ubuntu MATE 16.04.4 instead of gnome. 
The monitors work at native resolutions with MATE. 
  Let us know if there is anything else we can do to help with this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-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
  CurrentDesktop: GNOME
  Date: Tue May 29 15:24:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:13b6] (rev a2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2251]
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20HH0011US
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HH0011US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET41W(1.15):bd10/20/2017:svnLENOVO:pn20HH0011US:pvrThinkPadP51:rvnLENOVO:rn20HH0011US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HH0011US
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  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 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

To manage notifications about this bug go to:

[Touch-packages] [Bug 1774281] Re: Username displays incorrectly on login screen

[Daniel van Vugt]

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

The login screen always uses Wayland, even before you've decided to
choose Xorg. So...

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


** This bug has been marked a duplicate of bug 1760201
   ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + 
Wayland

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

Title:
  Username displays incorrectly on login screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Just did a clean install on a mid 2012 15" macbook pro. Every time
  that I get to the login screen, my username appears as strange blocks
  and shapes as pictured here:

  https://drive.google.com/file/d/0B4DXnUg-
  SK6WOG1ybjFTYnBWQ3B6eWVEelR6TmJWcHNJb2ZR/view?usp=sharing

  
  18.04 LTS
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:10:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fb]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00fc]
  MachineType: Apple Inc. MacBookPro9,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-22-generic ro 
root=UUID=bcac24f1-47fa-44d8-ae55-e5dff5f77a7d 
initrd=boot\initrd.img-4.15.0-22-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-4B7AC7E43945597E
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-4B7AC7E43945597E
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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/1774281/+subscriptions

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

[Touch-packages] [Bug 1775566] [NEW] networkd not applying config written by netplan on boot in q35 (PCIe) KVM guests

[ Christian Ehrhardt ]

Public bug reported:

Hi,
I miss some hidden trigger of "netplan apply" to understand the following case.

I have kvm guests, you can spawn your own one to reproduce via:
 $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
 $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
1. shut down your guest
2. run virsh edit bionic-netplan
2.1 replace pc-i440fx-bionic -> pc-q35-bionic
2.2 replace pci-root with pcie-root
2.3 replace piix3-uhci -> piix4-uhci
3. start the guest again
   virsh start bionic-netplan

It won't get network connection, this is where I started debugging.
I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

First I realized that the device names changed from ens3 -> enp0s3 (the kernel 
naming).
So I thought this entry might have a problem:
 ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:68:4b:62

I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
   If there are match: rules, then the ID field is a purely opaque name which 
is only being used 
   for references from definitions of compound devices in the config

And I found it works just fine when I run "sudo netplan apply".


This was odd, so to summarize up to here:
- PCIe based virt guest
- netplan egenrated config not working after (re)boot
- "netplan apply" makes it working


I disabled any cloud init things as recommended by the comment
  /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
  network: {config: disabled}
So that I can rely on my netplan yaml to stay as is.
I tried various things but so far can't find what magic "netplan apply" does 
which is missing to my boot.


I checked after reboot the devices are considered unmanaged by networkctl
$ networkctl list
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 enp0s3   ether  off unmanaged 

But the config was generated:
$ ll /run/systemd/network/
total 32
drwxr-xr-x  2 root root 200 Jun  7 09:02 ./
drwxr-xr-x 22 root root 500 Jun  7 09:02 ../
-rw-r--r--  1 root root  69 Jun  7 09:02 10-netplan-enp0s3.link
-rw-r--r--  1 root root 104 Jun  7 09:02 10-netplan-enp0s3.network

I checked the log and saw that apply restarts networkd.
So I thought might just restart networkd, so I ran
 $ sudo systemctl restart systemd-networkd.service
But things stayed as-is without the config being picked up.

With some nice discussion and help on IRC I also tried to disable netplan and 
check if this is networkd only.
# make this static networkd
$ sudo cp /run/systemd/network/10-netplan-enp0s* /etc/systemd/network/
# no netplan config
$ sudo mv /etc/netplan/* /root

That was supposed to show if networkd itself (or its config files) had issues.
And with that it still did not work, so is the error in networkd instead?
If so what magic thing does "netplan apply" do to fix it?

** Affects: netplan.io (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

Title:
  networkd not applying config written by netplan on boot in q35 (PCIe)
  KVM guests

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  I miss some hidden trigger of "netplan apply" to understand the following 
case.

  I have kvm guests, you can spawn your own one to reproduce via:
   $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
   $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
 virsh start bionic-netplan

  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
   ethernets:
  ens3:
  dhcp4: true
  match:
 

[Touch-packages] [Bug 1775566] Re: networkd not applying config written by netplan on boot in q35 (PCIe) KVM guests

[ Christian Ehrhardt ]

Since it might be networkd as well I added a bug task for it.

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

Title:
  networkd not applying config written by netplan on boot in q35 (PCIe)
  KVM guests

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  I miss some hidden trigger of "netplan apply" to understand the following 
case.

  I have kvm guests, you can spawn your own one to reproduce via:
   $ uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic label=daily
   $ uvt-kvm create --password ubuntu bionic-netplan arch=amd64 release=bionic 
label=daily

  So far all is good, but I wanted to run on q35 type guests (that means PCIe 
instead of PCI) based and more modern. To do so:
  1. shut down your guest
  2. run virsh edit bionic-netplan
  2.1 replace pc-i440fx-bionic -> pc-q35-bionic
  2.2 replace pci-root with pcie-root
  2.3 replace piix3-uhci -> piix4-uhci
  3. start the guest again
 virsh start bionic-netplan

  It won't get network connection, this is where I started debugging.
  I thought the devices might be wrong now or anything like it, but it is more 
puzzling.

  First I realized that the device names changed from ens3 -> enp0s3 (the 
kernel naming).
  So I thought this entry might have a problem:
   ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:68:4b:62

  I tried to name these enp0s3 to match,but it didn't matter and also according 
to the netplan man page:
 If there are match: rules, then the ID field is a purely opaque name which 
is only being used 
 for references from definitions of compound devices in the config

  And I found it works just fine when I run "sudo netplan apply".

  
  This was odd, so to summarize up to here:
  - PCIe based virt guest
  - netplan egenrated config not working after (re)boot
  - "netplan apply" makes it working

  
  I disabled any cloud init things as recommended by the comment
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
network: {config: disabled}
  So that I can rely on my netplan yaml to stay as is.
  I tried various things but so far can't find what magic "netplan apply" does 
which is missing to my boot.

  
  I checked after reboot the devices are considered unmanaged by networkctl
  $ networkctl list
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 enp0s3   ether  off unmanaged 

  But the config was generated:
  $ ll /run/systemd/network/
  total 32
  drwxr-xr-x  2 root root 200 Jun  7 09:02 ./
  drwxr-xr-x 22 root root 500 Jun  7 09:02 ../
  -rw-r--r--  1 root root  69 Jun  7 09:02 10-netplan-enp0s3.link
  -rw-r--r--  1 root root 104 Jun  7 09:02 10-netplan-enp0s3.network

  I checked the log and saw that apply restarts networkd.
  So I thought might just restart networkd, so I ran
   $ sudo systemctl restart systemd-networkd.service
  But things stayed as-is without the config being picked up.

  With some nice discussion and help on IRC I also tried to disable netplan and 
check if this is networkd only.
  # make this static networkd
  $ sudo cp /run/systemd/network/10-netplan-enp0s* /etc/systemd/network/
  # no netplan config
  $ sudo mv /etc/netplan/* /root

  That was supposed to show if networkd itself (or its config files) had issues.
  And with that it still did not work, so is the error in networkd instead?
  If so what magic thing does "netplan apply" do to fix it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1775566/+subscriptions

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

[Touch-packages] [Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

[Launchpad Bug Tracker]

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

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

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When using nslookup for local machine names, the local DNS was being
  ignored (not queried) and none of the local machines could be found.

  After much research and digging, it was discovered that the cause was
  the incorrect symbolic link /etc/resolv.conf file.

  The default install caused systemd-resolve to configure the link to point to 
the stub file:
  /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  Reomving that link and pointing it to the correct file solved the DNS lookup 
issue. The correct link looks like this:
  /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

  
  Steps used to test the bug before fixing the link is to perform an nslookup 
on a local (non FQDN) machine that is in your local DNS (my router is my DNS 
server for this case) Here is an example of the incorrect output:

  $ nslookup web1

  Server: 127.0.0.53
  Address:127.0.0.53#53

  ** server can't find web1: SERVFAIL

  
  Switching the symbolic link solves the problem. Here is my solution:

  $ sudo rm -f /etc/resolv.conf
  $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  
  After switching the symbolic link, the nslookup functions properly.

  $ nslookup web1

  Server: 192.168.1.1
  Address:192.168.1.1#53

  Name:   web1
  Address: 192.168.1.107

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  1 05:28:41 2018
  InstallationDate: Installed on 2018-01-20 (131 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Inspiron 5755
  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-22-generic 
root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0VY15F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 5755
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1753115] Re: add-apt-repository documentation does not mention --no-updates option

[Launchpad Bug Tracker]

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

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

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

Title:
  add-apt-repository documentation does not mention --no-updates option

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  The default has changed so that --updates is the default.  The man
  page should be updated to reflect that and to document the -n --no-
  updates option for 18.04

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

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

[Touch-packages] [Bug 1771539] Re: Xorg crash

[Mario Costa]

1)
```
$ls -la /var/crash/
total 8080
drwxrwsrwt  2 root whoopsie4096 Jun  7 01:30 .
drwxr-xr-x 14 root root4096 Ago  1  2017 ..
-rwxrwxrwx  1 root whoopsie   0 Jun  7 01:17 .lock
-rw-r-  1 root whoopsie 8265453 Jun  7 01:28 _usr_lib_xorg_Xorg.0.crash
-rw-r--r--  1 root whoopsie   0 Jun  7 01:30 _usr_lib_xorg_Xorg.0.upload
-rw---  1 whoopsie whoopsie   0 Jun  7 01:30 
_usr_lib_xorg_Xorg.0.uploaded
```

2) I've probably added id, when trying to disable the graphic card, to
use only one, as when trying to fix it came across some threads
suggesting that (e.g. https://askubuntu.com/questions/771562/16-04
-power-off-discrete-graphics-ati-amd). (I'll test removing this later on
the day).

3) Dell U2715H (REV A01, 2015)
(http://accessories.ap.dell.com/sna/productdetail.aspx?c=hk=en=bsd=hkbsd1=210-ADSZ)

4)  DisplayPort-to-DisplayPort (pc DisplayPort-MiniDisplayPort monitor)

5) No, it crashes.

6) Both, no difference.

I start the laptop, from cold boot, first login screen displays properly
in both monitors cloning the display. Afterwards I try to login and when
setting new settings starts crashing repeatedly, trying to restart the
xserver (as it seems).

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I try to use ubuntu with dual desktop display it crashes
  continuously, and entering into login mode.

  I cannot use dual display.
  To use an external monitor, I have to start the laptop with the computer 
closed.

  It seems to be related to the graphic card, maybe dual graphic card of
  the laptop.

  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 x86_64
  .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: None
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 16 10:36:05 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990]
  InstallationDate: Installed on 2017-12-13 (153 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.39
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG44010XD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  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.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Mar  8 12:39:32 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1775540] [NEW] Intermittent ipv4 connectivity on bionic beaver

[jeremy-list]

Public bug reported:

To replicate:

Connect to a wifi network (wired untested). The problem occurs most
consistently for DHCP configured connections but is also a significant
problem for manually configured connection.

Expected results:

IPv4 and IPv6 should both auto-configure correctly and be usable: as
they were in previous versions of Ubuntu, and still are on other devices
and operating systems.

Actual results:

IPv6 is automatically configured correctly and I have no difficulty
using IPv6 services. Most of the time no IPv4 address is configured.
Manually configuring an IPv4 address is possible but usually does not
result in a working IPv4 connection (pinging the gateway gives
"destination host unreachable")

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun  7 20:05:56 2018
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-05-11 (26 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
IpRoute:
 default via 192.168.178.1 dev wlp2s0 proto static metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.178.0/24 dev wlp2s0 proto kernel scope link src 192.168.178.28 metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTION CON-UUID  
CON-PATH   
 wlp2s0 wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  2degrees Broadband - D377  
10b8508a-4b0a-4ec4-9adb-e30685236fb7  
/org/freedesktop/NetworkManager/ActiveConnection/6 
 B8:C1:11:CA:B7:3A  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  -- --
-- 
 enp1s0 ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  -- --
-- 
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  -- --
--
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  disabled

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

Title:
  Intermittent ipv4 connectivity on bionic beaver

Status in network-manager package in Ubuntu:
  New

Bug description:
  To replicate:

  Connect to a wifi network (wired untested). The problem occurs most
  consistently for DHCP configured connections but is also a significant
  problem for manually configured connection.

  Expected results:

  IPv4 and IPv6 should both auto-configure correctly and be usable: as
  they were in previous versions of Ubuntu, and still are on other
  devices and operating systems.

  Actual results:

  IPv6 is automatically configured correctly and I have no difficulty
  using IPv6 services. Most of the time no IPv4 address is configured.
  Manually configuring an IPv4 address is possible but usually does not
  result in a working IPv4 connection (pinging the gateway gives
  "destination host unreachable")

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  7 20:05:56 2018
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 192.168.178.1 dev wlp2s0 proto static metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.178.0/24 dev wlp2s0 proto kernel scope link src 192.168.178.28 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  

[Touch-packages] [Bug 1772859] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From kieni...@de.ibm.com 2018-06-07 03:18 EDT---
"So your system is obviously not an 18.04 default installation from scratch" 
This is correct. We are not using a standard installation but build an 
appliance with a minimal footprint. Our build process builds the appliance 
using debootstrap and we are using a local apt repository with the deb packages 
from UBUNTU 18.04 as input for debootstrap. So we are basically controlling 
what packages are installed in our appliances and right now netplan is not 
included.

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

Title:
  Network Manager is not able to manage the devices on Ubuntu 18.04

Status in Ubuntu on IBM z Systems:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  NetworkManager is not able to manage the devices on latest Ubuntu(18.04)
   
  ---uname output---
  Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = z14 s390 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4).
  2. Configure a network device and login to the partition through ssh.
  3. Now you can see the following output
  root@(none):~# nmcli d s
  DEVICE  TYPE  STATE  CONNECTION
  eth0ethernet  unmanaged  --
  eth1ethernet  unmanaged  --
  lo  loopback  unmanaged  --
   
  Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el 
s390x 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: NetworkManager --version 1.10.4

  Userspace tool obtained from project website:  na 
   

  Some more information about the issue:

  Network device has been configured manually after the image is up from 
Support Element(SE):
  - znetconf -a 
  - cat /sys/bus/ccwgroup/drivers/qeth//if_name
  - ifconfig   netmask 255.255.255.0
  - route add default gw  
  - SSH service has been configured
  
  This helped us to login to the Lpar. In Lpar
  - output of znetconf -c
  Device IDs TypeCard Type  CHPID Drv. Name 
State
  
-
  0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 
online
  0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000  D0 qeth eth1 
online

  - output of nmcli c s
  root@(none):~# nmcli c s
  NAME  UUID  TYPE  DEVICE
  
  - output of nmcli d s
  root@(none):~# nmcli d s
  DEVICE  TYPE  STATE  CONNECTION
  eth0ethernet  unmanaged  --
  eth1ethernet  unmanaged  --
  lo  loopback  unmanaged  --
  
  * The above output shows that devices are not managed by nmcli
  
  After some investigation we found couple of suggestions like
  1. Ubuntu(version <17.04): Creating an empty 
file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and 
restarting NM,
 solved the issue.
 
  2. Ubuntu(version 17.10): Copying the said 
file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the 
 "unmanaged-devices" to none, resolved the issue.

  * link for reference: https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1638842

  For the latest version(18.04), none of the above solutions worked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions

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

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Falk]

I could not agree more with Jeff Carr.
This is a really important function.

>From my pov this is not a low priority bug.

--
Regards Falk

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7

[Bart Goeman]

well my reasoning was slightly different from supported/unsupported
i am not familiar with the exact scope of the apport project,
but I assume the goal is to collect info on ubuntu packages, not any unrelated 
code,
and since afaik all packages one one release all use the same (system) python 
version( i.e. 3.6 for bionic),
-> code running under any other python is of no interest anyhow
-> it only makes sense to install the apport exception hook for that python 
version,

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

Title:
  apport python exception handler messes up python3.7

Status in apport package in Ubuntu:
  New
Status in python-apt package in Ubuntu:
  Invalid

Bug description:
  it seems apport installs an exception hook whenever running python3.
  This hook is apparently installed for python3.7 too.
  This exception handler has a dependency on apt_pkg, which is a binary that is 
not compatible with python3.7 it seems (you can't import it, see below)

  As a result, whenever I run a python3.7 script and run into an exception 
(which happens often when writing code), I get an additional exception in the 
exception handler + a copy of the original exception, so three stacktraces in 
total.
  A solution would be to only install the exception hook for the system python  
i.e. python3.6

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

  apport: 2.20.9-0ubuntu7
  python-apt: 1.6.0
  python3.7: 3.7.0~b3-1

  Demo with a trivial error:
  $ python3 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?

  
  $ python3.7 -c 'print hello'
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ModuleNotFoundError: No module named 'apt_pkg'

  Original exception was:
File "", line 1
  print hello
^
  SyntaxError: Missing parentheses in call to 'print'. Did you mean 
print(hello)?


  Python 3.6.5 (default, Apr  1 2018, 05:46:30) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >>> import apt_pkg
  >>> apt_pkg.__file__
  '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so'
  >>> 

  Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) 
  [GCC 7.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sys
  >>> sys.excepthook
  
  >> import apt_pkg
  Traceback (most recent call last):
File "", line 1, in 
  ModuleNotFoundError: No module named 'apt_pkg'

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

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

[Touch-packages] [Bug 1356222] Re: [MIR] fcitx and related packages

[Didier Roche]

we demoted fcitx mid-2017.

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

Title:
  [MIR] fcitx and related packages

Status in extra-cmake-modules package in Ubuntu:
  Fix Released
Status in fcitx package in Ubuntu:
  Fix Released
Status in fcitx-anthy package in Ubuntu:
  Fix Committed
Status in fcitx-chewing package in Ubuntu:
  Fix Committed
Status in fcitx-cloudpinyin package in Ubuntu:
  Fix Released
Status in fcitx-configtool package in Ubuntu:
  Fix Released
Status in fcitx-googlepinyin package in Ubuntu:
  Fix Committed
Status in fcitx-hangul package in Ubuntu:
  Fix Released
Status in fcitx-m17n package in Ubuntu:
  Fix Committed
Status in fcitx-qimpanel package in Ubuntu:
  Fix Released
Status in fcitx-qt5 package in Ubuntu:
  Fix Released
Status in fcitx-sunpinyin package in Ubuntu:
  Fix Committed
Status in fcitx-table-extra package in Ubuntu:
  Fix Committed
Status in fcitx-table-other package in Ubuntu:
  Fix Committed
Status in fcitx-unikey package in Ubuntu:
  Fix Released
Status in libgooglepinyin package in Ubuntu:
  Fix Committed
Status in presage package in Ubuntu:
  Fix Released
Status in tinyxml package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  Currently in universe

  [Rationale]
  Fcitx is a replacement candidate for IBus

  [Security: ]
  CVE entries: none
  Security history: none
  Any binaries running as root or suid/sgid ? Any daemons ?
  -- all running as per user session, and /usr/bin/fcitx and 
/usr/bin/fcitx-qimpanel will run as daemon, /usr/bin/fcitx-dbus-watcher will be 
pulled up when fcitx is running.
  Network activity: does it open any port ? Does it handle incoming network 
data ?
  -- fcitx-cloudpinyin deals with network data by using libcurl and 
interact with remote API from several user-choosable providers.
  Does it directly (not through a library) process binary (video, audio, etc) 
or structured (PDF, etc) data ?
  -- no, it doesn't
  Any source code review performed ? (The approver will do a quick and shallow 
check.)
  -- no.

  [Quality Assurance]
  Package works out of the box with no prompting.
  There is no reproducible major bugs in Ubuntu and Debian.
  Upstream is active.
  Package is team maintained at Debian, and is the same people working on 
Debian and Ubuntu.

  Upstream bug tracker: https://github.com/fcitx/fcitx
  Hardware: Does this package deal with hardware and if so how exotic is it ?
  -- no
  Is there a test suite in the upstream source or packaging ? Is it enabled to 
run in the build ?
  -- yes, some fundamental tests

  [UI standards]
  User-visible strings are internationalized using standard gettext system ?
  -- yes
  Package with translatable strings builds a PO template during package 
build ?
  -- yes
  End-user applications ship a desktop file?
  -- fcitx and fcitx-ui-qimpanel do.

  [Standards Compliance]
  FHS and Debian Policy compliant.
  Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities 
?
  -- package is using debhelper,

  [Maintenance]
  Desktop Team will take care of them

  [Dependencies]
  librime and brise are for fcitx-rime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/extra-cmake-modules/+bug/1356222/+subscriptions

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

[Touch-packages] [Bug 1605657] Re: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

[Jess Stuart]

If this is an "Invalid" bug, can anyone offer help on how to correct
this problem?  Matthias Klose (doko), any help?

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

Title:
  package python3 3.5.1-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  I delet python3.5 by wrong using sudo apt-get remove python3.5 and to
  fix that I logged in from terminal because I lost my desktop terminal
  and I reinstalled the ubuntu dektop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Jul 22 14:48:23 2016
  DuplicateSignature:
   package:python3:3.5.1-3
   Removing python3 (3.5.1-3) ...
   /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: 
py3clean: not found
   dpkg: error processing package python3 (--remove):
subprocess installed pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2016-04-18 (94 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: Upgraded to xenial on 2016-06-01 (50 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.30-20ubuntu2~18.04

---
binutils (2.30-20ubuntu2~18.04) bionic-security; urgency=medium

  * Combined security update / SRU: LP: #1771635, LP: #1769657.

binutils (2.30-20ubuntu2) cosmic; urgency=medium

  * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098.
  * Fix PR binutils/23054, memory corruption in as. LP: #1763096.
  * Fix PR ld/23055, memory corruption in ld. LP: #1763094.

binutils (2.30-20ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-20) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180516.
- Fix PR binutils/23109, disassembly mask for vector sdot on AArch64.
- Fix uninitialised memory acccess in COFF bfd backend.
- Update Portuguese translations.

binutils (2.30-19) unstable; urgency=medium

  * Build-depend on procps.

binutils (2.30-17ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-17) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180502.
- Fix PR ld/23123, PR ld/22374, PowerPC32 ifunc regression.
- AArch64: Fix the mask for the sqrdml(a|s)h instructions.
  * Fix unintialized memory in aarch64 opcodes, taken from the trunk.

binutils (2.30-16) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180425.
- Fix PR ld 22782, x86: Remove the unused _GLOBAL_OFFSET_TABLE_.
- Update spanish and russian translations.
  * Add amd64, i386, x32 and riscv64 cross compilers as build (test)
dependencies.

 -- Matthias Klose   Wed, 16 May 2018 15:20:51 -0400

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

-- 
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:
  Fix Released
Status in binutils source package in Bionic:
  Fix Released

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 1769657] Re: update toolchain packages for bionic

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.30-20ubuntu2~18.04

---
binutils (2.30-20ubuntu2~18.04) bionic-security; urgency=medium

  * Combined security update / SRU: LP: #1771635, LP: #1769657.

binutils (2.30-20ubuntu2) cosmic; urgency=medium

  * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098.
  * Fix PR binutils/23054, memory corruption in as. LP: #1763096.
  * Fix PR ld/23055, memory corruption in ld. LP: #1763094.

binutils (2.30-20ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-20) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180516.
- Fix PR binutils/23109, disassembly mask for vector sdot on AArch64.
- Fix uninitialised memory acccess in COFF bfd backend.
- Update Portuguese translations.

binutils (2.30-19) unstable; urgency=medium

  * Build-depend on procps.

binutils (2.30-17ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-17) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180502.
- Fix PR ld/23123, PR ld/22374, PowerPC32 ifunc regression.
- AArch64: Fix the mask for the sqrdml(a|s)h instructions.
  * Fix unintialized memory in aarch64 opcodes, taken from the trunk.

binutils (2.30-16) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180425.
- Fix PR ld 22782, x86: Remove the unused _GLOBAL_OFFSET_TABLE_.
- Update spanish and russian translations.
  * Add amd64, i386, x32 and riscv64 cross compilers as build (test)
dependencies.

 -- Matthias Klose   Wed, 16 May 2018 15:20:51 -0400

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

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

Title:
  update toolchain packages for bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in build-essential package in Ubuntu:
  New
Status in cross-toolchain-base package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in gcc-7-cross package in Ubuntu:
  New
Status in gcc-7-cross-ports package in Ubuntu:
  New
Status in gcc-8 package in Ubuntu:
  New
Status in gcc-8-cross package in Ubuntu:
  New
Status in gcc-8-cross-ports package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in gcc-defaults-ports package in Ubuntu:
  New

Bug description:
  I'd like to update the toolchain packages in bionic, to state which we
  have in cosmic on May 07:

   - LP: #1771635: binutils updates from the branch
   - gcc-8, update to the final 8.1.0 release
   - gcc-7, updates to the gcc-7-branch up to the time of the
     8.1.0 release.
   - gcc-defaults to bump the 8.1 version, and add some provides
   - build-essential to add cross packages for amd64 and i386
   - corresponding gcc-cross packages

  The package builds are prepared in
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages

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

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

[Touch-packages] [Bug 1771635] Re: SRU: update binutils for bionic

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.30-20ubuntu2~18.04

---
binutils (2.30-20ubuntu2~18.04) bionic-security; urgency=medium

  * Combined security update / SRU: LP: #1771635, LP: #1769657.

binutils (2.30-20ubuntu2) cosmic; urgency=medium

  * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098.
  * Fix PR binutils/23054, memory corruption in as. LP: #1763096.
  * Fix PR ld/23055, memory corruption in ld. LP: #1763094.

binutils (2.30-20ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-20) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180516.
- Fix PR binutils/23109, disassembly mask for vector sdot on AArch64.
- Fix uninitialised memory acccess in COFF bfd backend.
- Update Portuguese translations.

binutils (2.30-19) unstable; urgency=medium

  * Build-depend on procps.

binutils (2.30-17ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-17) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180502.
- Fix PR ld/23123, PR ld/22374, PowerPC32 ifunc regression.
- AArch64: Fix the mask for the sqrdml(a|s)h instructions.
  * Fix unintialized memory in aarch64 opcodes, taken from the trunk.

binutils (2.30-16) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180425.
- Fix PR ld 22782, x86: Remove the unused _GLOBAL_OFFSET_TABLE_.
- Update spanish and russian translations.
  * Add amd64, i386, x32 and riscv64 cross compilers as build (test)
dependencies.

 -- Matthias Klose   Wed, 16 May 2018 15:20:51 -0400

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

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

Title:
  SRU: update binutils for bionic

Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  This is the binutils part of LP: #1769657.

  The update contains backports from the 2.30 branch.  GCC packages, and
  GCC cross packages have been tebuilt using this version in cosmic. The
  kernel has been rebuilt with -17 in cosmic.

  Changes are:

* Fix PR gprof/23056, memory corruption in gprof. LP: #1763098.
* Fix PR binutils/23054, memory corruption in as. LP: #1763096.
* Fix PR ld/23055, memory corruption in ld. LP: #1763094.
  - Fix PR binutils/23109, disassembly mask for vector sdot on AArch64.
  - Fix uninitialised memory acccess in COFF bfd backend.
  - Update Portuguese translations.
  - Fix PR ld/23123, PR ld/22374, PowerPC32 ifunc regression.
  - AArch64: Fix the mask for the sqrdml(a|s)h instructions.
* Fix unintialized memory in aarch64 opcodes, taken from the trunk.
  - Fix PR ld 22782, x86: Remove the unused _GLOBAL_OFFSET_TABLE_.
  - Update spanish and russian translations.

  Packaging changes:

* Add amd64, i386, x32 and riscv64 cross compilers as build (test)
  dependencies.

  Acceptance criteria:

   * The package builds and doesn't show any regression in the testsuite
  and autopkg tests.

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.30-20ubuntu2~18.04

---
binutils (2.30-20ubuntu2~18.04) bionic-security; urgency=medium

  * Combined security update / SRU: LP: #1771635, LP: #1769657.

binutils (2.30-20ubuntu2) cosmic; urgency=medium

  * Fix PR gprof/23056, memory corruption in gprof. LP: #1763098.
  * Fix PR binutils/23054, memory corruption in as. LP: #1763096.
  * Fix PR ld/23055, memory corruption in ld. LP: #1763094.

binutils (2.30-20ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-20) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180516.
- Fix PR binutils/23109, disassembly mask for vector sdot on AArch64.
- Fix uninitialised memory acccess in COFF bfd backend.
- Update Portuguese translations.

binutils (2.30-19) unstable; urgency=medium

  * Build-depend on procps.

binutils (2.30-17ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

binutils (2.30-17) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180502.
- Fix PR ld/23123, PR ld/22374, PowerPC32 ifunc regression.
- AArch64: Fix the mask for the sqrdml(a|s)h instructions.
  * Fix unintialized memory in aarch64 opcodes, taken from the trunk.

binutils (2.30-16) unstable; urgency=medium

  * Update, taken from the 2.30 branch 20180425.
- Fix PR ld 22782, x86: Remove the unused _GLOBAL_OFFSET_TABLE_.
- Update spanish and russian translations.
  * Add amd64, i386, x32 and riscv64 cross compilers as build (test)
dependencies.

 -- Matthias Klose   Wed, 16 May 2018 15:20:51 -0400

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

-- 
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:
  Fix Released
Status in binutils source package in Bionic:
  Fix Released

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