[Touch-packages] [Bug 1770323] [NEW] 1440x900 resolution is not stable with a dell monitor.

[VK Joseph]

Public bug reported:

Had filed a bug report earlier and the problem was not there for 2 days

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 10 11:01:19 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
InstallationDate: Installed on 2018-05-08 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=c785f1d1-48a1-4648-a96f-6c2a8d37d5b2 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FG
dmi.board.name: 945GZM-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 945GZM-S2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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

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

Title:
  1440x900 resolution is not stable with a dell monitor.

Status in xorg package in Ubuntu:
  New

Bug description:
  Had filed a bug report earlier and the problem was not there for 2
  days

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 10 11:01:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=c785f1d1-48a1-4648-a96f-6c2a8d37d5b2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: 945GZM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1770321] [NEW] help

[Ashish Adhikari]

Public bug reported:

me

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 10 11:16:32 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:110f]
InstallationDate: Installed on 2018-05-09 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-475
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=65ab738c-e1f4-4212-91c7-fc8d3d4df889 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.01
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: AntMan_SK
dmi.board.vendor: Acer
dmi.board.version: V1.01
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: SKL
dmi.product.name: Aspire E5-475
dmi.product.version: V1.01
dmi.sys.vendor: Acer
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

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

Title:
  help

Status in xorg package in Ubuntu:
  New

Bug description:
  me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 10 11:16:32 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:110f]
  InstallationDate: Installed on 2018-05-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-475
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=65ab738c-e1f4-4212-91c7-fc8d3d4df889 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: AntMan_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SKL
  dmi.product.name: Aspire E5-475
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Kai-Heng Feng]

Is this solved in latest mainline kernel?

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1770306] [NEW] X display is black after 18.04 upgrade from 17.10

[Kevin Dalley]

Public bug reported:

I can manually start lightdm, and that will give me a login screen,

Unfortunately, most of the desktop environments crash after login.

Only plasma gives me a little bit of clients, though even plasma
complains

All shell packages missing
And
Vboxclient warning

Under 17.10, I successfully used Wayland

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Wed May  9 19:15:12 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 5500 [1028:0665]
InstallationDate: Installed on 2015-05-18 (1087 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. XPS 13 9343
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.
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

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


** Tags: amd64 apport-bug bionic crash 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/1770306

Title:
  X display is black after 18.04 upgrade from 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I can manually start lightdm, and that will give me a login screen,

  Unfortunately, most of the desktop environments crash after login.

  Only plasma gives me a little bit of clients, though even plasma
  complains

  All shell packages missing
  And
  Vboxclient warning

  Under 17.10, I successfully used Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed May  9 19:15:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:0665]
  InstallationDate: Installed on 2015-05-18 (1087 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash 
i915.i915_enable_rc6=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

[Hui Wang]

I installed cosmic daily build 0509, the alsa-lib is 1.1.6-1ubuntu1, it
worked well.

Waiting for the bionic 1.1.3-5ubuntu1 to be ready.

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  In Progress

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_name, let other machines
  fail to search by card_long_name, then fallback to original searching
  method - search by card_name.

  [Other Info]

  Since I could not find the alsa-lib repository in canonical, I just
  generated the debdiff with "apt-get source ...".

To manage notifications about this bug go to:

[Touch-packages] [Bug 1769893] Re: CUPS Unauthorized when using Chrome browser

[Launchpad Bug Tracker]

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

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

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

Title:
  CUPS Unauthorized when using Chrome browser

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Using Chrome Version 66.0.3359.139 (Official Build) (64-bit)

  I am able to access and add a printer through Chrome by going to the
  page http://localhost:631/admin/login and I can add a printer fine.
  But I cannot add the printer if I go directly to
  http://localhost:631/admin and bypass the login.  If I need to change
  any defaults of the printer through the same pages it gives me the
  "Unauthorized" and will not change anything.  I can change it in
  Firefox and the printers control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CupsErrorLog:
   E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
   E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
   E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 
(Authentication failure)
   E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: XFCE
  Date: Tue May  8 07:18:47 2018
  InstallationDate: Installed on 2018-05-05 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat:
   device for Deskjet_3520_series_75C0A7_: 
ipp://HP6C3BE575C0A7.local:631/ipp/print
   device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', 
'/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied
   grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 
biosdevname=0
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.8
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K9N2GM-FIH(MS-7508)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7508
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Touch-packages] [Bug 1765141] Re: [regression] Full screen white flash from time to time (Wayland and X11)

[Daniel van Vugt]

** Tags added: amggpu radeon

** Tags removed: amggpu
** Tags added: amdgpu

** Summary changed:

- [regression] Full screen white flash from time to time (Wayland and X11)
+ [amdgpu][radeon][regression] Full screen white flash from time to time 
(Wayland and X11)

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

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  [amdgpu][radeon][regression] Full screen white flash from time to time
  (Wayland and X11)

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 18.04 with gnome shell on Wayland.

  From time to time, maybe every one or two hours, the desktop becomes
  white for a fraction of second. I guess it is just one frame (1/60 of
  second). It looks like a full filled rectangle of white color but it
  is so fast I cannot verify to be sure (the only solution I'm thinking
  of would be to have a fast recording camera pointed to my display).

  I did not experience that problem on Ubuntu 17.10 with Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 19:26:15 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-07 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Daniel van Vugt]

Thanks. Exact numbers help a lot.

** Summary changed:

- [regression][bionic] Bluetooth keyboard battery reports 0%
+ [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 
and later)

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1656557] Re: sshd boolean option parsing is excessively case-sensitive

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:7.7p1-2

---
openssh (1:7.7p1-2) unstable; urgency=medium

  * Fix parsing of DebianBanner option (closes: #894730).

 -- Colin Watson   Wed, 04 Apr 2018 00:47:29 +0100

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  sshd boolean option parsing is excessively case-sensitive

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  
  Dear People,

  The field 'PasswordAuthentication' unlike all the others requires no
  capitalization in order for the ssh daemon to start properly!

  While this works:

  PasswordAuthentication yes

  
  The following doesn't work for this field (though works for other fields):

  PasswordAuthentication Yes

  This is most likely an issue to bring up to upstream project. Could we
  have a fix so that configuration can be done in a consistent way and
  the daemon doesn't break because of capitalization of a given
  parameter (it works on the other fields using [Yy] or [Nn]).

  This is a reality in 14.04 and 16.04.

  Thanks for your time.

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

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

[Touch-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

[Doug McMahon]

As stated in duped bug removing nvidia drivers (nvidia-390 here) via 
software-properties only removes the driver meta package so actually nothing is 
removed. 
(- and of course /etc/modprobe.d/nvidia-graphics-drivers.conf will still  be 
there ..

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

Title:
  Uninstall left nouveau blacklisted

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

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

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

[Touch-packages] [Bug 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte

[Brian Murray]

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

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

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

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

Title:
  uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
  decode byte; invalid continuation byte

Status in apport package in Ubuntu:
  In Progress

Bug description:
  Hi,

  here is a python exception I got while reporting a bug:

  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/ubuntu.py", line 89, in add_info
  check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in 
check_attachment_for_errors
  trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in 
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070: 
invalid continuation byte

  It can also be seen here:

https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu6
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 23 20:13:24 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/cosmic/apport/ubuntu

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

Title:
  uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
  decode byte; invalid continuation byte

Status in apport package in Ubuntu:
  In Progress

Bug description:
  Hi,

  here is a python exception I got while reporting a bug:

  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/ubuntu.py", line 89, in add_info
  check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in 
check_attachment_for_errors
  trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in 
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070: 
invalid continuation byte

  It can also be seen here:

https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu6
  Uname: Linux 4.16.3-041603-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 23 20:13:24 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

** Branch linked: lp:~ubuntu-core-dev/ubuntu/cosmic/apport/ubuntu

-- 
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:
  In Progress

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

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] Re: PythonDetails contains an error message if python not installed

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/cosmic/apport/ubuntu

-- 
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:
  New

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launchpad 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

  
  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 1766794] Re: apport-collect doesn't create a ProblemType in the report

[Brian Murray]

** Changed in: apport
   Status: Triaged => Fix Released

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

-- 
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:
  Triaged
Status in apport source package in Bionic:
  Triaged

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

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 1766740] Re: apport autopkgtest regression due to kernel packaging changes

[Launchpad Bug Tracker]

** Branch linked: lp:apport

-- 
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:
  In Progress

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

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 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs

[Dirk F]

Please see my comments at https://bugs.launchpad.net/ubuntu/+source
/initramfs-tools/+bug/1644975/comments/12 and
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/1644975/comments/10.

In summary, /etc/initramfs-tools/conf.d/resume is obsolete.

The resume process is supposed to be driven by kernel command-line
parameters resume and (optionally) resume_offset (which can be set by a
script during update-grub) and the script /etc/initramfs-tools/scripts
/local-premount/resume.

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

Title:
  Lubuntu bionic boots slower than the other Ubuntu flavours with some
  SSDs

Status in initramfs-tools package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  See this thread at the Ubuntu Forums:

  https://ubuntuforums.org/showthread.php?t=2388799

  How come the ultra light Lubuntu Bionic needs 40 seconds from the grub
  menu to the log in screen, while the corresponding Kubuntu and Xubuntu
  Bionic can do it in 10 seconds in my Toshiba laptop?

  All the operating systems were installed from the Bionic Beta-2
  desktop 64-bit iso files and made up to date today (and reside in a
  new SSD connected via the internal SATA bay).

  -o-

  and to summarize the conclusion

  
https://ubuntuforums.org/showthread.php?t=2388799=2=13756324#post13756324

  This supports the assumption, that there are problems for Lubuntu to
  manage SSDs with 4096 byte size physical sectors. But the other
  flavours of Ubuntu can manage it.

  Let us hope that this can help the Lubuntu developer to find and
  squash the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lubuntu-desktop 0.93
  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
  CurrentDesktop: LXDE
  Date: Fri Apr 13 09:59:42 2018
  InstallationDate: Installed on 2018-04-06 (7 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405)
  SourcePackage: lubuntu-meta
  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/1763611/+subscriptions

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

[Touch-packages] [Bug 1644975] Re: Resume from disk (swapfile) fails

[Dirk F]

In the related bug #1763611, it is concluded that the Ubiquity installer
incorrectly set up /etc/initramfs-tools/conf.d/resume to reference a
non-existent disk UUID, causing a 30-40s delay in startup.

Surely that file is obsolete (because it doesn't help resume from
swapfile, eg) and should be removed from the installation?

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Incomplete

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

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

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

[Brian Murray]

If the source package has changed then there will also need to be an
additional apport package hook, symlink, for source_linux-signed.py
otherwise bug reports about kernels are going to be pretty incomplete.

-- 
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:
  In Progress

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

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 1766740] Re: apport autopkgtest regression due to kernel packaging changes

[Brian Murray]

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

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

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

Title:
  apport autopkgtest regression due to kernel packaging changes

Status in apport package in Ubuntu:
  In Progress

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

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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Justin]

I have this problem on a Dell XPS 15 laptop touchpad running Linux Mint
18.3 based upon Ubuntu 16.04. This actually defaults to libinput, and
that's where I first encountered the issue. So I tried synaptic to see
if it would go away (it did not), which led me to this bug. So for me it
happens with both drivers, it's just worse under synaptic. With
libinput, it doesn't jump as far across the screen. But it does jump,
under the scenario described in #52 -- you're moving the mouse with one
finger to where you want to click, and you click with the other finger.
But at that moment the pointer jumps in the direction of the other
pointer (for right-handed people clicking with their pointer finger,
this is to the bottom left).

Sadly, these are touchpads without dedicated buttons, but being used by
users who are used to having and using dedicated buttons. In either
case, it's quite frustrating. And it does not occur under windows, so it
isn't a hardware-only issue.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1770265] Re: package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Python install corrupted.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  9 14:01:46 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-10-26 (194 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770268] [NEW] [GeForce GTX 1080] 18.04 DisplayPort 15m cable no display

[naisanza]

Public bug reported:

related: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after 
starting "EFI VGA"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1747488

related: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747492


See related bug reports.

The same behavior is seen with Ubuntu 18.04.

Setting `nomodeset` in the grub kernel line is the only way for the
installer to be displayed. If `nomodeset` is not set, the installer will
boot into full resolution 3440x1440 and no display is able to reach the
monitor.

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

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

Title:
  [GeForce GTX 1080]  18.04 DisplayPort 15m cable no display

Status in mesa package in Ubuntu:
  New

Bug description:
  related: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after 
starting "EFI VGA"
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1747488

  related: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747492

  
  See related bug reports.

  The same behavior is seen with Ubuntu 18.04.

  Setting `nomodeset` in the grub kernel line is the only way for the
  installer to be displayed. If `nomodeset` is not set, the installer
  will boot into full resolution 3440x1440 and no display is able to
  reach the monitor.

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

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

[Touch-packages] [Bug 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa

[Bump]

Ok waiting for update, already on bionic-proposal.

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

Title:
  software-properties-gtk  gets stuck when switching from nvidia to
  nouveau and vice-versa

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching from nvidia to nouveau makes the gui to get stuck at
  "Applying changes..."

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

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

[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

[Bump]

I'm also affected:

https://bugs.launchpad.net/ubuntu/+source/software-
properties/+bug/1769338

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

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

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

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

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

[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

[Bump]

Running bionic-proposed here and still can't see software-properties
(0.96.24.33):

root@ubuntu:~# dpkg -l | grep software-properties
ii  python3-software-properties 0.96.24.32.2
all  manage the repositories that you install software 
from
ii  software-properties-common  0.96.24.32.2
all  manage the repositories that you install software 
from (common)
ii  software-properties-gtk 0.96.24.32.2
all  manage the repositories that you install software 
from (gtk)
ii  software-properties-kde 0.96.24.32.2
all  manage the repositories that you install software 
from (qt)

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

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

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

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

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

[Touch-packages] [Bug 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa

[Bump]

Ok waiting for update, already on bionic-proposal.

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

Title:
  software-properties-gtk  gets stuck when switching from nvidia to
  nouveau and vice-versa

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching from nvidia to nouveau makes the gui to get stuck at
  "Applying changes..."

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

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

[Touch-packages] [Bug 1770265] [NEW] package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co

[darkhipo]

Public bug reported:

Python install corrupted.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed May  9 14:01:46 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2017-10-26 (194 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1 failed 
to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited 
with return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1
  failed to install/upgrade: run-parts: /etc/kernel/postinst.d
  /initramfs-tools exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Python install corrupted.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  9 14:01:46 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-10-26 (194 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-41-generic 4.13.0-41.46~16.04.1 
failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770255] [NEW] Audio will not play from speakers or headphones after boot

[Steven Sandoval]

Public bug reported:

On bootup, the bootup ubuntu sound plays.  After ubuntu is fully booted,
the headphones or audio from speakers will not work.  If I change audio
output to hdmi and connect headphones to that, sound plays as expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 4.4.0-1055.64-aws 4.4.117
Uname: Linux 4.4.0-1055-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed May  9 20:29:26 2018
Ec2AMI: ami-da05a4a0
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1a
Ec2InstanceType: c5.4xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ec2-images xenial

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

Title:
  Audio will not play from speakers or headphones after boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On bootup, the bootup ubuntu sound plays.  After ubuntu is fully
  booted, the headphones or audio from speakers will not work.  If I
  change audio output to hdmi and connect headphones to that, sound
  plays as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-1055.64-aws 4.4.117
  Uname: Linux 4.4.0-1055-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  9 20:29:26 2018
  Ec2AMI: ami-da05a4a0
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1a
  Ec2InstanceType: c5.4xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1702495] Re: touchpad too sensitive

[Christopher M. Penalver]

Digjam Sarma, please advise to all of the following:

1) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

2) Did you get a chance to test for this via the daily build as
requested in
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702495/comments/2 ?

** Tags removed: bios-outdated-f.47
** Tags added: bios-outdated-f.49

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

Title:
  touchpad too sensitive

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The mouse cursor moves even when i move my fingers over the touchpad
  in the air(without touching it) but doesnt move at all when i use the
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul  5 20:00:11 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
  InstallationDate: Installed on 2017-06-27 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Hewlett-Packard HP 450 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=159622e6-6a00-43f4-baad-7b2d60cb8bd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3C
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG347B4F2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3C:bd10/11/2013:svnHewlett-Packard:pnHP450NotebookPC:pvr088612005B1600010:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 450 Notebook PC
  dmi.product.version: 088612005B1600010
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jul  5 19:48:09 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 673119] Re: dash "set -e" breaks "trap action INT"

[ZoFreX]

This bug is... now different. But not fixed. Using Dash 0.5.8-2.10, the
output I get from the script is:

3
^CEXIT
Ignored 1
Ignored 2
Back

Note that EXIT fires a lot earlier than expected, and the script
unexpectedly terminates.

I still see similar behaviour to the original bug (only one line is
executed) with this script:

#!/bin/sh
set -e

trap 'exit 1' INT
trap 'sorry' EXIT

sorry() {
  echo "Ignored 1"; echo "Ignored 2"
  sleep 1
  echo Back
}

for i in 3 2 1; do
echo "$i"
sleep 1 # || true
done

echo OUT

Expected output:

3
^CIgnored 1
Ignored 2
Back

Actual output:

3
^CIgnored 1

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

Title:
  dash "set -e" breaks "trap action INT"

Status in dash package in Ubuntu:
  New

Bug description:
  Binary package hint: dash

  With set -e, dash executes only the first command of an INT (Ctrl-C)
  trap handler:

  #!/bin/sh
  set -e

  trap 'sorry' INT
  trap 'echo EXIT' EXIT

  zero() {
return 0;
  }

  sorry() {
#zero
echo "Ignored 1"; echo "Ignored 2"
sleep 1
echo Back
  }

  for i in 3 2 1; do
  echo "$i"
  sleep 1 # || true
  done

  echo OUT

  Actual result:

  $ ./x  # Press ^C right away
  3
  ^CIgnored 1
  EXIT

  Expected result:

  3
  ^CIgnored 1
  Ignored 2
  Back
  2
  1
  OUT
  EXIT

  By un-commenting the call to function zero, or the "|| true" in the
  main loop, the problem disapears.

  Bash also exits prematurely, but at least it runs the "trap INT"
  handler code to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: dash 0.5.5.1-3ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Tue Nov  9 19:12:41 2010
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash

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

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

[Touch-packages] [Bug 1770248] [NEW] console-setup fails intermittently due to a missing file in /tmp

[Dan Watkins]

Public bug reported:

In our testing of cloud images, we intermittently see an error along the
lines of:

May 09 17:59:27 ubuntu setupcon[476]: /bin/setupcon: 809: /bin/setupcon:
cannot open /tmp/tmpkbd.7L3GEu: No such file

This only happens from time-to-time which suggests that it's a race
condition.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: console-setup 1.108ubuntu15.3
ProcVersionSignature: User Name 4.13.0-1015.19-gcp 4.13.16
Uname: Linux 4.13.0-1015-gcp x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed May  9 19:29:50 2018
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images xenial

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

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

Title:
  console-setup fails intermittently due to a missing file in /tmp

Status in console-setup package in Ubuntu:
  New

Bug description:
  In our testing of cloud images, we intermittently see an error along
  the lines of:

  May 09 17:59:27 ubuntu setupcon[476]: /bin/setupcon: 809:
  /bin/setupcon: cannot open /tmp/tmpkbd.7L3GEu: No such file

  This only happens from time-to-time which suggests that it's a race
  condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.3
  ProcVersionSignature: User Name 4.13.0-1015.19-gcp 4.13.16
  Uname: Linux 4.13.0-1015-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  9 19:29:50 2018
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770248] Re: console-setup fails intermittently due to a missing file in /tmp

[Dan Watkins]

The attached `systemd-analyze plot` output suggests that console-setup
ran at the same time as the systemd-tmpfiles-setup service, so I wonder
if this is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846256

** Attachment added: "plot.svg"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1770248/+attachment/5136872/+files/plot.svg

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

Title:
  console-setup fails intermittently due to a missing file in /tmp

Status in console-setup package in Ubuntu:
  New

Bug description:
  In our testing of cloud images, we intermittently see an error along
  the lines of:

  May 09 17:59:27 ubuntu setupcon[476]: /bin/setupcon: 809:
  /bin/setupcon: cannot open /tmp/tmpkbd.7L3GEu: No such file

  This only happens from time-to-time which suggests that it's a race
  condition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.3
  ProcVersionSignature: User Name 4.13.0-1015.19-gcp 4.13.16
  Uname: Linux 4.13.0-1015-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed May  9 19:29:50 2018
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770250] [NEW] xorg hangs, while watching video, or other times

[gregrwm]

Public bug reported:

Xorg hangs, with high usage of CPU, typically around 95%.  This happens
at unpredictable intervals, sometimes 3 times in a day, sometimes not
again for 3 weeks.  Usually while watching videos, which happened this
morning, causing me to submit this report.  This morning, as in several
earlier occurrences, the video image froze except that i was able to
move the mouse cursor, however window borders did not change as they
normally would when the mouse cursor travelled in and out of windows.
Onscreen interactions such as trying to show the twm root menu or move
or iconize windows, or keyboard keys such as ^L to the browser or even
ctl-alt-F2 or ctl-alt-F3 all failed to produce their usual response.  i
was able to login via ssh, attach to tmux, start htop, and observe that
xorg was consuming around 95% CPU.  if you'd like to know what happened
upon killing processes other than xorg, see my recent comments in Bug
#1757299.  This morning i didn't bother to yet again repeat the killing
of other processes, but went straight to sending signal 3 to xorg, after
which ctl-alt-F2 and ctl-alt-F3 were again operational, and i found the
attached report in /var/crash.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog:
 Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  * Starting AppArmor profiles    
[ OK ]
  * Restoring resolver state...    
[ OK ]
Date: Wed May  9 13:23:52 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 755 [1028:0211]
   Subsystem: Dell OptiPlex 755 [1028:0211]
MachineType: Dell Inc. OptiPlex 755
ProcEnviron:
 LC_TIME=en_DK.utf8
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@bb/vmlinuz ro 
root=UUID=22e7c84a-a416-43e9-ae9d-ee0119fc3894 partroot=:b init=/etc/g/subroot 
subroot=@bb panic=30
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0PU052
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex 755
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
xserver.bootTime: Sat Feb 24 05:53:57 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech Logitech USB Optical Mouse MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16421 
 vendor DEL
xserver.version: 2:1.19.6-1ubuntu1

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "found in /var/crash after sending xorg signal 3"
   
https://bugs.launchpad.net/bugs/1770250/+attachment/5136873/+files/_usr_lib_xorg_Xorg.444.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/1770250

Title:
  xorg hangs, while watching video, or other times

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg hangs, with high usage of CPU, typically around 95%.  This
  happens at unpredictable intervals, sometimes 3 times in a day,
  sometimes not again for 3 weeks.  Usually while watching videos, which
  happened this morning, causing me to submit this report.  This
  morning, as in several earlier occurrences, the video image froze
  except that i was able to move the mouse cursor, however window
  borders did not change as they normally would when the mouse cursor
  travelled in and out of windows.  Onscreen interactions such as trying
  to show the twm root menu or move or iconize windows, or keyboard keys
  such as ^L to the browser or even ctl-alt-F2 or 

[Touch-packages] [Bug 1770224] Re: unattended-upgrades crashes with: apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages

[Julian Andres Klode]

That backtracr is something completely different. So what is this about,
the locking failure or the resolver? Resolver failures are probably not
going to be fixable, or only with guessing and extreme caution.

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

Title:
  unattended-upgrades crashes with: apt_pkg.Error: E:Error,
  pkgProblemResolver::Resolve generated breaks, this may be caused by
  held packages

Status in apt package in Ubuntu:
  New

Bug description:
  It seems pkgProblemResolver is hitting an internal bug quite
  frequently with latest u-u:

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1822, in main
  options.dry_run)
File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
  res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 513, in cache_commit
  res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
  res = self._fetch_archives(fetcher, pm)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in 
_fetch_archives
  raise LockFailedException("Failed to lock %s" % lockfile)
  apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock

  
  I believe this should be fixed in apt rather than just catching it in u-u.

  More info:

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

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

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

[Touch-packages] [Bug 1748656] Re: Black Screen of Death after logging into Ubuntu Bionic: "Failed to acquire modesetting permission"

[Jonathan]

Created new bug. Seems very similar to this one.
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238

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

Title:
  Black Screen of Death after logging into Ubuntu Bionic: "Failed to
  acquire modesetting permission"

Status in xorg package in Ubuntu:
  Expired

Bug description:
  **Specs:** Ubuntu Bionic; NVidia GTX 1070 w/`nvidia-387` drivers.

  **Problem:** After installing a new GTX 1070 and installing
  `nvidia-387`, I get a black screen of death AFTER logging into Ubuntu
  (i.e., the login screen shows up just fine). I'm not even able to
  access other TTYs (the error logs below were retrieved via SSH).

  **/var/log/Xorg.0.log** There doesn't seem to be anything problematic
  in this file.

  **/var/log/Xorg.1.log** The problematic message seems to be:

  [26.455] (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
  [26.455] (EE) NVIDIA(0): Failing initialization of X screen 0
  [26.455] (II) UnloadModule: "nvidia"
  [26.455] (II) UnloadSubModule: "wfb"
  [26.455] (II) UnloadSubModule: "fb"
  [26.455] (EE) Screen(s) found, but none have a usable configuration.
  [26.455] (EE) 
  Fatal server error:
  [26.455] (EE) no screens found(EE) 
  [26.455] (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  [26.455] (EE) Please also check the log file at "/var/log/Xorg.1.log" 
for additional information.
  [26.455] (EE) 
  [26.457] (EE) Server terminated with error (1). Closing log file.

  **Conf files.** Here are my conf files:

  $ cd /usr/share/X11
  $ find . -name "*.conf"
  ./xorg.conf.d/glamoregl.conf
  ./xorg.conf.d/10-amdgpu.conf
  ./xorg.conf.d/40-libinput.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm-outputclass.conf
  ./xorg.conf.d/10-quirks.conf
  ./xorg.conf.d/10-radeon.conf
  ./xorg.conf.d/70-wacom.conf

  I tried deleting all of these except for the nvidia one and rebooting,
  and the error persists. In addition, I tried deleting all of them and
  generating a new one via `sudo X -configure` but get

  $ cd /usr/share/X11$ 
  $ sudo pkill X && sudo X -configure  
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
  _XSERVTransMakeAllCOTSServerListeners: server already running
  (EE) 
  Fatal server error:
  (EE) Cannot establish any listening sockets - Make sure an X server isn't 
already running(EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.

  **kms.** Finally, in case relevant:

  $ lsmod | grep kms
  drm_kms_helper167936  1 nvidia_drm
  syscopyarea16384  1 drm_kms_helper
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  drm   356352  6 nvidia_drm,drm_kms_helper

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Feb 10 13:14:48 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-25-generic, x86_64: installed
   nvidia-387, 387.34, 4.13.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 

[Touch-packages] [Bug 1743998] Re: Renewal of the DHCP lease causes an interface down/up event

[Launchpad Bug Tracker]

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

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

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

Title:
  Renewal of the DHCP lease causes an interface down/up event

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Based on a DHCPACK the client receives it determines a renewal time,
  which is 1/2 (+- some randomness) of the lease time provided by the
  DHCP server. After this time the client sends a new DHCPREQUEST. In my
  case the same DHCP server responds while providing the same IP address
  (in my case preconfigured in a customer environment). This one is
  being reassigned to the interface, resulting in a short link down /
  link up sequence (see syslog below):

  Jan 17 16:52:25 krombacher dhclient[2053]: DHCPREQUEST of 10.225.6.25 on 
wlan0 to 10.225.6.1 port 67 (xid=0x)
  Jan 17 16:52:25 krombacher dhclient[2053]: DHCPACK of 10.225.6.25 from 
10.225.6.1
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
address 10.225.6.25
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
plen 24 (255.255.255.0)
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
gateway 10.225.6.1
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
server identifier 10.225.6.1
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
lease time 10800
  Jan 17 16:52:25 krombacher vmnet-natd: RTM_NEWADDR: index:3, addr:10.225.6.25
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
hostname 'krombacher'
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
nameserver '8.8.8.8'
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307]   
nameserver '8.8.4.4'
  Jan 17 16:52:25 krombacher NetworkManager[1301]:   [1516204345.1307] 
dhcp4 (wlan0): state changed bound -> bound
  Jan 17 16:52:25 krombacher dbus[1216]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
  Jan 17 16:52:25 krombacher dhclient[2053]: bound to 10.225.6.25 -- renewal in 
4326 seconds.
  Jan 17 16:52:25 krombacher systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan 17 16:52:25 krombacher dbus[1216]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan 17 16:52:25 krombacher systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan 17 16:52:25 krombacher nm-dispatcher: req:1 'dhcp4-change' [wlan0]: new 
request (1 scripts)
  Jan 17 16:52:25 krombacher nm-dispatcher: req:1 'dhcp4-change' [wlan0]: start 
running ordered scripts...
  Jan 17 16:52:25 krombacher kernel: [29622.756223] userif-3: sent link down 
event.
  Jan 17 16:52:25 krombacher kernel: [29622.756227] userif-3: sent link up 
event.

  As a side effect, my running Cisco Connect Anywhere VPN client gets a
  disconnect event and reconnects again. This will cause a drop of all
  my open ssh, vnc, Oracle, ... sessions.

  Isn't it possible to identify that the IP address is the same as the
  one currently set and to skip this rebinding procedure?

  System details:
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  isc-dhcp-client/xenial-updates,now 4.3.3-5ubuntu12.7 
  isc-dhcp-common/xenial-updates,now 4.3.3-5ubuntu12.7

  Thanks,
  Christian

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

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

[Touch-packages] [Bug 1761743] Re: Xorg crash, session logout after screen turned off

[JB Duck-Mayr]

Also affected on Ubuntu MATE 18.04 (i.e., it's not just vanilla Ubuntu
with GNOME).

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

Title:
  Xorg crash, session logout after screen turned off

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Session logout after screen turned off and also logout during work

  May be related to Bug 1721428

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:52:02 2018
  DistUpgraded: 2018-04-02 12:05:40,293 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.10.0, 4.13.0-37-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.13.0-37-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 510 
[1462:7996]
  InstallationDate: Installed on 2017-03-02 (400 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd 
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7996
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=fa8af88c-68e6-4582-872e-a2c53edcbf97 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (4 days ago)
  dmi.bios.date: 07/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M PRO-VD (MS-7996)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7996
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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-1ubuntu3
  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/+source/xorg/+bug/1761743/+subscriptions

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

[Touch-packages] [Bug 1769297] Re: resume from hibernation broken when resume image is autodetected

[Brian Murray]

** Tags added: regression-release

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  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/1769297/+subscriptions

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

[Touch-packages] [Bug 1769385] Re: "text" errors when running Apport

[Brian Murray]

** Tags added: kubuntu

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

Title:
  "text" errors when running Apport

Status in apport package in Ubuntu:
  New

Bug description:
  When reporting a bug against SDDM (ubuntu-bug sddm) Apport displayed
  an error dialog box with only "text" message. See the screenshot.

  The error should be more descriptive.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   ERROR: apport (pid 5672) Sat May  5 16:51:48 2018: host pid 1566 crashed in 
a separate mount namespace, ignoring
   ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: called for pid 3084, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: executable was modified 
after program start, ignoring
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May  5 20:23:29 2018
  InstallationDate: Installed on 2015-05-01 (1099 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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

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

[Touch-packages] [Bug 1761743] Re: Xorg crash, session logout after screen turned off

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg crash, session logout after screen turned off

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Session logout after screen turned off and also logout during work

  May be related to Bug 1721428

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  6 15:52:02 2018
  DistUpgraded: 2018-04-02 12:05:40,293 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.10.0, 4.13.0-37-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.13.0-37-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 510 
[1462:7996]
  InstallationDate: Installed on 2017-03-02 (400 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a2c:2124 China Resource Semico Co., Ltd 
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7996
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=fa8af88c-68e6-4582-872e-a2c53edcbf97 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (4 days ago)
  dmi.bios.date: 07/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M PRO-VD (MS-7996)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7996
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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-1ubuntu3
  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/+source/xorg/+bug/1761743/+subscriptions

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

[Juha Luoma]

Hit this problem after updated Ubuntu 17.10 -> 18.04 on my old Dell
Latitude E6400 laptop.

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1767292] Re: The bluetooth mouse cannot connect after sleep mode.

[Launchpad Bug Tracker]

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

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

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

Title:
  The bluetooth mouse cannot connect after sleep mode.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bluetooth mouse cannot connect after sleep mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giacomo1998 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Apr 27 09:49:41 2018
  InstallationDate: Installed on 2017-04-13 (378 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago)
  dmi.bios.date: 07/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R08ET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FU001PMC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L460
  dmi.product.name: 20FU001PMC
  dmi.product.version: ThinkPad L460
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1770224] Re: unattended-upgrades crashes with: apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages

[Balint Reczey]

** Summary changed:

- 
/usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1927:main:mark_upgrade:mark_install
+ unattended-upgrades crashes with: apt_pkg.Error: E:Error, 
pkgProblemResolver::Resolve generated breaks, this may be caused by held 
packages

** Description changed:

+ It seems pkgProblemResolver is hitting an internal bug quite frequently
+ with latest u-u:
+ 
+ Traceback (most recent call last):
+   File "/usr/bin/unattended-upgrade", line 1927, in 
+ sys.exit(main(options))
+   File "/usr/bin/unattended-upgrade", line 1822, in main
+ options.dry_run)
+   File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
+ res, error = cache_commit(cache, logfile_dpkg, verbose)
+   File "/usr/bin/unattended-upgrade", line 513, in cache_commit
+ res = cache.commit(install_progress=iprogress)
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
+ res = self._fetch_archives(fetcher, pm)
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in 
_fetch_archives
+ raise LockFailedException("Failed to lock %s" % lockfile)
+ apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock
+ 
+ 
+ I believe this should be fixed in apt rather than just catching it in u-u.
+ 
+ More info:
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/49de8d44b4ceccb27b66921173ee7e837e7a1e54 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Package changed: unattended-upgrades (Ubuntu) => apt (Ubuntu)

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

Title:
  unattended-upgrades crashes with: apt_pkg.Error: E:Error,
  pkgProblemResolver::Resolve generated breaks, this may be caused by
  held packages

Status in apt package in Ubuntu:
  New

Bug description:
  It seems pkgProblemResolver is hitting an internal bug quite
  frequently with latest u-u:

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1822, in main
  options.dry_run)
File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
  res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 513, in cache_commit
  res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
  res = self._fetch_archives(fetcher, pm)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in 
_fetch_archives
  raise LockFailedException("Failed to lock %s" % lockfile)
  apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock

  
  I believe this should be fixed in apt rather than just catching it in u-u.

  More info:

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

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

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

[Touch-packages] [Bug 1770224] [NEW] unattended-upgrades crashes with: apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages

[errors.ubuntu.com bug bridge]

Public bug reported:

It seems pkgProblemResolver is hitting an internal bug quite frequently
with latest u-u:

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1927, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1822, in main
options.dry_run)
  File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
res, error = cache_commit(cache, logfile_dpkg, verbose)
  File "/usr/bin/unattended-upgrade", line 513, in cache_commit
res = cache.commit(install_progress=iprogress)
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
res = self._fetch_archives(fetcher, pm)
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in 
_fetch_archives
raise LockFailedException("Failed to lock %s" % lockfile)
apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock


I believe this should be fixed in apt rather than just catching it in u-u.

More info:

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

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


** Tags: bionic

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

Title:
  unattended-upgrades crashes with: apt_pkg.Error: E:Error,
  pkgProblemResolver::Resolve generated breaks, this may be caused by
  held packages

Status in apt package in Ubuntu:
  New

Bug description:
  It seems pkgProblemResolver is hitting an internal bug quite
  frequently with latest u-u:

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1822, in main
  options.dry_run)
File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
  res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 513, in cache_commit
  res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
  res = self._fetch_archives(fetcher, pm)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in 
_fetch_archives
  raise LockFailedException("Failed to lock %s" % lockfile)
  apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock

  
  I believe this should be fixed in apt rather than just catching it in u-u.

  More info:

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

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

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

[Touch-packages] [Bug 1770225] [NEW] package libperl5.26 5.26.1-6 failed to install/upgrade: próba nadpisania dzielonego "/usr/share/doc/libperl5.26/changelog.Debian.gz", który różni się od innych kop

[utom]

Public bug reported:

The error message appeared when the Simple Scanning tool completed its
task. (Before saving the result.)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libperl5.26 5.26.1-6
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May  9 19:11:09 2018
ErrorMessage: próba nadpisania dzielonego 
"/usr/share/doc/libperl5.26/changelog.Debian.gz", który różni się od innych 
kopii pakietu libperl5.26:i386
InstallationDate: Installed on 2016-07-28 (650 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
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: perl
Title: package libperl5.26 5.26.1-6 failed to install/upgrade: próba nadpisania 
dzielonego "/usr/share/doc/libperl5.26/changelog.Debian.gz", który różni się od 
innych kopii pakietu libperl5.26:i386
UpgradeStatus: Upgraded to bionic on 2018-04-07 (32 days ago)

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

Title:
  package libperl5.26 5.26.1-6 failed to install/upgrade: próba
  nadpisania dzielonego
  "/usr/share/doc/libperl5.26/changelog.Debian.gz", który różni się od
  innych kopii pakietu libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  The error message appeared when the Simple Scanning tool completed its
  task. (Before saving the result.)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 19:11:09 2018
  ErrorMessage: próba nadpisania dzielonego 
"/usr/share/doc/libperl5.26/changelog.Debian.gz", który różni się od innych 
kopii pakietu libperl5.26:i386
  InstallationDate: Installed on 2016-07-28 (650 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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: perl
  Title: package libperl5.26 5.26.1-6 failed to install/upgrade: próba 
nadpisania dzielonego "/usr/share/doc/libperl5.26/changelog.Debian.gz", który 
różni się od innych kopii pakietu libperl5.26:i386
  UpgradeStatus: Upgraded to bionic on 2018-04-07 (32 days ago)

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

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

[Touch-packages] [Bug 1770163] Re: my system crashed when i try to open android emulator

[dino99]

** Tags removed: 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/1770163

Title:
  my system crashed when i try to open android emulator

Status in systemd package in Ubuntu:
  New

Bug description:
  I was just trying to install android studio from software center
  unfortunately i could not do that. So then I download it from official
  web site then installed it. After installation is completed i was just
  try to open android emulator then my system began work slower and
  slower and i got this error "Your computer does not have enough free
  memory to automatically analyze the problem and send a report to the
  developers" then i try to send report via terminal.

  System information: 
RAM: 12 GB
processor: intel core i5-4200H CPU @ 2.80GHz x 4
graphics: llvmpipe (LLVM 5.0, 256 bits)
OS type: 64-bit
disk: 725,6 GB 

  package version: android studio 3.1.2 for Linux 64-bit (853 MB) (from
  official web site of android studio)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  9 15:32:25 2018
  InstallationDate: Installed on 2018-05-04 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[iuuuuan]

I have finally getting to work my ubuntu 18.04 with drivers installed
from additional drivers.

After update from ubuntu 17.10 to 18.04 nvidia-390 drivers were
installed, nvidia-340 package was metapackage for nvidia-390.

Today I was able to install nvidia-340.106 driver directly from
additional drivers, but they unfortunately did not work.

I have described method how to compile nvidia-340.104 for kernel 4.15 in
#114 and this worked without problems.

I did comparison of nvidia-340.104 and nvidia-340.106 and found out that in 
nvidia-340.106 driver has fix for issue between the NVIDIA kernel driver's Page 
Attribute Table (PAT) support and the KPTI page table isolation.
no

After few tries with different kernel settings I have noticed that I
have nopat option enabled in grub kernel boot.

Simple fix for that was to remove nopat option in grub

1. Open grub configuration file /etc/default/grub
# sudo vi /etc/default/grub

or

# sudo nano /etc/default/grub

2. Remove nopat from GRUB_CMDLINE_LINUX_DEFAULT

My current options looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw"

3. Save file and exit editor

4. Update grub configuration

# sudo update-grub2

5. Reboot
# sudo reboot

6. Install recommended drivers
# sudo ubuntu-drivers autoinstall

7. Reboot
# sudo reboot

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Jordan Piel]

This also breaks Shibboleth since libapache2-mod-shib2 has a dependency
on libxmltooling7 which depends on libcurl3.

sudo apt install libapache2-mod-shib2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libapache2-mod-shib2 : Depends: libshibsp-plugins (= 2.6.1+dfsg1-2) but it is 
not going to be installed
Depends: shibboleth-sp2-utils (>= 2.6)
Depends: libshibsp7 but it is not going to be installed
Depends: libxmltooling7 (>= 1.6.0-5) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

If installing libcurl3 alongside libcurl4 was possible this wouldn't be
an issue. Why is this not a high priority? It makes 18.04 unstable at
best.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1770163] Re: my system crashed when i try to open android emulator

[Ubuntu Foundations Team Bug Bot]

The attachment "error" seems to be a patch.  If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

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

Title:
  my system crashed when i try to open android emulator

Status in systemd package in Ubuntu:
  New

Bug description:
  I was just trying to install android studio from software center
  unfortunately i could not do that. So then I download it from official
  web site then installed it. After installation is completed i was just
  try to open android emulator then my system began work slower and
  slower and i got this error "Your computer does not have enough free
  memory to automatically analyze the problem and send a report to the
  developers" then i try to send report via terminal.

  System information: 
RAM: 12 GB
processor: intel core i5-4200H CPU @ 2.80GHz x 4
graphics: llvmpipe (LLVM 5.0, 256 bits)
OS type: 64-bit
disk: 725,6 GB 

  package version: android studio 3.1.2 for Linux 64-bit (853 MB) (from
  official web site of android studio)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  9 15:32:25 2018
  InstallationDate: Installed on 2018-05-04 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

[Michael von Glasow]

I upgraded to 18.04 last week. So far none of the screen issues (black
screen or image corruption) has reappeared; I will post an update if
anything comes up.

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  New

Bug description:
  Once every couple hours, the internal laptop display goes black for a
  few seconds.

  This was reproducible:
  + With the laptop connected to a port replicator and the external display 
connected into the port replicator DP port via DP-DVI adapter. The external 
display remains on during this time.
  + With the laptop not connected into a port replicator but connected to an 
external display. The external display remains on during this time.
  + With the laptop not connected to either a port replicator or an external 
display.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1. The problem started immediately
  after the drive move.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  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]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

Investigating, it appears that the interfaces are getting renamed by
udev in the initramfs, which pushes their name_assign_type value to 4,
and udev refuses to rename an interface if the name_assign_type value is
4.

So, I can make this scenario work if I do:

4. sudo update-initramfs -u
5. reboot

After rebooting, the interface is correct.

I'll add a systemd task here in case we want to poke at allowing renames
even if assign-type is 4.

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770210] [NEW] package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Daniel U. Thibault]

Public bug reported:

Upgrading from 14.04.5 to 16.04.4.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Wed May  9 12:18:48 2018
DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
InstallationDate: Installed on 2017-01-17 (477 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.18
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
UpgradeStatus: Upgraded to xenial on 2018-05-09 (0 days ago)

** Affects: shared-mime-info (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 shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1770210

Title:
  package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le
  sous-processus script post-installation installé a retourné une erreur
  de sortie d'état 1

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Upgrading from 14.04.5 to 16.04.4.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Wed May  9 12:18:48 2018
  DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2017-01-17 (477 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to xenial on 2018-05-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1770210/+subscriptions

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

[Touch-packages] [Bug 1770210] Re: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le
  sous-processus script post-installation installé a retourné une erreur
  de sortie d'état 1

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Upgrading from 14.04.5 to 16.04.4.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Wed May  9 12:18:48 2018
  DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2017-01-17 (477 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.18
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to xenial on 2018-05-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1770210/+subscriptions

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

[Touch-packages] [Bug 1770163] Re: my system crashed when i try to open android emulator

[Olivier Tilloy]

Per attached screenshot, what crashed is systemd-logind.

** Package changed: chromium-browser (Ubuntu) => systemd (Ubuntu)

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

Title:
  my system crashed when i try to open android emulator

Status in systemd package in Ubuntu:
  New

Bug description:
  I was just trying to install android studio from software center
  unfortunately i could not do that. So then I download it from official
  web site then installed it. After installation is completed i was just
  try to open android emulator then my system began work slower and
  slower and i got this error "Your computer does not have enough free
  memory to automatically analyze the problem and send a report to the
  developers" then i try to send report via terminal.

  System information: 
RAM: 12 GB
processor: intel core i5-4200H CPU @ 2.80GHz x 4
graphics: llvmpipe (LLVM 5.0, 256 bits)
OS type: 64-bit
disk: 725,6 GB 

  package version: android studio 3.1.2 for Linux 64-bit (853 MB) (from
  official web site of android studio)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  9 15:32:25 2018
  InstallationDate: Installed on 2018-05-04 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770195] [NEW] OpenSSL missing ciphers

[Florian Lentz]

Public bug reported:

In OpenSSL 1.1.0 several ciphers were simply removed. They can be re-
enabled by using "enable-weak-ssl-ciphers" option when building. This
should be done to increase compatibility.

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

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

Title:
  OpenSSL missing ciphers

Status in openssl package in Ubuntu:
  New

Bug description:
  In OpenSSL 1.1.0 several ciphers were simply removed. They can be re-
  enabled by using "enable-weak-ssl-ciphers" option when building. This
  should be done to increase compatibility.

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

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

[Touch-packages] [Bug 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs

[Andrej Shadura]

I'm also affected by this bug on a normal Ubuntu. Times out the same way
in initramfs.

Interestingly, this doesn't seem to happen with another installation of
Ubuntu here.

Cc @vorlon

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

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

Title:
  Lubuntu bionic boots slower than the other Ubuntu flavours with some
  SSDs

Status in initramfs-tools package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  See this thread at the Ubuntu Forums:

  https://ubuntuforums.org/showthread.php?t=2388799

  How come the ultra light Lubuntu Bionic needs 40 seconds from the grub
  menu to the log in screen, while the corresponding Kubuntu and Xubuntu
  Bionic can do it in 10 seconds in my Toshiba laptop?

  All the operating systems were installed from the Bionic Beta-2
  desktop 64-bit iso files and made up to date today (and reside in a
  new SSD connected via the internal SATA bay).

  -o-

  and to summarize the conclusion

  
https://ubuntuforums.org/showthread.php?t=2388799=2=13756324#post13756324

  This supports the assumption, that there are problems for Lubuntu to
  manage SSDs with 4096 byte size physical sectors. But the other
  flavours of Ubuntu can manage it.

  Let us hope that this can help the Lubuntu developer to find and
  squash the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lubuntu-desktop 0.93
  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
  CurrentDesktop: LXDE
  Date: Fri Apr 13 09:59:42 2018
  InstallationDate: Installed on 2018-04-06 (7 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405)
  SourcePackage: lubuntu-meta
  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/1763611/+subscriptions

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

[Touch-packages] [Bug 1770163] Re: my system crashed when i try to open android emulator

[Olivier Tilloy]

Note that android studio is available as a snap package, you might want
to give it a try:

snap install android-studio --classic

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

Title:
  my system crashed when i try to open android emulator

Status in systemd package in Ubuntu:
  New

Bug description:
  I was just trying to install android studio from software center
  unfortunately i could not do that. So then I download it from official
  web site then installed it. After installation is completed i was just
  try to open android emulator then my system began work slower and
  slower and i got this error "Your computer does not have enough free
  memory to automatically analyze the problem and send a report to the
  developers" then i try to send report via terminal.

  System information: 
RAM: 12 GB
processor: intel core i5-4200H CPU @ 2.80GHz x 4
graphics: llvmpipe (LLVM 5.0, 256 bits)
OS type: 64-bit
disk: 725,6 GB 

  package version: android studio 3.1.2 for Linux 64-bit (853 MB) (from
  official web site of android studio)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  9 15:32:25 2018
  InstallationDate: Installed on 2018-05-04 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770163] [NEW] my system crashed when i try to open android emulator

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I was just trying to install android studio from software center
unfortunately i could not do that. So then I download it from official
web site then installed it. After installation is completed i was just
try to open android emulator then my system began work slower and slower
and i got this error "Your computer does not have enough free memory to
automatically analyze the problem and send a report to the developers"
then i try to send report via terminal.

System information: 
  RAM: 12 GB
  processor: intel core i5-4200H CPU @ 2.80GHz x 4
  graphics: llvmpipe (LLVM 5.0, 256 bits)
  OS type: 64-bit
  disk: 725,6 GB 

package version: android studio 3.1.2 for Linux 64-bit (853 MB) (from
official web site of android studio)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May  9 15:32:25 2018
InstallationDate: Installed on 2018-05-04 (5 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial
-- 
my system crashed when i try to open android emulator
https://bugs.launchpad.net/bugs/1770163
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1769297] Re: resume from hibernation broken when resume image is autodetected

[Launchpad Bug Tracker]

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

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

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  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/1769297/+subscriptions

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

[Touch-packages] [Bug 1644975] Re: Resume from disk (swapfile) fails

[Andrej Shadura]

@superm1, your fix makes the boot process very slow on one of the
machines, it takes a minute or more for it to time out waiting for the
resume device.

People also complain here: https://askubuntu.com/questions/1013830/slow-
boot-long-kernel-load-time-due-to-wrong-resume-device

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

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Incomplete

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

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

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

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

On Wed, May 9, 2018 at 9:13 AM, Daniel Axtens
 wrote:
> Ryan: I removed /etc/netplan/50-cloud-init.yaml and rebooted repeatedly and
> I've never seen it regenerated.

Ah, right, it doesn't regenerate unless you change instance-ids.

>
> I also don't see anything in /run/netplan or /run/systemd/network that has
> been autogenerated.
>
> I haven't touched anything else generated by cloud-init. When would
> cloud-init regenerate a network config file?

Nothing, you're right.  You can make a local change and reboot but typically
for cloud instances you'd want to have it set during the first boot.

So your scenario is:

1) deploy instance
2) log in and modify /etc/netplan/50-cloud-init.yaml to add a set-name:
3) reboot?

And the result is that you don't see a name change?

Yes, I think this is the udev scenario where it won't change a device
name whose 'name_assign_type' is either 3 or 4;

The driver unplug code in netplan is designed to workaround this
design issue with udev itself.

Can you confirm the driver for the interface you're renaming? ethtool
-i 



>
> --
> You received this bug notification because you are subscribed to
> netplan.
> Matching subscriptions: netplan
> https://bugs.launchpad.net/bugs/1770082
>
> Title:
>   systemd-networkd not renaming devices on boot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are 

[Touch-packages] [Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key

[Lars Kollstedt]

Hi Markus,

this was originally a Bug about SHA-1 signed repositories in local0
breaking the entire installation. The Error messages displayed,
where/are not really good, changing to the shell of the install system,
and having a look at /var/log/syslog there shows more.

This was in 2016 and mainly a topic for xenial. But if you are still
using SHA1 signed repositories this will affect you in some way in any
newer release, too. Bionic removes any repositories that have invalid
keys, whereas xenial fails to install the base system because all
repositories where not loaded.

The missing gnupg tools are affecting bionic, I would wonder if this will 
affect artful, too. For xenial this is definitely working.
The missing gnupg tools are discussed in Bug #1754075 for bionic. There are two 
ways to fix. As far as I know none of them has been applied, yet.

This bug is not duplicated and IMHO not really solved, but it has lost
importance since SHA-1 signed repositories are getting rarer.

Kind regards
   Lars

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

Title:
  Xenial preseed fails to load key for 3rd party repo with apt-
  setup/local0/key

Status in apt-setup package in Ubuntu:
  Confirmed
Status in base-installer package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed
Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  I have an automated preseed installation that uses these lines to add
  custom repos during the installation:

  d-i apt-setup/local0/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local0/comment string JTS local repository
  d-i apt-setup/local0/source boolean false
  d-i apt-setup/local0/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local1/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local1/comment string Google Chrome Browser
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string 
http://dl.google.com/linux/linux_signing_key.pub

  
(seehttps://github.com/jschule/ubuntu/blob/d46f1cef49ed71dc4bfe317119cccd3f39097ef4/preseed/jts.txt
  for complete preseed file that causes the problem).

  In xenial the installation fails because the GPG key for the local0
  repo is not loaded into the system so that it can be used (see
  screenshot). Strangely, "chroot /target apt-key list" shows the key
  9E62229E to be installed.

  Just to be sure that there is no problem with my repo and key I
  started the Xenial live CD and installed my repo there manually. All
  works well. IMHO this shows that the problem is clearly related to the
  automated installation with preseed.

  Maybe this is related to #1512347, that was the only thing I could
  find on Launchpad that is in the same area.

  If you want to reproduce this then you can checkout the scripts from
  https://github.com/jschule/ubuntu/tree/gh-pages/qemu and run "./run.sh
  xenial" to start my installation.

  I found a very ugly workaround by changing the apt-setup lines to
  this:

  d-i apt-setup/local0/repository string deb 
http://archive.canonical.com/ubuntu trusty partner
  d-i apt-setup/local0/source boolean false

  d-i apt-setup/local1/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local1/comment string JTS local repository
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local2/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local2/comment string Google Chrome Browser
  d-i apt-setup/local2/source boolean false
  d-i apt-setup/local2/key string 
http://dl.google.com/linux/linux_signing_key.pub

  I suppose that the workaround works because now the local0 repo is one
  where the signing key is already part of Ubuntu. I just hope that
  there is no package in the trusty partner repo that is not also in the
  xenial partner repo.

  For me it is very important that you fix this bug before 16.04 is
  released so that I can continue to use Ubuntu with an automated setup.

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

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

[Touch-packages] [Bug 1770176] [NEW] Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.

[Antonio Marra]

Public bug reported:

In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on 
my Dell XPS 15.
This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
When I boot Ubuntu with the adapter plugged in, the wired connection section in 
the top right menu doesn't show the "Via cavo collegato" section (in Italian, 
sorry... maybe in English it is "Through connected cable") in the correct way, 
often but not every time...
The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

Another strange behaviour occours with the "VPN" section in the same topright 
menu.
I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

It seems there is some trouble in the topright menu communication with
the NetworkManager subsystem.

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

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

Title:
  Ubuntu 18.04 - NetworkManager menu items in top right menu behaves
  very strange.

Status in network-manager package in Ubuntu:
  New

Bug description:
  In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour 
on my Dell XPS 15.
  This laptop doesn't have an integrated Ethernet port, so I've to use external 
USB 3.0 Ethernet adapters.
  When I boot Ubuntu with the adapter plugged in, the wired connection section 
in the top right menu doesn't show the "Via cavo collegato" section (in 
Italian, sorry... maybe in English it is "Through connected cable") in the 
correct way, often but not every time...
  The menu section title is sometimes " collegato" and expanding the section it 
doesn't list all the defined Ethernet connection profiles I've on my machine.
  To access all profiles and to change it I've to select the "Wired network 
settings" item in the section and so the system settings window appears and all 
defined profiles are there (so I can change connection by clicking here).

  Another strange behaviour occours with the "VPN" section in the same topright 
menu.
  I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN 
type). If I select one of this two profiles, VPN connection is established but 
the switch button in the menu doesn't reflect the state of the connection. To 
see the correct state of the VPN connection I've to open the "system settings" 
window, again.

  It seems there is some trouble in the topright menu communication with
  the NetworkManager subsystem.

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

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

[Touch-packages] [Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key

[Markus Wigge]

I can confirm that bionic is affected too.

Maybe the installer image is missing some gnupg tools? I observed that
with a minimal install I cannot use "apt-key" within the installed
system because there is no gnupg installed at all.

This is really disappointing.

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

Title:
  Xenial preseed fails to load key for 3rd party repo with apt-
  setup/local0/key

Status in apt-setup package in Ubuntu:
  Confirmed
Status in base-installer package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed
Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  I have an automated preseed installation that uses these lines to add
  custom repos during the installation:

  d-i apt-setup/local0/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local0/comment string JTS local repository
  d-i apt-setup/local0/source boolean false
  d-i apt-setup/local0/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local1/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local1/comment string Google Chrome Browser
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string 
http://dl.google.com/linux/linux_signing_key.pub

  
(seehttps://github.com/jschule/ubuntu/blob/d46f1cef49ed71dc4bfe317119cccd3f39097ef4/preseed/jts.txt
  for complete preseed file that causes the problem).

  In xenial the installation fails because the GPG key for the local0
  repo is not loaded into the system so that it can be used (see
  screenshot). Strangely, "chroot /target apt-key list" shows the key
  9E62229E to be installed.

  Just to be sure that there is no problem with my repo and key I
  started the Xenial live CD and installed my repo there manually. All
  works well. IMHO this shows that the problem is clearly related to the
  automated installation with preseed.

  Maybe this is related to #1512347, that was the only thing I could
  find on Launchpad that is in the same area.

  If you want to reproduce this then you can checkout the scripts from
  https://github.com/jschule/ubuntu/tree/gh-pages/qemu and run "./run.sh
  xenial" to start my installation.

  I found a very ugly workaround by changing the apt-setup lines to
  this:

  d-i apt-setup/local0/repository string deb 
http://archive.canonical.com/ubuntu trusty partner
  d-i apt-setup/local0/source boolean false

  d-i apt-setup/local1/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local1/comment string JTS local repository
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local2/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local2/comment string Google Chrome Browser
  d-i apt-setup/local2/source boolean false
  d-i apt-setup/local2/key string 
http://dl.google.com/linux/linux_signing_key.pub

  I suppose that the workaround works because now the local0 repo is one
  where the signing key is already part of Ubuntu. I just hope that
  there is no package in the trusty partner repo that is not also in the
  xenial partner repo.

  For me it is very important that you fix this bug before 16.04 is
  released so that I can continue to use Ubuntu with an automated setup.

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

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

Re: [Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Anmar Oueja]

Awesome!... Thanks Daniel.

On Wed, May 9, 2018 at 6:01 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Now available for testing:
>
> https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
>
> Only cosmic is expected to get 5.49 but the above PPA also provides it
> for bionic if you want to try it out without changing the whole OS :)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1759628
>
> Title:
>bluez regression: Bluetooth audio fails to reconnect after resume
>
> Status in bluez package in Ubuntu:
>   In Progress
> Status in bluez package in Fedora:
>   Fix Released
> Status in Suse:
>   Fix Released
>
> Bug description:
>   STEPS TO REPRODUCE:
>   1. Connect to Bluetooth audio device
>   2. Suspend & Resume
>   3. Reconnect to Bluetooth device.
>
>   This regression in bluez 5.48 has already been identified and fixed
>   upstream. Report is here    bluetooth=151616078627045=2> and patch is here
>   <
> https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=d6e9539e31c6bb5afd39ec6f09c518d232e6345d
> >.
>
>   Syslog reports messages as follows when this issue is happening (I have
> replaced my device's MAC address with [MAC]):
>   Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c:
> Information about device /org/bluez/hci0/dev_[MAC] is invalid
>   Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error:
> org.bluez.Error.InvalidArguments
>   Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c:
> Information about device /org/bluez/hci0/dev_[MAC] is invalid
>   Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error:
> org.bluez.Error.InvalidArguments
>
>   Workaround is to run sudo systemctl restart bluetooth after resume.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: bluez 5.48-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
>   Uname: Linux 4.15.0-12-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu1
>   Architecture: amd64
>   CurrentDesktop: KDE
>   Date: Wed Mar 28 12:37:11 2018
>   InstallationDate: Installed on 2018-03-23 (5 days ago)
>   InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180306.1)
>   InterestingModules: rfcomm bnep btusb bluetooth
>   MachineType: Hewlett-Packard HP ProBook 640 G1
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic
> root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
>   SourcePackage: bluez
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/25/2018
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: L78 Ver. 01.43
>   dmi.board.name: 2101
>   dmi.board.vendor: Hewlett-Packard
>   dmi.board.version: KBC Version 16.3C
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias:
> dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
>   dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
>   dmi.product.name: HP ProBook 640 G1
>   dmi.product.version: A3009DD10303
>   dmi.sys.vendor: Hewlett-Packard
>   hciconfig:
>hci0:Type: Primary  Bus: USB
> BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
> UP RUNNING PSCAN
> RX bytes:5025 acl:32 sco:0 events:202 errors:0
> TX bytes:5785 acl:32 sco:0 commands:103 errors:0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions
>

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: 

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

Ryan: I removed /etc/netplan/50-cloud-init.yaml and rebooted repeatedly and
I've never seen it regenerated.

I also don't see anything in /run/netplan or /run/systemd/network that has
been autogenerated.

I haven't touched anything else generated by cloud-init. When would
cloud-init regenerate a network config file?

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start

[ChristianEhrhardt]

1. Upgrade from proposed - this is the same for all associated bugs, so
I only documented details in bug 1741390

2. This bug in particular
Running a few restarts and checking
$ systemctl status -l open-vm-tools.service
This checks if the service rules avoid the issue on these systems with older 
systemd (older than Bionic where these extra constraints are not needed)

Artful: did not expose the issue in 5/5 retries
Xenial: did not expose the issue in 5/5 retries

Per above (and the extensive precheck on the content-equal ppa by
VMWare) - setting to verified

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

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

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in open-vm-tools source package in Artful:
  Fix Committed
Status in open-vm-tools package in Debian:
  Fix Released

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: https://github.com/systemd/systemd/issues/5610

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Ryan Harper]

Are you providing network config to cloud-init?  Otherwise, cloud-init
is going to generate a fallback network config like your original, dhcp
on one of the interfaces.

If you want to persist network changes, you need to add them to a
separate netplan yaml config, or provide an updated network-config to
cloud-init; otherwise it's going to regenerate the same configuration
which will clobber a local change.

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

Both the original cloudy report and my test use a VM. The issue seems to
happen for both virtio and emulated e1000 network hardware.

What happens differently with a VM?

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

Works for me. I've been using a config like this for a while, the system
sets the interface name at boot as expected:

network:
  version: 2
  renderer: networkd
  ethernets:
mainif:
  match:
macaddress: "b8:27:eb:b6:35:86"
  set-name: mainif
  addresses: [ "10.3.0.5/23" ]
  gateway4: 10.3.0.1
  [...]

The difference here is that this is hardware rather than a VM. Are we
sure that the network interface shows up sufficiently early, and that
the mac can be matched at the time?

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

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

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

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

[henry eko]

Is this behavior related to the bug?
I have running router on 192.168.31.1

Then, I run a test setup of bionic on virtual box as a squid proxy.
Everything fine, almost. 

I found every local network names are failed to be resolved by the new bionic 
installation, but outside local network names are resolved. 
It is as if the system resolve the domain name to another dns server beyond 
configuration.

root@rld-proxy:/etc/NetworkManager/dispatcher.d# systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 2 (enp0s3)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 192.168.31.1

root@rld-proxy:/etc/NetworkManager/dispatcher.d# nslookup dm97-pandorabox
Server: 127.0.0.53
Address:127.0.0.53#53

** server can't find dm97-pandorabox: SERVFAIL

root@rld-proxy:/etc/NetworkManager/dispatcher.d# nslookup dm97-pandorabox 
192.168.31.1
Server: 192.168.31.1
Address:192.168.31.1#53

Name:   dm97-pandorabox
Address: 192.168.31.1
Name:   dm97-pandorabox
Address: fd76:bf99:23d7::1

Any thoughts?
If any work around produce another bugs, 
I guess it is safe for me to pending upgrade to bionic.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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 1752515] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1

[Phillip Susi]

You have a broken third party init script installed named "smfpd".  You
will need to remove it.


** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  podproces zainstalowany skrypt post-installation zwrócił kod błędu 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I can't install it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar  1 08:59:56 2018
  ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod 
błędu 1
  InstallationDate: Installed on 2017-11-24 (96 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770166] [NEW] The brightness of the notebook

[Adrian]

Public bug reported:

The brightness of the notebook does not lower or rise with the FN key.
Acer Aspire 5742 i3-380m 6gb ram ssd kingston 120gb.

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

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

Title:
  The brightness of the notebook

Status in xorg package in Ubuntu:
  New

Bug description:
  The brightness of the notebook does not lower or rise with the FN key.
  Acer Aspire 5742 i3-380m 6gb ram ssd kingston 120gb.

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

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

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Julian Andres Klode]

Can you check whether it works in bionic?

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Impact]
  lscpu fails to list CPU max and min frequencies if some CPUs are guarded.

  [Regression potential]
  Isolated change to lscpu min/max CPU frequency output, so the worst that 
could happen is that it fails to work elsewhere.

  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]  

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0%

[Vasilis Vlachoudis]

The latest that I've tried and it works is 4.14.40-041440
Anything later from 4.15.xx fails

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1768991] Re: [bytchtes8316] Sound does not work

[Jastria Rahmat]

i confirm this. the sound became dummy sound

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  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
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  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'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Joseph S Rebeirro]

no #121 don't work for me

I can access my desktop because i have blacklisted nouveau and using my intel 
gpu system  which I assume is functioning via mesa drivers nomodeset also works 
only issue is if i try to run nvidia

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Joseph S Rebeirro]

@tom-lorinthe

I have no issues with accessing Intel I just blacklisted nouveau for
that purpose. I wanted to use Nvidia but on evry install it seems to
crash the OS

will try and fix nvidia-prime after getting nvidia driver working

there is also dkms seems not to install in the kernel 4.15.21

anyways as you suggested it will attempt it thank you

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Tom]

@Joseph: did you try #121 ?

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Joseph S Rebeirro]

hey

There i am using ubuntu bionic 18.04 kernel 04.15.21

cant login on gdm or lightdm freezes on entering password  or access tty
on install nvidia-390 , nvidia 396 from ppa:graphics-drivers/ppa and
nvidia-driver-390 from bionic main repo

used to have black screen on boot suddenly rectified

nouveau driver ends up in cpu hard and soft lock

need help desperately. not able to access GPU

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

Title:
  nvidia-390 fails to boot graphical display

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

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

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

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

[Touch-packages] [Bug 1038434] Re: kupfer.py crashed with SIGSEGV

[Simon McVittie]

** Changed in: dbus-python (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  kupfer.py crashed with SIGSEGV

Status in kupfer:
  Fix Committed
Status in dbus-python package in Ubuntu:
  Invalid
Status in kupfer package in Ubuntu:
  Fix Released

Bug description:
  Kupfer seems to crash "spontaneously", even if I'm not directly using
  it. If I start it again, I am able to use it to launch a program or 2,
  but after a time, if I try to use it, I find it has crashed. I don't
  see any relevant information in .xsession-errors.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: kupfer 0+v208-2
  ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
  Uname: Linux 3.5.0-10-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.4-0ubuntu8
  Architecture: i386
  CrashCounter: 1
  Date: Sat Aug 18 13:14:27 2012
  ExecutablePath: /usr/share/kupfer/kupfer.py
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/share/kupfer/kupfer.py --no-splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0xb49ddac4:movl   $0x,0x4(%eax)
   PC (0xb49ddac4) ok
   source "$0x" ok
   destination "0x4(%eax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: kupfer
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
   ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
   ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
   ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
   ?? () from /lib/i386-linux-gnu/libdbus-1.so.3
  Title: kupfer.py crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev 
sambashare video

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

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

[Touch-packages] [Bug 1165742] Re: Synctex plugin was not built in raring

[Simon McVittie]

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

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

Title:
  Synctex plugin was not built in raring

Status in dbus-python package in Ubuntu:
  Fix Released
Status in gedit-plugins package in Ubuntu:
  Fix Released
Status in dbus-python source package in Raring:
  Won't Fix
Status in gedit-plugins source package in Raring:
  Won't Fix

Bug description:
  The Synctex plugin is apparently not installed by gedit-plugins. There
  is no "synctex" folder been created in usr/lib/gedit/plugins/
  Obviously the plugin does not appear among the available plugins in
  gedit preferences/plugins.

  The Synctex plugin appears to be in the package file on launchpad in
  https://launchpad.net/ubuntu/+archive/primary/+files/gedit-
  plugins_3.6.1.orig.tar.xz ; but it seems it fails to install
  correctly.

  Installing through CLI does not give any error message

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gedit-plugins 3.6.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic i686
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: i386
  Date: Sun Apr  7 14:48:14 2013
  InstallationDate: Installed on 2011-05-01 (706 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  SourcePackage: gedit-plugins
  UpgradeStatus: Upgraded to raring on 2013-03-29 (8 days ago)

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

Now available for testing:

https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Only cosmic is expected to get 5.49 but the above PPA also provides it
for bionic if you want to try it out without changing the whole OS :)

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1759961] Re: Update to 5.49 (mostly bug-fix release)

[Daniel van Vugt]

Now available for testing:

https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Only cosmic is expected to get 5.49 but the above PPA also provides it
for bionic if you want to try it out without changing the whole OS :)

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

Title:
  Update to 5.49 (mostly bug-fix release)

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

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

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

[Touch-packages] [Bug 1770119] Re: lightdm can't login to desktop session with gnome-flashback at Ubuntu18.04

[chenyu]

** Description changed:

  Environment:
  Ubuntu18.04 (fresh install)
  lightdm
  gnome-flashback
  domain user with PBIS joined domain
  
  root@ubuntu1804-2:/var/log/lightdm# lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04
  
  root@ubuntu1804-2:/var/log/lightdm# dpkg -s lightdm
  Package: lightdm
  Version: 1.26.0-0ubuntu1
  
  root@ubuntu1804-2:/var/log# dpkg -s gnome-flashback
  Package: gnome-flashback
  Version: 3.28.0-1ubuntu1
  
  Problem:
  local user can login to desktop fine, but for domain user, after enter 
password at greeter, lightdm is restarted and return back to greeter, no 
desktop session can be created.
  
- But for the domain user, login works fine at Mate and KDE.
+ But for the domain user, login works fine at Ubuntu(default), Mate and
+ KDE.
  
  Log: (please see full log in attachement)
  .xsession-errors: Failed to set environment: Process org.freedesktop.systemd1 
exited with status 1
  lightdm.log: [+4471.62s] DEBUG: Session pid=8524: Exited with return value 1
  
  Any help is appreciated.

** Description changed:

  Environment:
  Ubuntu18.04 (fresh install)
  lightdm
  gnome-flashback
  domain user with PBIS joined domain
  
  root@ubuntu1804-2:/var/log/lightdm# lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04
  
  root@ubuntu1804-2:/var/log/lightdm# dpkg -s lightdm
  Package: lightdm
  Version: 1.26.0-0ubuntu1
  
  root@ubuntu1804-2:/var/log# dpkg -s gnome-flashback
  Package: gnome-flashback
  Version: 3.28.0-1ubuntu1
  
  Problem:
- local user can login to desktop fine, but for domain user, after enter 
password at greeter, lightdm is restarted and return back to greeter, no 
desktop session can be created.
+ local user can login to gnome-flashback desktop fine, but for domain user, 
after enter password at greeter, lightdm is restarted and return back to 
greeter, no desktop session can be created.
  
  But for the domain user, login works fine at Ubuntu(default), Mate and
- KDE.
+ KDE desktop environment.
  
  Log: (please see full log in attachement)
  .xsession-errors: Failed to set environment: Process org.freedesktop.systemd1 
exited with status 1
  lightdm.log: [+4471.62s] DEBUG: Session pid=8524: Exited with return value 1
  
  Any help is appreciated.

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

Title:
  lightdm can't login to desktop session with gnome-flashback at
  Ubuntu18.04

Status in lightdm package in Ubuntu:
  New

Bug description:
  Environment:
  Ubuntu18.04 (fresh install)
  lightdm
  gnome-flashback
  domain user with PBIS joined domain

  root@ubuntu1804-2:/var/log/lightdm# lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  root@ubuntu1804-2:/var/log/lightdm# dpkg -s lightdm
  Package: lightdm
  Version: 1.26.0-0ubuntu1

  root@ubuntu1804-2:/var/log# dpkg -s gnome-flashback
  Package: gnome-flashback
  Version: 3.28.0-1ubuntu1

  Problem:
  local user can login to gnome-flashback desktop fine, but for domain user, 
after enter password at greeter, lightdm is restarted and return back to 
greeter, no desktop session can be created.

  But for the domain user, login works fine at Ubuntu(default), Mate and
  KDE desktop environment.

  Log: (please see full log in attachement)
  .xsession-errors: Failed to set environment: Process org.freedesktop.systemd1 
exited with status 1
  lightdm.log: [+4471.62s] DEBUG: Session pid=8524: Exited with return value 1

  Any help is appreciated.

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

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

[Touch-packages] [Bug 1759961] Re: Update to 5.49 (mostly bug-fix release)

[Daniel van Vugt]

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  Update to 5.49 (mostly bug-fix release)

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

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

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1770119] [NEW] lightdm can't login to desktop session with gnome-flashback at Ubuntu18.04

[chenyu]

Public bug reported:

Environment:
Ubuntu18.04 (fresh install)
lightdm
gnome-flashback
domain user with PBIS joined domain

root@ubuntu1804-2:/var/log/lightdm# lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

root@ubuntu1804-2:/var/log/lightdm# dpkg -s lightdm
Package: lightdm
Version: 1.26.0-0ubuntu1

root@ubuntu1804-2:/var/log# dpkg -s gnome-flashback
Package: gnome-flashback
Version: 3.28.0-1ubuntu1

Problem:
local user can login to gnome-flashback desktop fine, but for domain user, 
after enter password at greeter, lightdm is restarted and return back to 
greeter, no desktop session can be created.

But for the domain user, login works fine at Ubuntu(default), Mate and
KDE desktop environment.

Log: (please see full log in attachement)
.xsession-errors: Failed to set environment: Process org.freedesktop.systemd1 
exited with status 1
lightdm.log: [+4471.62s] DEBUG: Session pid=8524: Exited with return value 1

Any help is appreciated.

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

** Attachment added: "lightdm and .xsession_errors, and auth.log"
   https://bugs.launchpad.net/bugs/1770119/+attachment/5136615/+files/log.zip

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

Title:
  lightdm can't login to desktop session with gnome-flashback at
  Ubuntu18.04

Status in lightdm package in Ubuntu:
  New

Bug description:
  Environment:
  Ubuntu18.04 (fresh install)
  lightdm
  gnome-flashback
  domain user with PBIS joined domain

  root@ubuntu1804-2:/var/log/lightdm# lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  root@ubuntu1804-2:/var/log/lightdm# dpkg -s lightdm
  Package: lightdm
  Version: 1.26.0-0ubuntu1

  root@ubuntu1804-2:/var/log# dpkg -s gnome-flashback
  Package: gnome-flashback
  Version: 3.28.0-1ubuntu1

  Problem:
  local user can login to gnome-flashback desktop fine, but for domain user, 
after enter password at greeter, lightdm is restarted and return back to 
greeter, no desktop session can be created.

  But for the domain user, login works fine at Ubuntu(default), Mate and
  KDE desktop environment.

  Log: (please see full log in attachement)
  .xsession-errors: Failed to set environment: Process org.freedesktop.systemd1 
exited with status 1
  lightdm.log: [+4471.62s] DEBUG: Session pid=8524: Exited with return value 1

  Any help is appreciated.

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Valters]

Sorry, I meant the comments on ticket 1754686

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

** Summary changed:

- set-name doesn't work on boot, only with netplan apply
+ systemd-networkd not renaming devices on boot

** Description changed:

  === systemd issue ===
  
  Renaming devices doesn't seem to work.
  
  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:
  
  [Match]
  MACAddress=52:54:00:c1:c9:bb
  
  [Link]
  Name=myiface3
  
  I expect this to cause the device with that MAC address to be renamed to
  myiface3. However, when I reboot, I instead see:
  
  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
  
  The device is not renamed.
  
  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.
  
  The renaming does work if I boot with net.ifnames=0, and oddly, it also
- works if I unbind the device and rebind it as netplan apply does.
+ works if I unbind the device and rebind it as netplan apply does. No
+ setting of NamePolicy seems to help.
  
  === Original Bug ==
  
  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.
  
  Say I take this 50-cloud-init.yaml file:
  
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3
  
  Say I change set-name to 'myiface3' and reboot. I expect that the device
  will be called myiface3 and brought up fine with dhcp. However, instead
  I see:
  
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  
  The name has not been changed, and the device has not been brought up.
  
  If I run netplan apply however, I see the following:
  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever
  
  So names are successfully changed with netplan apply.
  
  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.
  
  This breaks some forms of migration in certain cloud environments.

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and 

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Valters]

Also not possible to install MySQL Workbench (mysql-workbench-
community-6.3.10-1ubuntu17.10-amd64.deb) because it has dependency on
libcurl3 which libcurl4 disallows. It is not a solution to require all
3rd party packages to move to libcurl4.

If the curl library did not break ABI between 3 and 4, and if it is
completely possible to have libcurl3 transitional package hanging
around, it would allow all those applications install and work.

Currently Ubuntu has centrally broken this for everyone, and the retoric
on ticket #1754294 is very frustrating.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1770062] Re: Please merge 2.3.2-1 from Debian Sid

[Julian Andres Klode]

Forgot to write: Uploaded.

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

Title:
  Please merge 2.3.2-1 from Debian Sid

Status in slang2 package in Ubuntu:
  Fix Committed

Bug description:
  Debian Sid contains a new upstream release. Let's merge it.

  Changelog entries since the last Ubuntu upload:

  slang2 (2.3.2-1) unstable; urgency=medium

* New upstream release
  - extended_terminfo.patch now included upstream
* Ack old bugs: Closes: #407835, #664075
* Set OBJDIR to src/x32objs on x32. Closes: #890545

   -- Alastair McKinstry   Mon, 19 Feb 2018
  16:59:12 +

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

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

[Touch-packages] [Bug 1770082] Re: set-name doesn't work on boot, only with netplan apply

[Daniel Axtens]

** Description changed:

+ === systemd issue ===
+ 
+ Renaming devices doesn't seem to work.
+ 
+ If I create /etc/systemd/network/10-network.link with:
+ 
+ [Match]
+ MACAddress=52:54:00:c1:c9:bb
+ 
+ [Link]
+ Name=myiface3
+ 
+ I expect this to cause the device with that MAC address to be named to
+ myiface3. However, when I reboot, I instead see:
+ 
+ $ ip l
+ 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ 2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
+ link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
+ 
+ The device is not renamed.
+ 
+ This link is pretty much identical to Example 2 in
+ https://www.freedesktop.org/software/systemd/man/systemd.link.html.
+ 
+ Oddly, while it doesn't work on reboot, it does work if you unbind the
+ device and rebind it as netplan apply does.
+ 
+ === Original Bug ==
+ 
  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.
  
  Say I take this 50-cloud-init.yaml file:
  
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3
  
  Say I change set-name to 'myiface3' and reboot. I expect that the device
  will be called myiface3 and brought up fine with dhcp. However, instead
  I see:
  
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  
  The name has not been changed, and the device has not been brought up.
  
  If I run netplan apply however, I see the following:
  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever
  
  So names are successfully changed with netplan apply.
  
  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.
  
  This breaks some forms of migration in certain cloud environments.

** Description changed:

  === systemd issue ===
  
  Renaming devices doesn't seem to work.
  
  If I create /etc/systemd/network/10-network.link with:
  
  [Match]
  MACAddress=52:54:00:c1:c9:bb
  
  [Link]
  Name=myiface3
  
- I expect this to cause the device with that MAC address to be named to
+ I expect this to cause the device with that MAC address to be renamed to
  myiface3. However, when I reboot, I instead see:
  
  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
- link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
+ link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
  
  The device is not renamed.
  
  This link is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.
  
  Oddly, while it doesn't work on reboot, it does work if you unbind the
  device and rebind it as netplan apply does.
  
  === Original Bug ==
  
  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.
  
  Say I take this 50-cloud-init.yaml file:
  
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # 

[Touch-packages] [Bug 1770062] Re: Please merge 2.3.2-1 from Debian Sid

[Julian Andres Klode]

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

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

Title:
  Please merge 2.3.2-1 from Debian Sid

Status in slang2 package in Ubuntu:
  Fix Committed

Bug description:
  Debian Sid contains a new upstream release. Let's merge it.

  Changelog entries since the last Ubuntu upload:

  slang2 (2.3.2-1) unstable; urgency=medium

* New upstream release
  - extended_terminfo.patch now included upstream
* Ack old bugs: Closes: #407835, #664075
* Set OBJDIR to src/x32objs on x32. Closes: #890545

   -- Alastair McKinstry   Mon, 19 Feb 2018
  16:59:12 +

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

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

[Touch-packages] [Bug 1770092] [NEW] error

[frank mark]

Public bug reported:

when I downloading apps some errors and when working OS working so slowy

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May  9 15:43:57 2018
DistUpgraded: 2018-05-02 06:58:57,163 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GconfCompiz:
 /apps/compiz-1/general:
   /apps/compiz-1/general/screen0:
/apps/compiz-1/general/screen0/options:
 active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c652]
 NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd GF119M [GeForce 610M] [144d:c652]
InstallationDate: Installed on 2017-01-31 (462 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C
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-20-generic 
root=UUID=e8f1d7ee-2740-4158-977c-6250f43f5995 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-01 (7 days ago)
dmi.bios.date: 02/20/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P07RAC
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07RAC:bd02/20/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4C/300E5C/300E7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 300E4C/300E5C/300E7C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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
xserver.bootTime: Tue Apr 10 08:59:09 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5539 
 vendor CMO
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug bionic 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/1770092

Title:
  error

Status in xorg package in Ubuntu:
  New

Bug description:
  when I downloading apps some errors and when working OS working so
  slowy

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed 

[Touch-packages] [Bug 1754692] Re: [regression] Tabs in Settings of Thunderbird not visible

[Rolf Leggewie]

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

** This bug has been marked a duplicate of bug 1725588
   Thunderbird: tab borders Preferences > Security missing

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

Title:
  [regression] Tabs in Settings of Thunderbird not visible

Status in thunderbird package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  I am on Ubuntu 18.04 Bionic right now and noticed a little theme
  missbehavior. (i think)

  >> Open 'Thunderbird'...go into 'Settings'...go to 'Security' (for
  example)

  There the Tabs below (Junk, Password, ...) are not visible.
  There is just text with no background (see screenhot)

  
  Sidenote: The same i noticed on Xubuntu with greybird-theme. But with other 
themes (numix, arc) they are visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  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
  CasperVersion: 1.389
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 15:26:35 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180308)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1768579] Re: package libopencv3.2-java 3.2.0+dfsg-4build2 failed to install/upgrade: trying to overwrite '/usr/share/java/opencv.jar', which is also in package libopencv3.1-java

[Launchpad Bug Tracker]

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

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

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

Title:
  package libopencv3.2-java 3.2.0+dfsg-4build2 failed to
  install/upgrade: trying to overwrite '/usr/share/java/opencv.jar',
  which is also in package libopencv3.1-java 3.1.0+dfsg1-1~exp1ubuntu3

Status in opencv package in Ubuntu:
  Confirmed

Bug description:
  I just logged in and this error message was on the desktop.  This is a
  system that has been upgraded from 12.04 to 14.04 to 16.04 to 18.04
  over the years.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libopencv3.2-java 3.2.0+dfsg-4build2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 10:19:39 2018
  ErrorMessage: trying to overwrite '/usr/share/java/opencv.jar', which is also 
in package libopencv3.1-java 3.1.0+dfsg1-1~exp1ubuntu3
  InstallationDate: Installed on 2016-10-01 (577 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  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: opencv
  Title: package libopencv3.2-java 3.2.0+dfsg-4build2 failed to 
install/upgrade: trying to overwrite '/usr/share/java/opencv.jar', which is 
also in package libopencv3.1-java 3.1.0+dfsg1-1~exp1ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-01-25 (97 days ago)

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

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

[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

[Timo Aaltonen]

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  In Progress

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_name, let other machines
  fail to search by card_long_name, then fallback to original searching
  method - search by card_name.

  [Other Info]

  Since I could not find the alsa-lib repository in canonical, I just
  generated the debdiff with "apt-get source ...".

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1768830/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Pascal Normand]

After updating to 18.04, curl is gone! When trying to install it want to
remove virtualbox (libcurl3, libcurl4 issue).

No... way.

At the moment, the simplest solution is to move the VM to another
computer (windows) and after that I can experiment with this...
disaster.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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