[Touch-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

This is actually a kernel bug, in Linux. The issue is the absence of
platform data for this particular board in the snd_soc_rt5645 module.

The issue can be worked around by creating
/etc/modprobe.d/hacksound.conf with the following contents:

# Invert jack detection (1) and use detection mode 2 (2).
options snd_soc_rt5645 quirk=0x21

This takes advantage of the "quirk" option for the module, added in
https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f,
which allows overriding the platform data it usually just has built into
it about how audio jacks are hooked up on particular systems.

It looks like this board needs special system info added to
sound/soc/codecs/rt5645.c, keyed on DMI data. The platform data would
look something like:

static const struct rt5645_platform_data lattepanda_platform_data = {
.jd_mode = 2,
.inv_jd1_1 = true
};

Here's the DMI data for the motherboard; it's a bit generic. I can
provide other DMI data to match on if needed.

Base Board Information
Manufacturer: AMI Corporation
Product Name: Cherry Trail CR
Version: Default string
Serial Number: Default string
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0


** Package changed: alsa-lib (Ubuntu) => linux (Ubuntu)

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My machine is a LattePanda board, which uses a "chtrt5645" device as a
  sound card. It has a single headphone output jack, which I think is a
  TRRS jack, with a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:

[Touch-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

This may be a kernel driver bug, and a regression from 4.12. See
http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689

This may be a missing piece of platform data in the kernel that would
tell it to invert jack detection on this particular board. I will try
testing with the functionality added to the kernel in
https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f
which lets you tinker with the platform data at runtime.

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  My machine is a LattePanda board, which uses a "chtrt5645" device as a
  sound card. It has a single headphone output jack, which I think is a
  TRRS jack, with a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
  index: 1
name: 
driver: 
owner module: 8
properties:
alsa.card = "0"
alsa.card_name = "chtrt5645"
alsa.long_card_name = 
"AMICorporation-Defaultstring-Defaultstring-CherryTrailCR"
alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645"
device.bus_path = "platform-cht-bsw-rt5645"

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

[AaronMa]

verification-done-disco

Verified on the latest update on disco.
i2c_i801 is removed and works fine on several laptops.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions

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

[Touch-packages] [Bug 1692494] Re: klibc does not support reboot arguments

[Bug Watch Updater]

** Changed in: klibc (Debian)
   Status: Confirmed => Fix Released

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

Title:
  klibc does not support reboot arguments

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Xenial:
  New
Status in klibc package in Debian:
  Fix Released

Bug description:
  ... so we cannot do things like "reboot recovery" in devices that
  follow the Android partitions conventions.

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

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

[Touch-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

If I save the ALSA state with the headphones unplugged to a file:

sudo alsactl --file=settings-out.txt store

And then plug in the headphones and restore it:

sudo alsactl --file=settings-out.txt restore

I still get no sound. But then diffing the final state against the
unplugged state did find this:

control.175 {
iface CARD
name 'Headphone Jack'
-   value false
+   value true
comment {
access read
type BOOLEAN
count 1
}
}
control.176 {
iface CARD
name 'Headset Mic Jack'
-   value false
+   value true
comment {
access read
type BOOLEAN
count 1
}
}

I need to convince ALSA to report/interpret those boolean jack states
the other way around.

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

Title:
  Headphone jack switch sense is inverted: plugging in headphones
  disables headphone output

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  My machine is a LattePanda board, which uses a "chtrt5645" device as a
  sound card. It has a single headphone output jack, which I think is a
  TRRS jack, with a mic input, such as is normally used on phones.

  When I don't have headphones plugged in, the system thinks headphones
  *are* plugged in. Gnome Control Center shows my audio device as being
  headphones. If I insert a headphone connector partway into the jack, I
  can even get sound in the headphones.

  But if I plug the headphones all the way in, the system decided that I
  have *un*plugged the headphones, and switches output over to
  "Speaker". The system doesn't actually have a speaker, only a
  headphone jack. And when the system switches over to "Speaker", I get
  no sound out of the headphones, even if I open "pavucontrol" and swap
  over to "Headphones (unplugged)" on the "Output Devices" tab.

  This is what "pacmd"'s "list-cards" command says with my headphones
  *unplugged*:

  2 card(s) available.
  index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency 
offset 0 usec, available: no)
   

[Touch-packages] [Bug 1824259] [NEW] Headphone jack switch sense is inverted: plugging in headphones disables headphone output

[Adam Novak]

Public bug reported:

My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.

When I don't have headphones plugged in, the system thinks headphones
*are* plugged in. Gnome Control Center shows my audio device as being
headphones. If I insert a headphone connector partway into the jack, I
can even get sound in the headphones.

But if I plug the headphones all the way in, the system decided that I
have *un*plugged the headphones, and switches output over to "Speaker".
The system doesn't actually have a speaker, only a headphone jack. And
when the system switches over to "Speaker", I get no sound out of the
headphones, even if I open "pavucontrol" and swap over to "Headphones
(unplugged)" on the "Output Devices" tab.

This is what "pacmd"'s "list-cards" command says with my headphones
*unplugged*:

2 card(s) available.
index: 0
name: 
driver: 
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path = 
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output 
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output 
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) 
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output 
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) 
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) 
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile: 
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
index: 1
name: 
driver: 
owner module: 8
properties:
alsa.card = "0"
alsa.card_name = "chtrt5645"
alsa.long_card_name = 
"AMICorporation-Defaultstring-Defaultstring-CherryTrailCR"
alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645"
device.bus_path = "platform-cht-bsw-rt5645"
sysfs.path = 
"/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0"
device.form_factor = "internal"
device.string = "0"
device.description = "Built-in Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card"
profiles:
HiFi: Default (priority 8000, available: unknown)
off: Off (priority 0, available: unknown)
active profile: 
sinks:

alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink/#0: Built-in Audio 
Headphones + Speaker
sources:

alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink.monitor/#0: 
Monitor of Built-in Audio Headphones + Speaker

alsa_input.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__source/#1: 

[Touch-packages] [Bug 1824252] Re: at startup it asks me to perform a manual fsk

[Daniel van Vugt]

It sounds like you are talking about this kernel error:

[   89.164362] FAT-fs (sdb): Volume was not properly unmounted. Some
data may be corrupt. Please run fsck.

That's a problem with the 16GB USB stick ("Verbatim STORE N GO") you
have plugged in and not an Ubuntu bug.

To check and repair the USB stick, you can run the 'Disks' app.


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

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

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

Title:
  at startup it asks me to perform a manual fsk

Status in Ubuntu:
  Invalid

Bug description:
   $ ubuntu-bug manual fsk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr 10 18:52:44 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6320] 
[19da:a233]
  InstallationDate: Installed on 2017-05-02 (708 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: ZOTAC ZBOX-AD04
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=b95f85bd-633b-4ec2-8e28-e51070b90849 ro quiet plymouth:debug=1=1=1=1 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-AD04
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 3
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/24/2012:svnZOTAC:pnZBOX-AD04:pvrXX:rvnZOTAC:rnZBOX-AD04:rvrXX:cvnNA:ct3:cvrNA:
  dmi.product.name: ZBOX-AD04
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 10 18:33:54 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLiteOn HP USB Multimedia Keyboard KEYBOARD, id 8
   inputLiteOn HP USB Multimedia Keyboard KEYBOARD, id 9
   inputDell Dell USB Mouse  MOUSE, id 10
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions

[Daniel van Vugt]

Apparently the feature doesn't exist in Xwayland yet. Someone mentioned
that it's a known issue and the upstream developers will be looking at
completing it this year.

** Summary changed:

- Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions
+ Nvidia driver installed but apps are using LLVMpipe/Mesa in Wayland sessions

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

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

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Nvidia driver installed but apps are using LLVMpipe/Mesa in Wayland
  sessions

Status in mesa package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland
  sessions.

  I am using kernel parameter nvidia-drm.modeset=1, which is required to
  get the "Ubuntu on Wayland" option. But after logging in I see:

  $ glxinfo | grep OpenGL
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 19.0.1
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  $ es2_info | grep ^GL
  GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1
  GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-driver-418 418.56-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  Date: Sun Apr  7 17:26:07 2019
  InstallationDate: Installed on 2018-12-04 (124 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: nvidia-graphics-drivers-418
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

[Bug Watch Updater]

** Changed in: systemd (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

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

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

[Daniel van Vugt]

** Changed in: gnome-shell
 Remote watch: GNOME Bug Tracker #724935 => 
gitlab.gnome.org/GNOME/gnome-shell/issues #1159

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/gnome-shell/+bug/1738676/+subscriptions

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Daniel van Vugt]

** Tags removed: yakkety zesty

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1796251] Re: gnome-shell crashed with SIGSEGV when taking a screenshot, in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/365834

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

Title:
  gnome-shell crashed with SIGSEGV when taking a screenshot, in
  __strlen_avx2() from real_save_png() from
  gdk_pixbuf__png_image_save_to_callback() from
  gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv()

Status in GNOME Shell:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.0-3ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 
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/gnome-shell/+bug/1796251/+subscriptions

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

[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

[Launchpad Bug Tracker]

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

** Changed in: policykit-desktop-privileges (Ubuntu)
   Status: New => Confirmed

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

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On 16.04 (XFCE session and others) and possibly later the power-
  manager is unable to suspend the system when the user is inactive. A
  PK user-agent dialog is presented for the user to authenticate first -
  and as this action occurs specifically when the user is idle and away
  the PC can end up having an unplanned loss of power when the battery
  is exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

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

[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

[PJSingh5000]

This bug is still being tracked in bugzilla.

** Bug watch added: GNOME Bug Tracker #724935
   https://gitlab.gnome.org/724935

** Changed in: gnome-shell
   Status: New => Unknown

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1159 => GNOME Bug 
Tracker #724935

** Bug watch added: GNOME Bug Tracker #703046
   https://gitlab.gnome.org/703046

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/gnome-shell/+bug/1738676/+subscriptions

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

[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

[PJSingh5000]

For reference, here are the upstream bugs:

GITLAB:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159

BUGZILLA:
https://bugzilla.gnome.org/show_bug.cgi?id=724935
https://bugzilla.gnome.org/show_bug.cgi?id=703046

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/gnome-shell/+bug/1738676/+subscriptions

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

[Touch-packages] [Bug 1824252] [NEW] at startup it asks me to perform a manual fsk

[David Lee]

Public bug reported:

 $ ubuntu-bug manual fsk

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Apr 10 18:52:44 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6320] 
[19da:a233]
InstallationDate: Installed on 2017-05-02 (708 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: ZOTAC ZBOX-AD04
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=b95f85bd-633b-4ec2-8e28-e51070b90849 ro quiet plymouth:debug=1=1=1=1 
splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: NA
dmi.board.name: ZBOX-AD04
dmi.board.vendor: ZOTAC
dmi.board.version: XX
dmi.chassis.asset.tag: NA
dmi.chassis.type: 3
dmi.chassis.vendor: NA
dmi.chassis.version: NA
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd12/24/2012:svnZOTAC:pnZBOX-AD04:pvrXX:rvnZOTAC:rnZBOX-AD04:rvrXX:cvnNA:ct3:cvrNA:
dmi.product.name: ZBOX-AD04
dmi.product.version: XX
dmi.sys.vendor: ZOTAC
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Apr 10 18:33:54 2019
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLiteOn HP USB Multimedia Keyboard KEYBOARD, id 8
 inputLiteOn HP USB Multimedia Keyboard KEYBOARD, id 9
 inputDell Dell USB Mouse  MOUSE, id 10
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: radeon

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


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

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

Title:
  at startup it asks me to perform a manual fsk

Status in xorg package in Ubuntu:
  New

Bug description:
   $ ubuntu-bug manual fsk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr 10 18:52:44 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6320] 
[19da:a233]
  InstallationDate: Installed on 2017-05-02 (708 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: ZOTAC ZBOX-AD04
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=b95f85bd-633b-4ec2-8e28-e51070b90849 ro quiet plymouth:debug=1=1=1=1 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2012
  

[Touch-packages] [Bug 1824249] Re: package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-li

[valerio cogrossi]

provo a controllare cosa manca per linux-gnu

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

Title:
  package binutils-multiarch (not installed) [modified: usr/bin/x86_64
  -linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-
  gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy
  usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib
  usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size
  usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip]
  failed to install/upgrade: new binutils-multiarch package pre-
  installation script subprocess returned error exit status 2

Status in binutils package in Ubuntu:
  New

Bug description:
  non si riesce ad installare multiarch e binutils

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: binutils-multiarch (not installed) [modified: 
usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar 
usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm 
usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump 
usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf 
usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings 
usr/bin/x86_64-linux-gnu-strip]
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Wed Apr 10 20:39:45 2019
  ErrorMessage: new binutils-multiarch package pre-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2019-04-09 (1 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: binutils
  Title: package binutils-multiarch (not installed) [modified: 
usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar 
usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm 
usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump 
usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf 
usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings 
usr/bin/x86_64-linux-gnu-strip] failed to install/upgrade: new 
binutils-multiarch package pre-installation script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1824249] [NEW] package binutils-multiarch (not installed) [modified: usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-

[valerio cogrossi]

Public bug reported:

non si riesce ad installare multiarch e binutils

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: binutils-multiarch (not installed) [modified: 
usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar 
usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm 
usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump 
usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf 
usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings 
usr/bin/x86_64-linux-gnu-strip]
ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
Date: Wed Apr 10 20:39:45 2019
ErrorMessage: new binutils-multiarch package pre-installation script subprocess 
returned error exit status 2
InstallationDate: Installed on 2019-04-09 (1 days ago)
InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.4
SourcePackage: binutils
Title: package binutils-multiarch (not installed) [modified: 
usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar 
usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm 
usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump 
usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf 
usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings 
usr/bin/x86_64-linux-gnu-strip] failed to install/upgrade: new 
binutils-multiarch package pre-installation script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package cosmic uec-images

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

Title:
  package binutils-multiarch (not installed) [modified: usr/bin/x86_64
  -linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar usr/bin/x86_64-linux-
  gnu-gprof usr/bin/x86_64-linux-gnu-nm usr/bin/x86_64-linux-gnu-objcopy
  usr/bin/x86_64-linux-gnu-objdump usr/bin/x86_64-linux-gnu-ranlib
  usr/bin/x86_64-linux-gnu-readelf usr/bin/x86_64-linux-gnu-size
  usr/bin/x86_64-linux-gnu-strings usr/bin/x86_64-linux-gnu-strip]
  failed to install/upgrade: new binutils-multiarch package pre-
  installation script subprocess returned error exit status 2

Status in binutils package in Ubuntu:
  New

Bug description:
  non si riesce ad installare multiarch e binutils

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: binutils-multiarch (not installed) [modified: 
usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar 
usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm 
usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump 
usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf 
usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings 
usr/bin/x86_64-linux-gnu-strip]
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  Date: Wed Apr 10 20:39:45 2019
  ErrorMessage: new binutils-multiarch package pre-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2019-04-09 (1 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: binutils
  Title: package binutils-multiarch (not installed) [modified: 
usr/bin/x86_64-linux-gnu-addr2line usr/bin/x86_64-linux-gnu-ar 
usr/bin/x86_64-linux-gnu-gprof usr/bin/x86_64-linux-gnu-nm 
usr/bin/x86_64-linux-gnu-objcopy usr/bin/x86_64-linux-gnu-objdump 
usr/bin/x86_64-linux-gnu-ranlib usr/bin/x86_64-linux-gnu-readelf 
usr/bin/x86_64-linux-gnu-size usr/bin/x86_64-linux-gnu-strings 
usr/bin/x86_64-linux-gnu-strip] failed to install/upgrade: new 
binutils-multiarch package pre-installation script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1824249/+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 1823426] Re: librsvg ftbfs in disco (i386 only)

[Bug Watch Updater]

** Changed in: librsvg
   Status: Unknown => New

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg:
  New
Status in librsvg package in Ubuntu:
  In Progress
Status in librsvg source package in Disco:
  In Progress

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

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

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

[Touch-packages] [Bug 1822590] Re: Found storing user fingerprints without encryption

[Bug Watch Updater]

** Changed in: fprintd
   Status: Unknown => New

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

Title:
  Found storing user fingerprints without encryption

Status in fprintd:
  New
Status in apparmor package in Ubuntu:
  New
Status in fprintd package in Ubuntu:
  Triaged

Bug description:
  Dear all,

  I would like to report a new issue as follows.
  ‘fprintd’ saves a fingerprint data, ISO/IEC 19794-2 formatted, to a file on 
the host without any encryption.
  Though fprintd generates fingerprint image with root permission for 
protecting the file from attackers, it is not of itself sufficient.
  It is well known threat model that a formatted fingerprint data can be 
restored to original image about a decade ago.
  [1-4] are presented to create sophisticated and natural-looking fingerprints 
only from the numerical template data format as defined in ISO/IEC 19794-2.
  They also successfully evaluated these approaches against a number of 
undisclosed state-of-the-art algorithms and the NIST Fingerprint Image Software.

  We need improvements of those issues.

  [1] R. Cappelli et al., “Fingerprint Image Reconstruction from Standard 
Templates”, IEEE Trans. on Pattern Analysis and Machine Intelligence, vol.29, 
no.9, pp.1489-1503, 2007.
  [2] A. Ross et al., “From template to image: Reconstructing fingerprints from 
minutiae points”, IEEE Trans on Pattern Analysis and Machine Intelligence, 
vol.29, no.4, pp.544-560, 2007.
  [3] R. Cappelli et al., “Can Fingerprints be reconstructed from ISO 
Templates?”, IEEE ICARCV 2006.
  [4] J. Feng et al., “Fingerprint Reconstruction: From Minutiae to Phase”, 
IEEE Trans on Pattern Analysis and Machine Intelligence, vol.33, no.2, 
pp.209-223, 2011.

  Sincerely,
  Seong-Joong Kim

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

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

[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/gnome-shell/+bug/1738676/+subscriptions

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

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

[loluchayjose]

Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es
"sudo apt purge gdm etc."... "etc." que?

Varios dicen "borrar"... borrar como?

Tu dijiste: "I solved problem sttoping services and erasing systemd-shim upon 
console.
After I could updating my pc, also, from console"... Qué servicios paraste, y 
como? Tengo que hacerlo en Safe Mode?

Uno de los últimos dice: "The upload of systemd that was purported to
fix this bug report was superseded by a security update of systemd so
the fix is no longer available." Así que por lo que se ve, esa solucion
ya no sirve.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Triaged
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

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

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

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

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

[Touch-packages] [Bug 1079232] Re: OpenCV built without Qt support

[Bug Watch Updater]

** Changed in: opencv (Debian)
   Status: Won't Fix => Fix Released

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

Title:
  OpenCV built without Qt support

Status in opencv package in Ubuntu:
  Triaged
Status in opencv package in Debian:
  Fix Released

Bug description:
  Is there any specific reason for openCV to be built without Qt
  support? The "new" Highgui Qt functions, already available in the
  version which ships with Ubuntu Precise, provide for much better user
  interfaces for simpler cases without having to build complete GUIs.

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

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

[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

[PJSingh5000]

I opened this issue against gnome-shell, upstream.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159

I did not report this bug against gtk+3.0. Should I do that as well?

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1159
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159
   Importance: Unknown
   Status: Unknown

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/gnome-shell/+bug/1738676/+subscriptions

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

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[PJSingh5000]

Oops, I meant to say, "Less than *4* doesn't work, and more than 4 are
not necessary."

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  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/1727908/+subscriptions

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

[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

[PJSingh5000]

Works on 18.10 x64 for me...

$ sudo apt update
$ sudo apt install --reinstall libxkbcommon0 libxkbcommon-x11-0 xkb-data

Thanks!

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

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[PJSingh5000]

Interesting...

I tried that, and I noticed that 4 rapid clicks (actually taps on my
touchpad) consistently brings up the pkexec password box. Less than 3
doesn't work, and more than 4 are not necessary.

Once you've been authenticated, you are able to make changes on the
Other Software tab, as you would expect.

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  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/1727908/+subscriptions

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

[Touch-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)

[Olivier Tilloy]

There is also a unit test failure on i386 only.
Upstream bug report: https://gitlab.gnome.org/GNOME/librsvg/issues/455

** Bug watch added: gitlab.gnome.org/GNOME/librsvg/issues #455
   https://gitlab.gnome.org/GNOME/librsvg/issues/455

** Also affects: librsvg via
   https://gitlab.gnome.org/GNOME/librsvg/issues/455
   Importance: Unknown
   Status: Unknown

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg:
  Unknown
Status in librsvg package in Ubuntu:
  In Progress
Status in librsvg source package in Disco:
  In Progress

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

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

-- 
Mailing list: 

[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles

[Brian Murray]

Hello Robert, or anyone else affected,

Accepted console-setup into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu9.1 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: console-setup (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: console-setup (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Fix Committed
Status in console-setup source package in Xenial:
  Fix Committed
Status in console-setup source package in Bionic:
  Fix Committed
Status in console-setup source package in Cosmic:
  Fix Committed
Status in console-setup source package in Disco:
  Fix Committed

Bug description:
  [SRU Justification]
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

    19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
    ...
    19:51:13 systemd[1]: Starting Set console font and keymap...
    19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file
    19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
    19:51:15 systemd[1]: Failed to start Set console font and keymap.
    19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
    19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
    if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp 2>/dev/null`

  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
    the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
    the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
    on systemd-tmpfiles-clean; let's remove the dependency
    instead of declaring it

  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
    data to answer that.

  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
    say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
    to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
    that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot

  [Test case]
  1. Install console-setup from -proposed
  2. Reboot
  3. Verify that `systemctl status console-setup` shows that the service has 
completed successfully.

  Since this is a race, additional fuzz testing may be warranted for the
  cloud images to confirm that the issue experienced in GCE is really
  fixed.  However, that should not block promotion of this SRU fix since
  there 

[Touch-packages] [Bug 1824227] Please test proposed package

[Brian Murray]

Hello Robert, or anyone else affected,

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

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: console-setup (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Fix Committed
Status in console-setup source package in Xenial:
  Fix Committed
Status in console-setup source package in Bionic:
  Fix Committed
Status in console-setup source package in Cosmic:
  Fix Committed
Status in console-setup source package in Disco:
  Fix Committed

Bug description:
  [SRU Justification]
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

    19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
    ...
    19:51:13 systemd[1]: Starting Set console font and keymap...
    19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file
    19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
    19:51:15 systemd[1]: Failed to start Set console font and keymap.
    19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
    19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
    if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp 2>/dev/null`

  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
    the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
    the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
    on systemd-tmpfiles-clean; let's remove the dependency
    instead of declaring it

  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
    data to answer that.

  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
    say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
    to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
    that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot

  [Test case]
  1. Install console-setup from -proposed
  2. Reboot
  3. Verify that `systemctl status console-setup` shows that the service has 
completed successfully.

  Since this is a race, additional fuzz testing may be warranted for the
  cloud images to confirm that the issue experienced in GCE is really
  fixed.  However, that should not block promotion of this SRU fix since
  there definitely is a race here that should be fixed per se even if
  there are other issues still causing a failure in GCE.

  [Regression potential]
  None known. 

[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

[Steve Langasek]

Hello Alan, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.3 in
a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-bionic
** Tags added: verification-needed-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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

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

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

[Touch-packages] [Bug 1824227] Please test proposed package

[Brian Murray]

Hello Robert, or anyone else affected,

Accepted console-setup into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.108ubuntu15.5 in a few hours, and then in the -proposed
repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Fix Committed
Status in console-setup source package in Xenial:
  Fix Committed
Status in console-setup source package in Bionic:
  Fix Committed
Status in console-setup source package in Cosmic:
  Fix Committed
Status in console-setup source package in Disco:
  Fix Committed

Bug description:
  [SRU Justification]
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

    19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
    ...
    19:51:13 systemd[1]: Starting Set console font and keymap...
    19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file
    19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
    19:51:15 systemd[1]: Failed to start Set console font and keymap.
    19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
    19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
    if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp 2>/dev/null`

  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
    the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
    the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
    on systemd-tmpfiles-clean; let's remove the dependency
    instead of declaring it

  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
    data to answer that.

  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
    say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
    to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
    that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot

  [Test case]
  1. Install console-setup from -proposed
  2. Reboot
  3. Verify that `systemctl status console-setup` shows that the service has 
completed successfully.

  Since this is a race, additional fuzz testing may be warranted for the
  cloud images to confirm that the issue experienced in GCE is really
  fixed.  However, that should not block promotion of this SRU fix since
  there definitely is a race here that should be fixed per se even if
  there are other issues still causing a failure in GCE.

  [Regression potential]
  None known.  /run is guaranteed to be mounted rw very early in boot - 
generally before /tmp is mounted, due to /tmp being on the rootfs that 

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

[Steve Langasek]

Hello Daniel, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.3 in
a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === 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 

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

[Dan Streetman]

autopkgtest regressions:

bionic:

apt passed on re-run

dovecot (armhf) failed again; i'm re-running it again, but i think we
can ignore it as it failed in the same way for the openssl upload before
we uploaded this.

snapd i opened bug 1824237, although that might be limited to only
cosmic, not bionic

all other bionic tests ignorable as explained in previous comments

cosmic:

snapd as with bionic, bug 1824237
docker.io tests fail also due to bug 1824237 (because they use snaps in their 
tests, and the core snap is broken)

systemd test are failing, i think, also because of bug 1824237.  since
the problem is the cosmic 'core' snap is broken, all other snaps fail,
and the failing test for all systemd archs is 'boot-and-services' which
checks that no services failed.  it appears some of the services, like
lxd, because they could not start due to broken core snap; i'm testing
locally to verify this.

all other cosmic tests ignorable as explained in previous comments

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

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

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1101049] Re: non-free algorithms (e.g. SIFT) excluded

[Bug Watch Updater]

** Changed in: opencv (Debian)
   Status: New => Fix Released

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

Title:
  non-free algorithms (e.g. SIFT) excluded

Status in opencv package in Ubuntu:
  Confirmed
Status in opencv package in Debian:
  Fix Released

Bug description:
  Currently, non-free algorithms such as SIFT are excluded from the
  opencv_2.4.2+dfsg-0exp2.  However, is it possible to include libraries
  and header under opencv2/non-free (that may be subject to patents in
  some countries) into packages such as libopencv-nonfree(-dev)?  This
  non-free package can be included in the multiverse repository.

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

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

[Touch-packages] [Bug 1823572] Re: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all

[boombam]

I ended up getting a USB DAC to avoid this issue all together.

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

Title:
  [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound output. I don't see the CA0132 devices listed in the sound
  settings GUI either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  archeetos   1879 F pulseaudio
   /dev/snd/controlC1:  archeetos   1879 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 14:04:20 2019
  InstallationDate: Installed on 2017-03-18 (749 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1476 F pulseaudio
archeetos   1879 F pulseaudio
   /dev/snd/controlC1:  gdm1476 F pulseaudio
archeetos   1879 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [Z170X-Gaming 7, Creative CA0132, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to bionic on 2019-04-07 (0 days ago)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22m
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-Gaming 7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22m:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z170X-Gaming 7
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

[Dan Streetman]

Your /run dir and /var/run link look fine - I am 99% sure that tmpfiles
has nothing to do with whatever problem you're having (tmpfiles doesn't
even create the /var/run symlink, base-files does).

> /var/run directories are not created properly

what specifically do you mean by this?  just that you see log errors?

What's the output of:

$ sudo find /run -ls

$ df


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

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

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 16.04.6 LTS
   
  Release:16.04 
   

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  systemd:  
   
Installed: 229-4ubuntu21.16 
   
Candidate: 229-4ubuntu21.16 
   
Version table:  
   
   *** 229-4ubuntu21.16 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages  
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status  
   
   229-4ubuntu4 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages   
 

  3) What you expected to happen
  4) What happened instead

  Ubuntu server (running in OpenVZ VPS farm, thus the old kernel
  version) has been up and running happily, until I performed apt-get
  upgrade and rebooted the server. After reboot, I could not establish
  SSH connection to server, port 22 connection was refused.

  I opened a HTML console to my server instance and checked logs. From
  the logs, it was shown, that SSH server could not start, as it did not
  have the /var/run/sshd directory. After scrolling back the
  /var/log/syslog, I noticed that there were lots of other /var/run
  subdirectories, which were not created. Here is cut from
  /var/log/syslog, related to systemd-tmpfiles:

  ---8<---8<---
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: 
[/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v
  ar/log", ignoring.
   
  Mar  6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: 
Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/fail2ban: Too many levels of symb
  olic links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/screen: Too many levels of symbol
  ic links  
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sshd: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo/ts: Too many levels of symbo
  lic links 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: 
Invalid argument  
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif 
failed: Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: 

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

[José Enrique]

Good night looking for internet, there are many solutions. The treat can
help you. Kind regards.
Buenas noches, busca en Internet hay muchas soluciones a este problema,
creo que este hilo puede ayudarte.
Saludos

El mié., 10 abr. 2019 22:11, loluchayjose <1773...@bugs.launchpad.net>
escribió:

> Looks like I can't install anything (or most things) until this gets
> fixed. Is there a consensus on the proper way to uninstall systemd-shim?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>   upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>   Fix Released
> Status in systemd-shim package in Ubuntu:
>   Won't Fix
> Status in systemd source package in Bionic:
>   Triaged
> Status in systemd-shim source package in Bionic:
>   Won't Fix
> Status in systemd source package in Cosmic:
>   Fix Released
> Status in systemd-shim source package in Cosmic:
>   Won't Fix
>
> Bug description:
>   [Impact]
>
>* Some systems fail to upgrade due to conflicts between systemd and
>   the (now removed from the archive) systemd-shim / upstart.
>
>* Instead of trying to work out what's the problem in ordering /
>   removal of diverts, ensure that systemd is never unpacked whilst
>   systemd-shim/upstart are still on disk. Thus declare conflicts against
>   systemd-shim/upstart packages in systemd package.
>
>   [Test Case]
>
>* monitor drop-off of upgrades with below reported problem
>
>* Check that it is possible to upgrade to bionic's libpam-systemd
>   from xenial with systemd-shim installed on xenial, ie.
>
>   lxc launch ubuntu-daily:xenial test-shim-upgrade
>   lxc exec test-shim-upgrade
>   apt update
>   apt install systemd-shim
>   wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
>   apt install ./systemd-shim_10-3_amd64.deb
>   sed 's/xenial/bionic/' -i /etc/apt/sources.list
>   apt update
>   apt install systemd
>
>   this currently passes, however, systemd-shim remains installed. It
>   should be removed instead. Apt install systemd should have lines like
>   this:
>
>   The following packages will be REMOVED:
> systemd-shim
>   ...
>   Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>   ...
>
>
>   [Regression Potential]
>
>* systemd-shim/upstart are both removed and not supported in bionic,
>   thus forcing their removal via conflicts should bring the system into
>   an expected state.
>
>   [Other Info]
>
>* original bug report
>
>   $ sudo apt upgrade
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   Calculating upgrade... Done
>   The following packages will be REMOVED:
> systemd-shim
>   0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>   1 not fully installed or removed.
>   After this operation, 71.7 kB disk space will be freed.
>   Do you want to continue? [Y/n] y
>   (Reading database ... 63 files and directories currently installed.)
>   Removing systemd-shim (9-1bzr4ubuntu1) ...
>   Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>   dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
> different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
>   dpkg: error processing package systemd-shim (--remove):
>subprocess installed post-removal script returned error exit status 2
>   Errors were encountered while processing:
>systemd-shim
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>   Commenting out the dpkg-divert in systemd-shim's postrm solved this
>   for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
>

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Triaged
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  

Re: [Touch-packages] [Bug 1823985] Re: isc-dhcp-server can't load leases file with apparmor enabled

[Seth Arnold]

On Wed, Apr 10, 2019 at 08:34:47AM -, Lars wrote:
> [root@myhost:~]↥ 1 # namei -l /test/var/lib/dhcp/dhcpd.leases
> f: /test/var/lib/dhcp/dhcpd.leases
> drwxr-xr-x root  root  /
> drwxr-xr-x dhcpd dhcpd test
> drwxr-xr-x dhcpd dhcpd var
> drwxr-xr-x dhcpd dhcpd lib
> drwxr-xr-x dhcpd dhcpd dhcp
> -rw-r--r-- dhcpd dhcpd dhcpd.leases

Note that these permissions don't allow root to write to this file UNLESS
root uses the CAP_DAC_OVERRIDE permission is used.

Thanks.

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

Title:
  isc-dhcp-server can't load leases file with apparmor enabled

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I can't start isc-dhcp-server with apparmor enabled.

  I set a custom leases file in the dhcpd.conf:
   lease-file-name "/test/var/lib/dhcp/dhcpd.leases";

  and created a custom apparmor profile for that in 
/etc/apparmor.d/local/usr.sbin.dhcpd:
  /test/var/lib/dhcp/dhcpd{,6}.leases* lrw,

  But when I try to start I see the following errors from dhcpd:

  Internet Systems Consortium DHCP Server 4.3.5
  Copyright 2004-2016 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/
  Config file: /etc/dhcp/dhcpd.conf
  Database file: /test/var/lib/dhcp/dhcpd.leases
  PID file: /run/dhcp-server/dhcpd.pid
  Can't open /test/var/lib/dhcp/dhcpd.leases for append.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.

  
  And in the messages log I can see errors like this:

  Apr  9 17:07:03.601 myhost dhcpd[27361]: Can't open 
/test/var/lib/dhcp/dhcpd.leases for append.
  Apr  9 17:07:03.601 myhost dhcpd[27361]:
  Apr  9 17:07:03.601 myhost dhcpd[27361]: If you think you have received this 
message due to a bug rather
  Apr  9 17:07:03.601 myhost dhcpd[27361]: than a configuration issue please 
read the section on submitting
  Apr  9 17:07:03.601 myhost dhcpd[27361]: bugs on either our web page at 
www.isc.org or in the README file
  Apr  9 17:07:03.601 myhost dhcpd[27361]: before submitting a bug.  These 
pages explain the proper
  Apr  9 17:07:03.601 myhost dhcpd[27361]: process and the information we find 
helpful for debugging..
  Apr  9 17:07:03.601 myhost dhcpd[27361]:
  Apr  9 17:07:03.601 myhost dhcpd[27361]: exiting.
  Apr  9 17:07:03.603 myhost kernel: audit: type=1400 
audit(1554822423.596:221): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1  
capname="dac_override"
  Apr  9 17:07:03.603 myhost kernel: audit: type=1400 
audit(1554822423.596:221): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=27361 comm="dhcpd" capability=1  
capname="dac_override"



  After disabling apparmor for dhcpd everything works as expected:

  ln -s /etc/apparmor.d/usr.sbin.dhcpd /etc/apparmor.d/disable/
  apparmor_parser -R /etc/apparmor.d/usr.sbin.dhcpd

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

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

[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles

[Steve Langasek]

** Changed in: console-setup (Ubuntu Cosmic)
   Status: Triaged => In Progress

** Changed in: console-setup (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: console-setup (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: console-setup (Ubuntu Cosmic)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: console-setup (Ubuntu Bionic)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: console-setup (Ubuntu Xenial)
 Assignee: (unassigned) => Steve Langasek (vorlon)

** Changed in: console-setup (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Fix Committed
Status in console-setup source package in Xenial:
  In Progress
Status in console-setup source package in Bionic:
  In Progress
Status in console-setup source package in Cosmic:
  In Progress
Status in console-setup source package in Disco:
  Fix Committed

Bug description:
  [SRU Justification]
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

    19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
    ...
    19:51:13 systemd[1]: Starting Set console font and keymap...
    19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file
    19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
    19:51:15 systemd[1]: Failed to start Set console font and keymap.
    19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
    19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
    if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
    || TMPFILE=`mktemp 2>/dev/null`

  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
    the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
    the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
    on systemd-tmpfiles-clean; let's remove the dependency
    instead of declaring it

  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
    data to answer that.

  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
    say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
    to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
    that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot

  [Test case]
  1. Install console-setup from -proposed
  2. Reboot
  3. Verify that `systemctl status console-setup` shows that the service has 
completed successfully.

  Since this is a race, additional fuzz testing may be warranted for the
  cloud images to confirm that the issue experienced in GCE is really
  fixed.  However, that should not block promotion of this SRU fix since
  there definitely is a race here that should be fixed per se even if
  there are other issues still causing a failure in GCE.

  [Regression potential]
  None known.  /run is guaranteed to be mounted rw very early in boot - 
generally before /tmp is mounted, due to /tmp being on the rootfs that needs to 
be fscked before remount.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.4
  ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18
  Uname: Linux 4.15.0-1029-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 19:24:12 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about 

[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

[Kalle Tuulos]

About var.conf, I wrote that in the initial bug report:
"My first idea was, that for some reason, systemd-tmpfiles was not able to 
create the /var directory properly, so I renamed /usr/lib/tmpfiles.d/var.conf 
to var.conf, but it was no help."

The output of "ls -lad" is as follows:

kalle@vspk:~$ ls -lad /run /var/run
drwxr-xr-x 31 root root 980 Apr 10 23:03 /run
lrwxrwxrwx  1 root root   4 May 14  2018 /var/run -> /run


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

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

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

Status in systemd package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 16.04.6 LTS
   
  Release:16.04 
   

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  systemd:  
   
Installed: 229-4ubuntu21.16 
   
Candidate: 229-4ubuntu21.16 
   
Version table:  
   
   *** 229-4ubuntu21.16 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages  
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status  
   
   229-4ubuntu4 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages   
 

  3) What you expected to happen
  4) What happened instead

  Ubuntu server (running in OpenVZ VPS farm, thus the old kernel
  version) has been up and running happily, until I performed apt-get
  upgrade and rebooted the server. After reboot, I could not establish
  SSH connection to server, port 22 connection was refused.

  I opened a HTML console to my server instance and checked logs. From
  the logs, it was shown, that SSH server could not start, as it did not
  have the /var/run/sshd directory. After scrolling back the
  /var/log/syslog, I noticed that there were lots of other /var/run
  subdirectories, which were not created. Here is cut from
  /var/log/syslog, related to systemd-tmpfiles:

  ---8<---8<---
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: 
[/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v
  ar/log", ignoring.
   
  Mar  6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: 
Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/fail2ban: Too many levels of symb
  olic links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/screen: Too many levels of symbol
  ic links  
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sshd: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo/ts: Too many levels of symbo
  lic links 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: 
Invalid argument  
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif 
failed: Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of 
/run/systemd/netif/links failed: Invalid 

[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles

[Steve Langasek]

** Description changed:

+ [SRU Justification]
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.
  
-   19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
-   ...
-   19:51:13 systemd[1]: Starting Set console font and keymap...
-   19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file   
-   19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
-   19:51:15 systemd[1]: Failed to start Set console font and keymap.
-   19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
-   19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
- ...
+   19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
+   ...
+   19:51:13 systemd[1]: Starting Set console font and keymap...
+   19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file
+   19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
+   19:51:15 systemd[1]: Failed to start Set console font and keymap.
+   19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
+   19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
+ ...
  
  /bin/setupcon has a lovely tempfile function that looks like:
-   if \
- TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
-   || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
-   || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
-   || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
-   || TMPFILE=`mktemp 2>/dev/null`
+   if \
+ TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
+   || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
+   || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
+   || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
+   || TMPFILE=`mktemp 2>/dev/null`
  
  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
-   the tmp cleaner, to delete files that have just been created
+   the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
-   the ordering of the systemd units on startup
+   the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
-   on systemd-tmpfiles-clean; let's remove the dependency
-   instead of declaring it
+   on systemd-tmpfiles-clean; let's remove the dependency
+   instead of declaring it
  
  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
-   data to answer that.
+   data to answer that.
  
  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
-   say "yep, nothing to do here" and exit
+   say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
-   to complete AIUI
+   to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
-   that will happen
+   that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot
+ 
+ [Test case]
+ 1. Install console-setup from -proposed
+ 2. Reboot
+ 3. Verify that `systemctl status console-setup` shows that the service has 
completed successfully.
+ 
+ Since this is a race, additional fuzz testing may be warranted for the
+ cloud images to confirm that the issue experienced in GCE is really
+ fixed.  However, that should not block promotion of this SRU fix since
+ there definitely is a race here that should be fixed per se even if
+ there are other issues still causing a failure in GCE.
+ 
+ [Regression potential]
+ None known.  /run is guaranteed to be mounted rw very early in boot - 
generally before /tmp is mounted, due to /tmp being on the rootfs that needs to 
be fscked before remount.  
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.4
  ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18
  Uname: Linux 4.15.0-1029-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 19:24:12 2019
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

[Dan Streetman]

** Tags added: sts-sponsor-ddstreet

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed
Status in openldap package in Debian:
  New

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
     Memory: 712.6M
     CGroup: /system.slice/slapd.service
     └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  6) Check if systemd has loaded both
  /run/systemd/generator.late/slapd.service &
  /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf

  $ systemctl cat slapd

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

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

[loluchayjose]

Looks like I can't install anything (or most things) until this gets
fixed. Is there a consensus on the proper way to uninstall systemd-shim?

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Triaged
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

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

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

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

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

[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles

[Steve Langasek]

** Changed in: console-setup (Ubuntu Disco)
   Status: Triaged => Fix Committed

** Changed in: console-setup (Ubuntu Disco)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Fix Committed
Status in console-setup source package in Bionic:
  Triaged
Status in console-setup source package in Cosmic:
  Triaged
Status in console-setup source package in Disco:
  Fix Committed

Bug description:
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
...
19:51:13 systemd[1]: Starting Set console font and keymap...
19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file   
19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
19:51:15 systemd[1]: Failed to start Set console font and keymap.
19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp 2>/dev/null`

  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
on systemd-tmpfiles-clean; let's remove the dependency
instead of declaring it

  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
data to answer that.

  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.4
  ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18
  Uname: Linux 4.15.0-1029-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 19:24:12 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1824227/+subscriptions

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

[Touch-packages] [Bug 1824227] [NEW] console-setup failure due to race with systemd-tmpfiles

[Robert C Jennings]

Public bug reported:

I'm seeing a console-setup.service failure quite regularly in testing
where the temp file that should have been created can't be found.
This is a regular xenial cloud image.

  19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
  ...
  19:51:13 systemd[1]: Starting Set console font and keymap...
  19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file   
  19:51:15 systemd[1]: console-setup.service: Main process exited, code=exited, 
status=1/FAILURE
  19:51:15 systemd[1]: Failed to start Set console font and keymap.
  19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
  19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
...

/bin/setupcon has a lovely tempfile function that looks like:
  if \
TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
  || TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
  || TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
  || TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
  || TMPFILE=`mktemp 2>/dev/null`

Here's our edited IRC conversation on the bug:
<@vorlon> so I do think you're being hit by the tmp cleaner
<@vorlon> also this seems like bad pathological default behavior for
  the tmp cleaner, to delete files that have just been created
<@vorlon> but we should fix console-setup to not rely on /tmp
<@vorlon> and I prefer that we do that instead of trying to fiddle with
  the ordering of the systemd units on startup
<@vorlon> i.e. console-setup has an undeclared dependency
  on systemd-tmpfiles-clean; let's remove the dependency
  instead of declaring it

<@vorlon> are you failing the race more often now than in the past?
<@rcj>vorlon: it feels like it's failing more often but I don't have
  data to answer that.

<@vorlon> are we shipping an image with a dirty rootfs?
<@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
  say "yep, nothing to do here" and exit
<@vorlon> in the sense that this is what would make dev-sda1.device slow
  to complete AIUI
<@rcj>would filesystem resize on first boot mark it dirty?  Because
  that will happen
<@vorlon> huh good question
<@vorlon> it might
rcj, unclean shutdown?
<@rcj>xnox: first boot

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: console-setup 1.108ubuntu15.4
ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18
Uname: Linux 4.15.0-1029-gcp x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Apr 10 19:24:12 2019
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: console-setup (Ubuntu Bionic)
 Importance: High
 Status: Triaged

** Affects: console-setup (Ubuntu Cosmic)
 Importance: High
 Status: Triaged

** Affects: console-setup (Ubuntu Disco)
 Importance: High
 Status: Triaged


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

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Triaged
Status in console-setup source package in Bionic:
  Triaged
Status in console-setup source package in Cosmic:
  Triaged
Status in console-setup source package in Disco:
  Triaged

Bug description:
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
...
19:51:13 systemd[1]: Starting Set console font and keymap...
19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file   
19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
19:51:15 systemd[1]: Failed to start Set console font and keymap.
19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp 2>/dev/null`

 

[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles

[Steve Langasek]

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => High

** Changed in: console-setup (Ubuntu)
   Status: New => Triaged

** Also affects: console-setup (Ubuntu Disco)
   Importance: High
   Status: Triaged

** Also affects: console-setup (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: console-setup (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: console-setup (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: console-setup (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: console-setup (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: console-setup (Ubuntu Cosmic)
   Importance: Undecided => High

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Triaged
Status in console-setup source package in Bionic:
  Triaged
Status in console-setup source package in Cosmic:
  Triaged
Status in console-setup source package in Disco:
  Triaged

Bug description:
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
...
19:51:13 systemd[1]: Starting Set console font and keymap...
19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file   
19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
19:51:15 systemd[1]: Failed to start Set console font and keymap.
19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp 2>/dev/null`

  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
on systemd-tmpfiles-clean; let's remove the dependency
instead of declaring it

  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
data to answer that.

  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.4
  ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18
  Uname: Linux 4.15.0-1029-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 19:24:12 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1824227/+subscriptions

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

[Touch-packages] [Bug 1824227] Re: console-setup failure due to race with systemd-tmpfiles

[Robert C Jennings]

** Attachment added: "journal"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+attachment/5254776/+files/journal

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

Title:
  console-setup failure due to race with systemd-tmpfiles

Status in console-setup package in Ubuntu:
  Triaged
Status in console-setup source package in Bionic:
  Triaged
Status in console-setup source package in Cosmic:
  Triaged
Status in console-setup source package in Disco:
  Triaged

Bug description:
  I'm seeing a console-setup.service failure quite regularly in testing
  where the temp file that should have been created can't be found.
  This is a regular xenial cloud image.

19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate 
line for path "/var/log", ignoring.
...
19:51:13 systemd[1]: Starting Set console font and keymap...
19:51:15 setupcon[455]: /bin/setupcon: 809: /bin/setupcon: cannot open 
/tmp/tmpkbd.a8FGSs: No such file   
19:51:15 systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
19:51:15 systemd[1]: Failed to start Set console font and keymap.
19:51:15 systemd[1]: console-setup.service: Unit entered failed state.
19:51:15 systemd[1]: console-setup.service: Failed with result 'exit-code'.
  ...

  /bin/setupcon has a lovely tempfile function that looks like:
if \
  TMPFILE=`mktemp /tmp/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /run/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /dev/.tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp /lib/init/rw/tmpkbd.XX 2>/dev/null` \
|| TMPFILE=`mktemp 2>/dev/null`

  Here's our edited IRC conversation on the bug:
  <@vorlon> so I do think you're being hit by the tmp cleaner
  <@vorlon> also this seems like bad pathological default behavior for
the tmp cleaner, to delete files that have just been created
  <@vorlon> but we should fix console-setup to not rely on /tmp
  <@vorlon> and I prefer that we do that instead of trying to fiddle with
the ordering of the systemd units on startup
  <@vorlon> i.e. console-setup has an undeclared dependency
on systemd-tmpfiles-clean; let's remove the dependency
instead of declaring it

  <@vorlon> are you failing the race more often now than in the past?
  <@rcj>vorlon: it feels like it's failing more often but I don't have
data to answer that.

  <@vorlon> are we shipping an image with a dirty rootfs?
  <@vorlon> dirty in the sense that e2fsck doesn't take one look at it,
say "yep, nothing to do here" and exit
  <@vorlon> in the sense that this is what would make dev-sda1.device slow
to complete AIUI
  <@rcj>would filesystem resize on first boot mark it dirty?  Because
that will happen
  <@vorlon> huh good question
  <@vorlon> it might
  rcj, unclean shutdown?
  <@rcj>xnox: first boot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: console-setup 1.108ubuntu15.4
  ProcVersionSignature: User Name 4.15.0-1029.31~16.04.1-gcp 4.15.18
  Uname: Linux 4.15.0-1029-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 19:24:12 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1824227/+subscriptions

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

[Touch-packages] [Bug 1659534] Reminder of SRU verification policy change

[Brian Murray]

Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

Title:
  userdel doesn't supports extrausers

Status in Snappy:
  In Progress
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Committed

Bug description:
  TEST CASE:
  - run userdel --extrausers foo on a ubuntu core system

  REGRESSION POTENTIAL:
  - low, this option will only take effect when "userdel --extrauser" is used.

  On an Ubuntu Core system is impossible to delete an user from the
  extrausers db:

  root@localhost:/# userdel --extrausers alice
  userdel: unrecognized option '--extrausers'

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

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

[Touch-packages] [Bug 1818814] Re: systemd-tmpfiles-setup.services fails to create /var/run directories

[Dan Streetman]

Did you create/copy this file yourself?  systemd drops the var.conf file
there, not var.conf...not that I see any reason it would cause any
problems, but it shouldn't be there.

/usr/lib/tmpfiles.d/var.conf


What does your /var/run and /run dirs look like?

$ ls -lad /run /var/run

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

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

Title:
  systemd-tmpfiles-setup.services fails to create /var/run directories

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 16.04.6 LTS
   
  Release:16.04 
   

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  systemd:  
   
Installed: 229-4ubuntu21.16 
   
Candidate: 229-4ubuntu21.16 
   
Version table:  
   
   *** 229-4ubuntu21.16 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages  
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status  
   
   229-4ubuntu4 500 
   
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages   
 

  3) What you expected to happen
  4) What happened instead

  Ubuntu server (running in OpenVZ VPS farm, thus the old kernel
  version) has been up and running happily, until I performed apt-get
  upgrade and rebooted the server. After reboot, I could not establish
  SSH connection to server, port 22 connection was refused.

  I opened a HTML console to my server instance and checked logs. From
  the logs, it was shown, that SSH server could not start, as it did not
  have the /var/run/sshd directory. After scrolling back the
  /var/log/syslog, I noticed that there were lots of other /var/run
  subdirectories, which were not created. Here is cut from
  /var/log/syslog, related to systemd-tmpfiles:

  ---8<---8<---
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: 
[/usr/lib/tmpfiles.d/00rsyslog.conf:6] Duplicate line for path "/v
  ar/log", ignoring.
   
  Mar  6 12:32:54 vspk systemd[1]: Starting Raise network interfaces... 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/named failed: 
Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/fail2ban: Too many levels of symb
  olic links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/screen: Too many levels of symbol
  ic links  
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sshd: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo: Too many levels of symbolic
   links
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/sudo/ts: Too many levels of symbo
  lic links 
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/utmp failed: 
Invalid argument  
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/systemd/netif 
failed: Invalid argument 
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument  
  Mar  6 12:32:54 

[Touch-packages] [Bug 1823550] Re: GtkSourceView wrongly has monospaced font in dropdown (context) menu

[Khurshid Alam]

@Norbert

No, I actually wanted you to change the font from gedit preference. For
example select purisha oblique.

Reset geit pref. Install tweak-tool. Try changing monospace font. It
will change both context menu and soureview font.

But I think you are right by default it is set to monospace font. But
you can force it to use other fonts.

And yes this can be set in the theme too.

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

Title:
  GtkSourceView wrongly has monospaced font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Confirmed
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

[Dan Streetman]

autopkgtest regressions, cosmic:

re-running:

systemd (various) : some of the archs fail frequently, but i'll try re-
running again

ignore:

linux (various) : tests very flaky, fail more often than pass
docker.io (various) : snapd appears to have broken this test
snapd (various) : snapd appears to have also broken this test
(snapd in bionic is also likely to be failing due to snapd problems)

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

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

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

[Dan Streetman]

autopkgtest regressions, bionic:

re-running:

apt (i386) : re-running; test seems flaky (random failures in previous runs)
dovecot (arm64) : re-running, test seems flaky (same failure in previous runs)


ignore:

systemd (ppc64el) : existing failure bug 1821625
linux (various) : tests very flaky, fail more often than pass
snapd (various) : test seems to install lots from github,
  no idea what it's unhappy about;
  started failing before our package was uploaded
mariadb (various) : always failed.
linux-aws-edge (amd64) : always failed.

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

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

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files

[Dan Streetman]

as this upload covers two bugs, let's put the autopkgtest regression
analysis into the other bug 1818282

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

Title:
  networkd: [Route] PreferredSource not working in *.network files

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Users cannot create IPv6 routes that specify PreferredSource. This
  means that users cannot specify a number of valid IPv6 routes that are
  useful in some circumstances. These routes can be created with the
  'ip' tool, just not with systemd.

  This was reported upstream in systemd issue #5882 is fixed by pulling
  in the changes in systemd PR #11375 -
  https://github.com/systemd/systemd/pull/11375

  [Test Case]

  Start a Bionic or Cosmic VM.

  Add the following netplan yaml (adjust for ethernet card and MAC):

  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:e2:c2:d7
  set-name: ens3
  addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"]
  routes:
    - to: "a::/16"
  via: "fd8f:1d7d:b141::1"
  from: "fd8f:1d7d:b141::2"
    - to: "fd8f:1d7d:b141::/64"
  scope: link
  from: "fd8f:1d7d:b141::2"
  metric: 255

  Run netplan apply or reboot. Wait ~10s.

  Alternately, to test without netplan, configure systemd-networkd with:

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=fd8f:1d7d:b141::2/64
  Address=fd8f:1d7d:b141::200/64

  [Route]
  Destination=a::/16
  Gateway=fd8f:1d7d:b141::1
  PreferredSource=fd8f:1d7d:b141::2

  [Route]
  Destination=fd8f:1d7d:b141::/64
  PreferredSource=fd8f:1d7d:b141::2
  Scope=link
  Metric=255

  [DHCP]
  UseMTU=true
  RouteMetric=100


  Currently, ip -6 route will not include a route to "a::/16", and will
  not include the route to "fd8f:1d7d:b141::/64" that has
  "fd8f:1d7d:b141::2" as the source address - both those addresses will
  be missing.

  Correct behaviour is for ip -6 route to report the following:

  ubuntu@b-np:~$ ip -6 route
  a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 
metric 1024 pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 
pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium
  fe80::/64 dev ens3 proto kernel metric 256 pref medium

  Check before and after upgrade that 'systemctl status network-
  online.target' shows that the target has been reached.

  [Regression Potential]

  This changes the state machine in systemd which configures the links.
  It passes systemd's internal tests, and has been approved by systemd
  maintainers, but it remains possible that the changes will break the
  configuration of obscure network setups.

  The backport requires pulling in two further commits that also change
  behaviour: currently systemd deletes all addresses and routes that
  were attached to an interface. With this change, it will only delete
  those that are not specified in the configuration files. A side effect
  of this is that restarting networkd will not cause remove/add netlink
  events to be emitted for these addresses, so if anyone is relying on
  this behavior this will break compatibility; but that is an unlikely
  thing to be relying on, and it seems worth this risk to reduce
  unnecessary network state changes.

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

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Dan Streetman]

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

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

** Changed in: ureadahead (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: ureadahead (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Won't Fix
Status in ureadahead source package in Xenial:
  In Progress
Status in ureadahead source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  ureadahead logs thousands of lines of useless noise on each boot.

  [test case]

  install bionic on physical hardware (ureadhead doesn't run under virt)
  and check the boot logs:

  #journalctl -m | grep ureadahead | wc -l
  30244

  
  ureadahead stores its data in /var/lib/ureadahead/pack so on future boots, it 
doesn't print as many noise messages (if any), until the pack file is a month 
or more old, at which time it recreates it (at the next boot) and prints all 
the noise out again.

  to reproduce this test case without waiting a month, just remove the
  pack file and reboot.

  
  [regression potential]

  very little, adding the -q param only causes libnih to switch to quiet
  mode.  any regression would likely be around ureadahead not starting
  at all, which really wouldn't be that bad anyway, as ureadahead has
  been removed entirely from Ubuntu starting in cosmic.

  [other info]

  original description:

  --

  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts

[Dan Streetman]

can you paste the output of dig:

$ dig phspi05 @192.168.2.1

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

Title:
  DNS lookup fails for local hosts

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

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

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

[Touch-packages] [Bug 1823516] Re: Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland sessions

[Nico Jakob]

Is there anything one can do to help resolving this issue?

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

Title:
  Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland
  sessions

Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Nvidia-418 installed but apps are using LLVMpipe/Mesa in Wayland
  sessions.

  I am using kernel parameter nvidia-drm.modeset=1, which is required to
  get the "Ubuntu on Wayland" option. But after logging in I see:

  $ glxinfo | grep OpenGL
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 19.0.1
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  $ es2_info | grep ^GL
  GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1
  GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nvidia-driver-418 418.56-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  Date: Sun Apr  7 17:26:07 2019
  InstallationDate: Installed on 2018-12-04 (124 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: nvidia-graphics-drivers-418
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures

[Bug Watch Updater]

** Changed in: perl (Debian)
   Status: Unknown => Fix Released

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

Title:
  mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by
  executing perl script, multiple architectures

Status in The Ubuntu-power-systems project:
  Fix Released
Status in perl package in Ubuntu:
  Fix Released
Status in perl source package in Disco:
  Fix Released
Status in perl package in Debian:
  Fix Released

Bug description:
  == Comment: #0 - NAGENDRA P. DONTAMSETTY  - 2019-02-28 
00:14:49 ==
  ---Problem Description---
  Perl core dumping core on UBUNTU 19.04 by executing perl script
   
  ---uname output---
  root@p8ct1p13:/tmp# uname -a Linux p8ct1p13.in.ibm.com 4.19.0-13-generic 
#14-Ubuntu SMP Thu Feb 7 21:50:00 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ppc64le and power8 
   
  ---Debugger Data---
  root@p8ct1p13:/tmp# file core
  core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1 
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1 
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0, 
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
   
   
  ---Steps to Reproduce---
   Description:  Perl core dumpinmg core on UBUNTU 19.04 by exec cmd "mkrsrc"

  
  root@p8ct1p13:/tmp# uname -a
  Linux p8ct1p13.in.ibm.com 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:50:00 
UTC 2019 ppc64le ppc64le ppc64le GNU/Linux

  
  root@p8ct1p13:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="19.04 (Disco Dingo)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
  VERSION_ID="19.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  
  root@p8ct1p13:~# ctversion -bv
  RSCT_Build_Name=rsholxs002a 3.2.4.2 RSCT_Build_Time=19043.16:11:49 
RSCT_Build_Context=ppc64le_linux_2

  
  root@p8ct1p13:/tmp# mkrsrc IBM.Ray Name="fvt1" 
NodeNameList={"p8ct1p09.in.ibm.com"} ManualMode=0 Int32=00 String="Initial Test 
String 2"
  perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
  Aborted (core dumped)

  root@p8ct1p13:/tmp# file core
  core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1 
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1 
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0, 
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'

  
  root@p8ct1p13:/tmp# which mkrsrc
  /usr/bin/mkrsrc

  root@p8ct1p13:/tmp# file /usr/bin/mkrsrc

  /usr/bin/mkrsrc: symbolic link to /opt/rsct/bin/mkrsrc

  root@p8ct1p13:/tmp# file /opt/rsct/bin/mkrsrc
  /opt/rsct/bin/mkrsrc: Perl script text executable
   
  Contact Information = Nagendra Dontamsetty/ndont...@in.ibm.com, 
Anirban/anirb...@in.ibm.com 
   
  Userspace tool common name: perl 5 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace rpm: ii  perl  5.28.1-4
  ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Nagendra Dontamsetty/ndont...@in.ibm.com, 
Anirban/anirb...@in.ibm.com: 
  -Post a private note with access information to the machine that is currently 
in the debugger.
  -Attach ltrace and strace of userspace application.

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

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

[Touch-packages] [Bug 1210144] Re: package should include slapd headers

[Bug Watch Updater]

** Changed in: openldap (Debian)
   Status: New => Confirmed

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

Title:
  package should include slapd headers

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap package in Debian:
  Confirmed

Bug description:
  Slapd headers like portable.h, slap.h are not included in development
  package. Please include them to enable to build additional modules
  like ppolicy-check-password .

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[ausiasbcn]

They left us behind
...what a shame

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Dan Streetman]

(note that /var/lib/ureadahead/pack file removed and then system
immediately rebooted before each verification test below)


ubuntu@fili:~$ dpkg -l |grep ureadahead
ii  ureadahead0.100.0-20 
amd64Read required files in advance
ubuntu@fili:~$ journalctl -b | grep ureadahead | wc -l
3203


ubuntu@fili:~$ dpkg -l |grep ureadahead
ii  ureadahead0.100.0-21 
amd64Read required files in advance
ubuntu@fili:~$ journalctl -b | grep ureadahead| wc -l
3


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

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Won't Fix
Status in ureadahead source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  ureadahead logs thousands of lines of useless noise on each boot.

  [test case]

  install bionic on physical hardware (ureadhead doesn't run under virt)
  and check the boot logs:

  #journalctl -m | grep ureadahead | wc -l
  30244

  
  ureadahead stores its data in /var/lib/ureadahead/pack so on future boots, it 
doesn't print as many noise messages (if any), until the pack file is a month 
or more old, at which time it recreates it (at the next boot) and prints all 
the noise out again.

  to reproduce this test case without waiting a month, just remove the
  pack file and reboot.

  
  [regression potential]

  very little, adding the -q param only causes libnih to switch to quiet
  mode.  any regression would likely be around ureadahead not starting
  at all, which really wouldn't be that bad anyway, as ureadahead has
  been removed entirely from Ubuntu starting in cosmic.

  [other info]

  original description:

  --

  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[Seth Forshee]

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

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  In Progress
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

  Impact: iptables does not work in disco with linux-virtual.

  Fix: Add bpfilter to the generic inclusion list.

  Regression Potential: There are no code changes and thus minimal
  potential for regressions.

  Test Case: Verify that bpffilter.ko is shipped in linux-modues instead
  of linux-module-extra and that iptables commands work in disco with
  the linux-virtual kernel installed.

  ---

  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

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

[bugproxy]

--- Comment From andreas.kreb...@de.ibm.com 2019-04-10 13:00 EDT---
(In reply to comment #10)
> All of the three mentioned patches are already in Disco / 2.32 as shipped by
> Ubuntu. As we regularly apply stable branch updates. You can check that this
> code is in the branch-updates.diff.
>
> Is everything done here for Disco? Are you asking to backport this to some
> other series?

Yes. These patches are required only ontop of 2.32 and will not fit onto
older branches.

--- Comment From andreas.kreb...@de.ibm.com 2019-04-10 13:02 EDT---
(In reply to comment #12)
> (In reply to comment #10)
> > All of the three mentioned patches are already in Disco / 2.32 as shipped by
> > Ubuntu. As we regularly apply stable branch updates. You can check that this
> > code is in the branch-updates.diff.
> >
> > Is everything done here for Disco? Are you asking to backport this to some
> > other series?
>
> Yes. These patches are required only ontop of 2.32 and will not fit onto
> older branches.

Erm sorry that was misleading.

> Is everything done here for Disco?
Yes, everything done for Disco then.

> Are you asking to backport this to some other series?
No, only 2.32 needs patching.

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

Title:
  [Ubuntu] Patches on top of binutils 2.32

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Instructions change in z13 abi

  [Test Case]

   * Testsuite adjusted, and should pass.

  [Regression Potential]

   * Without these patches assembly/dissambly of code that uses renamed
  instructions will fail (z13+ abi)

  [Other Info]
   
   * Original request.

  Following patches have to be applied to binutils 2.32

  - S/390: arch13: Adjust to recent changes
  commit e49edb49713e435b8441bb5a9bd0c10d9df84e2f

  - S/390: arch13: Add instruction descriptions
  commit d98eed0923af29043ce18da43d2a242191d44ceb

  - Revert "Add support to GNU ld to separate got related plt entries"
  commit 9db2b33d363e2047df53f89ad34e7d1104299d12

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

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

[Touch-packages] [Bug 1824205] Re: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem

[Florian Richer]

Line Out it work but Headphone output doesn't appear.

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

Title:
  [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My card is detected and with ubuntu-bug all output is detected but on
  Sound Control only SPDIF Output is showed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:47:50 2019
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
  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.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B09
  dmi.product.sku: To be filled by O.E.M.
  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/alsa-driver/+bug/1824205/+subscriptions

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

[Dan Streetman]

** Description changed:

  [impact]
  
  ureadahead logs thousands of lines of useless noise on each boot.
  
  [test case]
  
  install bionic on physical hardware (ureadhead doesn't run under virt)
  and check the boot logs:
  
  #journalctl -m | grep ureadahead | wc -l
  30244
+ 
+ 
+ ureadahead stores its data in /var/lib/ureadahead/pack so on future boots, it 
doesn't print as many noise messages (if any), until the pack file is a month 
or more old, at which time it recreates it (at the next boot) and prints all 
the noise out again.
+ 
+ to reproduce this test case without waiting a month, just remove the
+ pack file and reboot.
+ 
  
  [regression potential]
  
  very little, adding the -q param only causes libnih to switch to quiet
  mode.  any regression would likely be around ureadahead not starting at
  all, which really wouldn't be that bad anyway, as ureadahead has been
  removed entirely from Ubuntu starting in cosmic.
  
  [other info]
  
  original description:
  
  --
  
  ureadahead reports relative path errors in my journalctl output.
  
  This is currently 4368 lines of useless annoyances in my logs.
  
  To see if you have this problem, run: journalctl -b | grep ureadahead |
  grep relative | wc -l
  
  Thanks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Won't Fix
Status in ureadahead source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  ureadahead logs thousands of lines of useless noise on each boot.

  [test case]

  install bionic on physical hardware (ureadhead doesn't run under virt)
  and check the boot logs:

  #journalctl -m | grep ureadahead | wc -l
  30244

  
  ureadahead stores its data in /var/lib/ureadahead/pack so on future boots, it 
doesn't print as many noise messages (if any), until the pack file is a month 
or more old, at which time it recreates it (at the next boot) and prints all 
the noise out again.

  to reproduce this test case without waiting a month, just remove the
  pack file and reboot.

  
  [regression potential]

  very little, adding the -q param only causes libnih to switch to quiet
  mode.  any regression would likely be around ureadahead not starting
  at all, which really wouldn't be that bad anyway, as ureadahead has
  been removed entirely from Ubuntu starting in cosmic.

  [other info]

  original description:

  --

  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1824203] [NEW] p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit section header

[Orion-cora]

Public bug reported:

# trust list
p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit section header
p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit section header

Description:Ubuntu 16.04.6 LTS
Release:16.04

** Affects: p11-kit (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit
  section header

Status in p11-kit package in Ubuntu:
  New

Bug description:
  # trust list
  p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit section 
header
  p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit section 
header

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

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

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

[Touch-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: iptables does not work in disco with linux-virtual.
+ 
+ Fix: Add bpfilter to the generic inclusion list.
+ 
+ Regression Potential: There are no code changes and thus minimal
+ potential for regressions.
+ 
+ Test Case: Verify that bpffilter.ko is shipped in linux-modues instead
+ of linux-module-extra and that iptables commands work in disco with the
+ linux-virtual kernel installed.
+ 
+ ---
+ 
  Fresh install of disco:
  
  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name
  
  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory
  
  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory
  
  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory
  
  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  
  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
-  TERM=screen-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=screen-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

  Impact: iptables does not work in disco with linux-virtual.

  Fix: Add bpfilter to the generic inclusion list.

  Regression Potential: There are no code changes and thus minimal
  potential for regressions.

  Test Case: Verify that bpffilter.ko is shipped in linux-modues instead
  of linux-module-extra and that iptables commands work in disco with
  the linux-virtual kernel installed.

  ---

  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Touch-packages] [Bug 1824205] [NEW] [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem

[Florian Richer]

Public bug reported:

My card is detected and with ubuntu-bug all output is detected but on
Sound Control only SPDIF Output is showed.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 18:47:50 2019
InstallationDate: Installed on 2019-04-10 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: Only some of outputs are working
Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.B0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
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.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B09
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug disco

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

Title:
  [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My card is detected and with ubuntu-bug all output is detected but on
  Sound Control only SPDIF Output is showed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:47:50 2019
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
  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.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B09
  dmi.product.sku: To be filled by O.E.M.
  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/alsa-driver/+bug/1824205/+subscriptions

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

[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

[Orion-cora]

I'm trying to make use of this in Ubuntu 14.04 with p11-kit
0.23.2-5~ubuntu16.04.1, but get the following error:

# trust list
p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit section header
p11-kit: ca-certificates.crt: BEGIN ...: pem block before p11-kit section header

Is p11-kit just too old there?

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

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

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

[Touch-packages] [Bug 1816812] Re: desktop logout delays due to missing PropertiesChanged signal

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 240-6ubuntu4

---
systemd (240-6ubuntu4) disco; urgency=medium

  * pam-systemd: use secure_getenv() rather than getenv()
CVE-2019-3842
File: debian/patches/pam-systemd-use-secure_getenv-rather-than-getenv.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f3291e9e8c3eafd0c8921cb26a0d5ee0fd563b3c

  * core: queue jobs on uninstall to generate PropertiesChanged signal.
(LP: #1816812)
File: 
debian/patches/core-when-we-uninstall-a-job-add-unit-to-dbus-queue.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=241deca98fb9a0f1ba9a6ba781f738fb31a3bd80

 -- Dimitri John Ledkov   Wed, 10 Apr 2019 01:06:03
+0100

** Changed in: systemd (Ubuntu Disco)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3842

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

Title:
  desktop logout delays due to missing PropertiesChanged signal

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  We need the fix from https://github.com/systemd/systemd/pull/11697 to
  avoid having unity (and other sessions) hanging on logout

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

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

[Touch-packages] [Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

[Balint Reczey]

Verified 1.361.3 on Xenial:

root@x-wsl:~# apt install ubuntu-wsl 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  bc wslu
Suggested packages:
  imagemagick
The following NEW packages will be installed:
  bc ubuntu-wsl wslu
0 upgraded, 3 newly installed, 0 to remove and 20 not upgraded.
Need to get 127 kB of archives.
After this operation, 500 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 bc amd64 
1.06.95-9build1 [82.6 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 wslu all 
2.0.0-0ubuntu2~16.04.0 [42.4 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 ubuntu-wsl 
amd64 1.361.3 [2,402 B]
Fetched 127 kB in 0s (425 kB/s)   
Selecting previously unselected package bc.
(Reading database ... 25734 files and directories currently installed.)
Preparing to unpack .../bc_1.06.95-9build1_amd64.deb ...
Unpacking bc (1.06.95-9build1) ...
Selecting previously unselected package wslu.
Preparing to unpack .../wslu_2.0.0-0ubuntu2~16.04.0_all.deb ...
Unpacking wslu (2.0.0-0ubuntu2~16.04.0) ...
Selecting previously unselected package ubuntu-wsl.
Preparing to unpack .../ubuntu-wsl_1.361.3_amd64.deb ...
Unpacking ubuntu-wsl (1.361.3) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Setting up bc (1.06.95-9build1) ...
Setting up wslu (2.0.0-0ubuntu2~16.04.0) ...
update-alternatives: using /usr/bin/wslview to provide /usr/bin/x-www-browser 
(x-www-browser) in auto mode
Setting up ubuntu-wsl (1.361.3) ...
root@x-wsl:~# apt-cache show ubuntu-wsl 
Package: ubuntu-wsl
Architecture: amd64
Version: 1.361.3
Priority: optional
Section: metapackages
Source: ubuntu-meta
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 45
Depends: wslu
Filename: pool/main/u/ubuntu-meta/ubuntu-wsl_1.361.3_amd64.deb
Size: 2402
MD5sum: cf67ec318212d92abf78ed2588d862f5
SHA1: 17e46726f10b40f91f7237eb83b3c0584b307fa2
SHA256: 8102641a51eab7a712a752f868a8f4e96e0a55f07b901ce4448cb02315efd548
Description-en: Ubuntu on Windows tools - Windows Subsystem for Linux 
integration
 Utilities for integrating Ubuntu well into the WSL environment.
 .
 It is also used to help ensure proper upgrades, so it is recommended that
 it not be removed.
Description-md5: 31a2c9edbae1d8c6f5ec0d556efdb9e9

root@x-wsl:~#


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

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

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

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

[Touch-packages] [Bug 1824152] Re: /usr/share/apport/whoopsie-upload-all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport/whoopsie-upload-all@166:colle

[El jinete sin cabeza]

Excellent guys!

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

Title:
  /usr/share/apport/whoopsie-upload-
  
all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport
  /whoopsie-upload-all@166:collect_info:process_report

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu26, the problem page at 
https://errors.ubuntu.com/problem/069eb695cd341ac71e40453596403139bc245c08 
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/apport/+bug/1824152/+subscriptions

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

[Touch-packages] [Bug 1823862] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1823862

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Touch-packages] [Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

[Balint Reczey]

Verified 1.417.1 on Bionic:

root@b-wsl:~# apt install ubuntu-wsl
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  wslu
Suggested packages:
  imagemagick
The following NEW packages will be installed:
  ubuntu-wsl wslu
0 upgraded, 2 newly installed, 0 to remove and 3 not upgraded.
Need to get 44.8 kB of archives.
After this operation, 256 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 wslu all 
2.0.0-0ubuntu2~18.04.0 [42.3 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 ubuntu-wsl 
amd64 1.417.1 [2448 B]
Fetched 44.8 kB in 0s (207 kB/s)
Selecting previously unselected package wslu.
(Reading database ... 28631 files and directories currently installed.)
Preparing to unpack .../wslu_2.0.0-0ubuntu2~18.04.0_all.deb ...
Unpacking wslu (2.0.0-0ubuntu2~18.04.0) ...
Selecting previously unselected package ubuntu-wsl.
Preparing to unpack .../ubuntu-wsl_1.417.1_amd64.deb ...
Unpacking ubuntu-wsl (1.417.1) ...
Setting up wslu (2.0.0-0ubuntu2~18.04.0) ...
update-alternatives: using /usr/bin/wslview to provide /usr/bin/x-www-browser 
(x-www-browser) in auto mode
Setting up ubuntu-wsl (1.417.1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
root@b-wsl:~# apt-cache show ubuntu-wsl
Package: ubuntu-wsl
Architecture: amd64
Version: 1.417.1
Priority: optional
Section: metapackages
Source: ubuntu-meta
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 47
Depends: wslu
Filename: pool/main/u/ubuntu-meta/ubuntu-wsl_1.417.1_amd64.deb
Size: 2448
MD5sum: 4e3c81855b806702a7cb99690c0999e5
SHA1: 23838fd8a2b268499baabb89bb8742a88fa00d35
SHA256: a4525f5fee12f9febdf9f71d10edb03ed8e749319f3cd411cb8e10536dbd2896
Description-en: Ubuntu on Windows tools - Windows Subsystem for Linux 
integration
 Utilities for integrating Ubuntu well into the WSL environment.
 .
 It is also used to help ensure proper upgrades, so it is recommended that
 it not be removed.
Description-md5: 31a2c9edbae1d8c6f5ec0d556efdb9e9

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

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

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

[Touch-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[James Page]

Tested with the kernel+modules linked in #22

I can confirm I was able to enable ufw and query the installed iptables
rules:

$ uname -a
Linux juju-0f0cbd-disco-testing-38 5.0.0-10-generic #11+lp1823862v201904100938 
SMP Wed Apr 10 14:40:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup

$ sudo iptables-save
# Generated by iptables-save v1.6.1 on Wed Apr 10 16:15:01 2019
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
:ufw-after-forward - [0:0]
:ufw-after-input - [0:0]
:ufw-after-logging-forward - [0:0]
:ufw-after-logging-input - [0:0]
:ufw-after-logging-output - [0:0]
:ufw-after-output - [0:0]
:ufw-before-forward - [0:0]
:ufw-before-input - [0:0]
:ufw-before-logging-forward - [0:0]
:ufw-before-logging-input - [0:0]
:ufw-before-logging-output - [0:0]
:ufw-before-output - [0:0]
:ufw-logging-allow - [0:0]
:ufw-logging-deny - [0:0]
:ufw-not-local - [0:0]
:ufw-reject-forward - [0:0]
:ufw-reject-input - [0:0]
:ufw-reject-output - [0:0]
:ufw-skip-to-policy-forward - [0:0]
:ufw-skip-to-policy-input - [0:0]
:ufw-skip-to-policy-output - [0:0]
:ufw-track-forward - [0:0]
:ufw-track-input - [0:0]
:ufw-track-output - [0:0]
:ufw-user-forward - [0:0]
:ufw-user-input - [0:0]
:ufw-user-limit - [0:0]
:ufw-user-limit-accept - [0:0]
:ufw-user-logging-forward - [0:0]
:ufw-user-logging-input - [0:0]
:ufw-user-logging-output - [0:0]
:ufw-user-output - [0:0]
-A INPUT -j ufw-before-logging-input
-A INPUT -j ufw-before-input
-A INPUT -j ufw-after-input
-A INPUT -j ufw-after-logging-input
-A INPUT -j ufw-reject-input
-A INPUT -j ufw-track-input
-A FORWARD -j ufw-before-logging-forward
-A FORWARD -j ufw-before-forward
-A FORWARD -j ufw-after-forward
-A FORWARD -j ufw-after-logging-forward
-A FORWARD -j ufw-reject-forward
-A FORWARD -j ufw-track-forward
-A OUTPUT -j ufw-before-logging-output
-A OUTPUT -j ufw-before-output
-A OUTPUT -j ufw-after-output
-A OUTPUT -j ufw-after-logging-output
-A OUTPUT -j ufw-reject-output
-A OUTPUT -j ufw-track-output
-A ufw-after-input -p udp -m udp --dport 137 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 138 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 139 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 445 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 67 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 68 -j ufw-skip-to-policy-input
-A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input
-A ufw-after-logging-forward -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW BLOCK] "
-A ufw-after-logging-input -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW BLOCK] "
-A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-forward -j ufw-user-forward
-A ufw-before-input -i lo -j ACCEPT
-A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny
-A ufw-before-input -m conntrack --ctstate INVALID -j DROP
-A ufw-before-input -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-input -p udp -m udp --sport 67 --dport 68 -j ACCEPT
-A ufw-before-input -j ufw-not-local
-A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
-A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT
-A ufw-before-input -j ufw-user-input
-A ufw-before-output -o lo -j ACCEPT
-A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-output -j ufw-user-output
-A ufw-logging-allow -m limit --limit 3/min --limit-burst 10 -j LOG 
--log-prefix "[UFW ALLOW] "
-A ufw-logging-deny -m conntrack --ctstate INVALID -m limit --limit 3/min 
--limit-burst 10 -j RETURN
-A ufw-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix 
"[UFW BLOCK] "
-A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN
-A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN
-A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN
-A ufw-not-local -m limit --limit 3/min --limit-burst 10 -j ufw-logging-deny
-A ufw-not-local -j DROP
-A ufw-skip-to-policy-forward -j DROP
-A ufw-skip-to-policy-input -j DROP
-A ufw-skip-to-policy-output -j ACCEPT
-A ufw-track-output -p tcp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-track-output -p udp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-user-limit -m limit --limit 3/min -j LOG 

[Touch-packages] [Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

[Balint Reczey]

Tested ubuntu-wsl 1.425.1 on Cosmic.

root@c-wsl:~# apt install ubuntu-wsl
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  wslu
Suggested packages:
  imagemagick
The following NEW packages will be installed:
  ubuntu-wsl wslu
0 upgraded, 2 newly installed, 0 to remove and 39 not upgraded.
Need to get 44.9 kB of archives.
After this operation, 257 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 wslu all 
2.0.0-0ubuntu2~18.10.0 [42.3 kB]
Get:2 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 ubuntu-wsl 
amd64 1.425.1 [2620 B]
Fetched 44.9 kB in 0s (118 kB/s)
Selecting previously unselected package wslu.
(Reading database ... 28284 files and directories currently installed.)
Preparing to unpack .../wslu_2.0.0-0ubuntu2~18.10.0_all.deb ...
Unpacking wslu (2.0.0-0ubuntu2~18.10.0) ...
Selecting previously unselected package ubuntu-wsl.
Preparing to unpack .../ubuntu-wsl_1.425.1_amd64.deb ...
Unpacking ubuntu-wsl (1.425.1) ...
Setting up wslu (2.0.0-0ubuntu2~18.10.0) ...
update-alternatives: using /usr/bin/wslview to provide /usr/bin/x-www-browser 
(x-www-browser) in auto mode
Setting up ubuntu-wsl (1.425.1) ...
Processing triggers for man-db (2.8.4-2) ...
root@c-wsl:~#

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

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

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

[Touch-packages] [Bug 1568143] Re: apport-kde crashed with SIGSEGV

[Laurent Bonnaud]

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1568143/+attachment/4629626/+files/JournalErrors.txt

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

Title:
  apport-kde crashed with SIGSEGV

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Random crash

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-kde 2.20.1-0ubuntu1
  Uname: Linux 4.5.0-040500-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashReports: 640:1000:136:9666180:2016-04-08 20:43:09.867370128 
+0200:2016-04-08 20:43:10.867370128 
+0200:/var/crash/_usr_share_apport_apport-kde.1000.crash
  CurrentDesktop: KDE
  Date: Fri Apr  8 20:43:03 2016
  ExecutablePath: /usr/share/apport/apport-kde
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde systemd
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f666ccc6105:mov(%rax),%rax
   PC (0x7f666ccc6105) ok
   source "(%rax)" (0x7575757575757575) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   () at 
/usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-35m-x86_64-linux-gnu.so
   QObject::~QObject() (this=, __in_chrg=) at 
kernel/qobject.cpp:987
   (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() 
(this=0x7f66691ccb40 <(anonymous 
namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, 
__in_chrg=) at accessible/qaccessiblecache_p.h:60
   (anonymous namespace)::Q_QGS_qAccessibleCache::Holder::~Holder() 
(this=0x7f66691ccb40 <(anonymous 
namespace)::Q_QGS_qAccessibleCache::innerFunction()::holder>, 
__in_chrg=) at accessible/qaccessiblecache.cpp:46
   __run_exit_handlers (status=1, listp=0x7f6670b925f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
  Title: apport-kde crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2016-03-31 (8 days ago)
  UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare staff

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

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

[Touch-packages] [Bug 1824152] Re: /usr/share/apport/whoopsie-upload-all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport/whoopsie-upload-all@166:colle

[Brian Murray]

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

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

** Tags removed: rls-dd-incoming

** Also affects: apport (Ubuntu Disco)
   Importance: High
 Assignee: Brian Murray (brian-murray)
   Status: In Progress

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

Title:
  /usr/share/apport/whoopsie-upload-
  
all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport
  /whoopsie-upload-all@166:collect_info:process_report

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu26, the problem page at 
https://errors.ubuntu.com/problem/069eb695cd341ac71e40453596403139bc245c08 
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/apport/+bug/1824152/+subscriptions

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Rainer Rohde]

Hi, I would like to be able to either add this new issue here found in
disco or create a new ticket for it, but I don't know what package to
file against.

Just like before, I opened Thunderbird to attach a file, and the file
picker comes up. I type the first few characters of my search (eg.
someone's firstname), and hit space to enter that person's lastname, but
as soon as I hit space the search stops and jumps into the folder of the
first person found. There is no way to continue searching after the
space.

So, does this fit here, or do I need a new ticket? If the latter, what
package?

Thanks.

PS: I've uploaded a new screencast (Screencast 2019-04-10 10:17:23.mp4)
to help visualize this new problem.

** Attachment added: "screencast"
   
https://bugs.launchpad.net/ubuntu-gnome/+bug/1592177/+attachment/5254723/+files/Screencast%202019-04-10%2010%3A17%3A23.mp4

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)

[Bug Watch Updater]

** Changed in: sysvinit (Debian)
   Status: New => Incomplete

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

Title:
  Network is brought down before network filesystems are unmounted (CIFS
  timeout at shutdown)

Status in dbus package in Ubuntu:
  Fix Released
Status in dhcdbd package in Ubuntu:
  Invalid
Status in netbase package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Fix Released
Status in dhcdbd source package in Lucid:
  Invalid
Status in dhcdbd source package in Natty:
  Invalid
Status in sysvinit package in Debian:
  Incomplete

Bug description:
  IMPORTANT: this bug has enough information; please don't post
  _anything_ unless a developer asks for specific feedback! By posting
  to this bug you only make it harder for a developer to spot the gem
  comments. Please use the "me too feature" of launchpad to signal that
  you are affected and would like to see this fixed.

  I installed smbfs,and then put some entries into /etc/fstab, so they 
automount on startup. An example of this is here:
  ///  /home/hamish/  cifs  
credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
  0  0

  ** note the use of "cifs" in the lines above **

  (The username and password are in the .smbcredentials file)

  On startup, for each entry in the /etc/fstab file, I get the following in 
dmesg:
  [   70.495504]  CIFS VFS: Error connecting to IPv4 socket. Aborting operation
  [   70.495569]  CIFS VFS: cifs_mount failed w/return code = -101
  But the shares are mounted, and a nautilus session opens up (which is also 
annoying...)

  Also logging off with CIFS shares mounted in /etc/fstab, it sits with an 
error message:
  CIFS VFS: server not responding
  CIFS VFS: no response for cmd 50 mid 
  And takes about 2 minutes to timeout. This also happened with Gutsy

  Should the timing of the mounting and dismounting be changed so that
  it works? It is related to the starting of network-manager and CIFS
  shares trying to connect on startup *before* the network is up, and
  dismounting the shares *after* network-manager is stopped.

  Hamish

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

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

[Touch-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

[Seth Forshee]

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

** This bug has been marked a duplicate of bug 1823862
   disco: unable to use iptables/enable ufw under -virtual kernel

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)

[Olivier Tilloy]

** Changed in: librsvg (Ubuntu Disco)
   Status: Confirmed => In Progress

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg package in Ubuntu:
  In Progress
Status in librsvg source package in Disco:
  In Progress

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

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

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

[Touch-packages] [Bug 1823862] Re: disco: unable to use iptables/enable ufw under -virtual kernel

[Seth Forshee]

All that seems to be missing is bpffilter. I've made a test build with
this moved to linux-modules. It appears to be working for check-
requirements. Can you test and make sure everything is working as
expected? Thanks!

http://people.canonical.com/~sforshee/lp1823862/

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Fernando]

Thanks for the info about snaps, I somehow thought that they get the
file picker from the system, I don't really know how they work. Then, we
keep the tag verification-done-bionic and I'll wait until this GTK fix
arrives at snaps to test it. Thanks for your great work!

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Sebastien Bacher]

> Nevertheless, if I open a file dialog and start typing, the default
behaviour is still typeahead. I do not whether this is intended or
should also be fixed.

That's the intended behaviour, we don't want to change that in a stable
serie but just fix the focus bug. Thanks for confirming the fix works as
intended!


> Sorry, the bug is not fixed in snaps, but it is fixed in regular applications.

Right, that's because the gtk version in the snap platform doesn't
include that fix yet

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)

[Launchpad Bug Tracker]

This bug was fixed in the package unity-tweak-tool - 0.0.7+-0ubuntu5

---
unity-tweak-tool (0.0.7+-0ubuntu5) disco; urgency=medium

  * Switch to source format 3.0 (quilt), because this in not a native package
  * Use nemo-desktop to draw desktop icons under Unity (LP: #1814506)
  * Specify GTK version 3 to fix warning (LP: #1575485)
  * Add required dependency on notify-osd (LP: #1822472)
  * Add missing build dependency on dh-python
  * Drop ancient X-Python3-Version field
  * Run wrap-and-sort

 -- Benjamin Drung   Wed, 10 Apr 2019
14:36:41 +0200

** Changed in: unity-tweak-tool (Ubuntu)
   Status: New => Fix Released

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

Title:
  Use nemo-desktop to draw desktop icons under Unity (Disco)

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-tweak-tool package in Ubuntu:
  Fix Released

Bug description:
  As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have
  the desktop any more. The alternate options are to use caja-desktop or
  nemo-desktop keeping nautilus default file manger for now. Since nemo-
  desktop does not require any extensive patching it is easy to use
  under unity.

  Nemo-desktop will only draw the icons, not the background. In absence of
  nautilus unity-settings-daemon draws the background, so nothing to do in 
u-s-d.

  There are few small patches (nemo action files) required from nemo. 
@fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship 
  these action files ourselves as recommended by upstream. Budgie is doing the 
same.
  
https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions

  
  Since nautilus still be default file-manager we disable auto-mount with nemo 
and various other cinnamon/nemo option in ubuntu-settings.gsettings-override

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

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Fernando]

Sorry, the bug is not fixed in snaps, but it is fixed in regular
applications.

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1447148] Re: broken apport hook

[Laurent Bonnaud]

This bug no longer exists.


** Changed in: network-manager (Ubuntu)
   Status: New => Fix Released

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

Title:
  broken apport hook

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Reporting a bug in network-manager with ubuntu-bug, leads to this
  error:

   nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with
  exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

  (as can be seen at the end of this bug report :>)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  Uname: Linux 4.0.0-04-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 22 14:31:54 2015
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.11
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-20 (1 days ago)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  READONLY  DBUS-PATH  
 ACTIVE  DEVICE  STATE  ACTIVE-PATH 
   
   Wired connection 1  dbecefc9-ce36-429a-952e-5df76b594328  802-3-ethernet  
1429705873  Wed 22 Apr 2015 02:31:13 PM CEST  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes eth0activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth0ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  dbecefc9-ce36-429a-952e-5df76b594328  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Fernando]

libgtk-3-0/bionic-proposed,now 3.22.30-1ubuntu3 amd64 [installed]

This fixes the problem, this means that clicking on the magnifier button
I can search without the cursor jumping to the typeahead old behavior.
Nevertheless, if I open a file dialog and start typing, the default
behaviour is still typeahead. I do not whether this is intended or
should also be fixed.

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

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1824097] Re: [Ubuntu] Patches on top of binutils 2.32

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2019-04-10 10:21 EDT---
Changed target milestone to 19.4 . thx for checking this

** Tags removed: targetmilestone-inin1804
** Tags added: targetmilestone-inin1904

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

Title:
  [Ubuntu] Patches on top of binutils 2.32

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Instructions change in z13 abi

  [Test Case]

   * Testsuite adjusted, and should pass.

  [Regression Potential]

   * Without these patches assembly/dissambly of code that uses renamed
  instructions will fail (z13+ abi)

  [Other Info]
   
   * Original request.

  Following patches have to be applied to binutils 2.32

  - S/390: arch13: Adjust to recent changes
  commit e49edb49713e435b8441bb5a9bd0c10d9df84e2f

  - S/390: arch13: Add instruction descriptions
  commit d98eed0923af29043ce18da43d2a242191d44ceb

  - Revert "Add support to GNU ld to separate got related plt entries"
  commit 9db2b33d363e2047df53f89ad34e7d1104299d12

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

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

[Touch-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

[Dan Watkins]

I can also confirm that installing linux-modules-extra-5.0.0-8-generic
(which also pulls in crda iw libnl-genl-3-200 wireless-regdb) caused
this problem to no longer appear.

(I'm happy for this to be marked duplicate, but I wonder if there's
still an iptables bug, given that memory allocation is perhaps not the
real problem it's hitting?)

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1823578] Re: scp doesn't work; required GLIBC versions not found; connection lost

[Robie Basak]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Yes - scp calls scp at the remote end. I think it's likely that the
error you're seeing is produced by the remote end, so I'm marking this
bug Invalid. If this turns out to be incorrect, feel free to explain and
change the bug status back to New. Thanks!

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

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

Title:
  scp doesn't work; required GLIBC versions not found; connection lost

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Command:
  scp -r '/home/talib/Desktop/Week 2 Lab' 
talib.pier...@syccuxas01.pcc.edu:/home/student/talib.pierson/
  Password:
  scp: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by scp)
  scp: /lib64/libc.so.6: version `GLIBC_2.26' not found (required by scp)
  lost connection

  Notes:
  ldd (Ubuntu GLIBC 2.28-0ubuntu1) 2.28

  libc6 is already the newest version (2.28-0ubuntu1)

  I created symlink to libc.so.6 to see if that was the problem:
  sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6
  yet the problem persisted

  Does this have anything to do with
  [https://wiki.ubuntu.com/MultiarchSpec Multiarch]?

  
  List installed packages:
  glibc-doc-reference/cosmic,cosmic,now 2.27-1 all [installed]
  glibc-doc/cosmic,cosmic,now 2.28-0ubuntu1 all [installed]
  glibc-source/cosmic,cosmic,now 2.28-0ubuntu1 all [installed]
  libc6-amd64/cosmic,now 2.28-0ubuntu1 i386 [installed]
  libc6-dbg/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6-dev/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6-pic/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6/cosmic,now 2.28-0ubuntu1 amd64 [installed]
  libc6/cosmic,now 2.28-0ubuntu1 i386 [installed,automatic]
  libklibc/cosmic,now 2.0.4-9ubuntu2 amd64 [installed,automatic]

  Diagnostic information:
  ldd /usr/bin/scp
  linux-vdso.so.1 (0x7ffd04f57000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92f9424000)
  /lib64/ld-linux-x86-64.so.2 (0x7f92f964a000)

  Diagnostic information:
  strings /lib64/libc.so.6 | grep GLIBC
  GLIBC_2.2.5
  GLIBC_2.2.6
  GLIBC_2.3
  GLIBC_2.3.2
  GLIBC_2.3.3
  GLIBC_2.3.4
  GLIBC_2.4
  GLIBC_2.5
  GLIBC_2.6
  GLIBC_2.7
  GLIBC_2.8
  GLIBC_2.9
  GLIBC_2.10
  GLIBC_2.11
  GLIBC_2.12
  GLIBC_2.13
  GLIBC_2.14
  GLIBC_2.15
  GLIBC_2.16
  GLIBC_2.17
  GLIBC_2.18
  GLIBC_2.22
  GLIBC_2.23
  GLIBC_2.24
  GLIBC_2.25
  GLIBC_2.26
  GLIBC_2.27
  GLIBC_2.28
  GLIBC_PRIVATE

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: openssh-client 1:7.7p1-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 17:20:03 2019
  InstallationDate: Installed on 2019-02-11 (55 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain

[Dimitri John Ledkov]

For bionic, cosmic, this is in proposed still. But will be released into
-updates soon.

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

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

** Also affects: gcc-7-cross (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gcc-8-cross (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

** Also affects: gcc-7-cross (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gcc-8-cross (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** No longer affects: binutils (Ubuntu Bionic)

** No longer affects: binutils (Ubuntu Cosmic)

** No longer affects: gcc-7-cross (Ubuntu Bionic)

** No longer affects: gcc-7-cross (Ubuntu Cosmic)

** No longer affects: gcc-8-cross (Ubuntu Bionic)

** No longer affects: gcc-8-cross (Ubuntu Cosmic)

** No longer affects: gcc-defaults (Ubuntu Bionic)

** No longer affects: gcc-defaults (Ubuntu Cosmic)

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

Title:
  Enable arm-linux-gnueabi target on ppc64el toolchain

Status in The Ubuntu-power-systems project:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-7-cross package in Ubuntu:
  Fix Released
Status in gcc-8-cross package in Ubuntu:
  Fix Released
Status in gcc-defaults package in Ubuntu:
  Fix Released

Bug description:
  Dear Canonical.

  We would like to have arm-linux-gnueabi target on ppc64el cross
  toolchain. This would enable us to use a ppc64el host to do cross
  compilation for aarch64.

  I talked to Matthias Klose already, and he is aware of this request.

  Thank you,
  Breno

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

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

[Touch-packages] [Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain

[Dimitri John Ledkov]

never mind, this is all fix-released. I have missread the output from
rmadison. So we are all good on bionic and up.

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

Title:
  Enable arm-linux-gnueabi target on ppc64el toolchain

Status in The Ubuntu-power-systems project:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-7-cross package in Ubuntu:
  Fix Released
Status in gcc-8-cross package in Ubuntu:
  Fix Released
Status in gcc-defaults package in Ubuntu:
  Fix Released

Bug description:
  Dear Canonical.

  We would like to have arm-linux-gnueabi target on ppc64el cross
  toolchain. This would enable us to use a ppc64el host to do cross
  compilation for aarch64.

  I talked to Matthias Klose already, and he is aware of this request.

  Thank you,
  Breno

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

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

[Touch-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

[Jamie Strandboge]

To be clear, when I installed linux-modules-extra-5.0.0-8-generic, I no
longer saw this error message. Of course, it might not strictly be a
duplicate, but I'll let the kernel team figure that out.

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem

[Jamie Strandboge]

FYI, I saw this when looking at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823862. In the
other bug, the reporter say a different error message, but I saw
'iptables v1.6.1: can't initialize iptables table `filter': Memory
allocation problem'. If those in this bug do not have linux-modules-
extra-5.0.0-8-generic installed, then this is a dupe of the other bug.

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

Title:
  iptables v1.6.1: can't initialize iptables table `filter': Memory
  allocation problem

Status in iptables package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I hit this error on disco:

  ```
  $ free -h
totalusedfree  shared  buff/cache   
available
  Mem:  478Mi98Mi   311Mi   0.0Ki68Mi   
366Mi
  Swap:0B  0B  0B

  $ sudo iptables -S
  iptables v1.6.1: can't initialize iptables table `filter': Memory allocation 
problem
  Perhaps iptables or your kernel needs to be upgraded.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: iptables 1.6.1-2ubuntu3
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Thu Mar 14 19:16:15 2019
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Tags:  disco uec-images
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

[Jamie Strandboge]

I can confirm that without linux-modules-extra-*, iptables is broken.

Reduced test case:
$ sudo iptables -L -n
iptables: No chain/target/match by that name.

Full test case:
$ sudo /usr/share/ufw/check-requirements -f
...
ERROR: could not create 'ufw-check-requirements'. Aborting
FAIL: check your kernel and that you have iptables >= 1.4.0

Perhaps the above should be added to image smoke tests?

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

** Summary changed:

- disco: unable to enable ufw under -virtual kernel
+ disco: unable to use iptables/enable ufw under -virtual kernel

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

Title:
  disco: unable to use iptables/enable ufw under -virtual kernel

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

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw under -virtual kernel

[Jamie Strandboge]

Marking the ufw task as Invalid. The kernel doesn't have what is needed
to run iptables.

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

** Changed in: ufw (Ubuntu)
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

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

Title:
  disco: unable to enable ufw under -virtual kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ufw package in Ubuntu:
  Invalid

Bug description:
  Fresh install of disco:

  $ sudo ufw enable
  Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
  ERROR: problem running ufw-init
  iptables-restore v1.6.1: Can't set policy `DROP' on `INPUT' line 3: Bad 
built-in chain name

  iptables-restore: line 22 failed
  iptables-restore: line 2 failed
  iptables-restore v1.6.1: Couldn't load target `ufw-logging-deny':No such file 
or directory

  Error occurred at line: 30
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-skip-to-policy-input':No 
such file or directory

  Error occurred at line: 19
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.
  iptables-restore v1.6.1: Couldn't load target `ufw-user-input':No such file 
or directory

  Error occurred at line: 2
  Try `iptables-restore -h' or 'iptables-restore --help' for more information.

  Problem running '/etc/ufw/before.rules'
  Problem running '/etc/ufw/after.rules'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ufw 0.36-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  Date: Tue Apr  9 08:49:59 2019
  Ec2AMI: ami-04cf
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.blue
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.ufw: 2019-04-09T08:48:31.371301

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

[Heitor Alves de Siqueira]

** Patch added: "lp1821343-bionic.debdiff"
   
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254687/+files/lp1821343-bionic.debdiff

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed
Status in openldap package in Debian:
  New

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
     Memory: 712.6M
     CGroup: /system.slice/slapd.service
     └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  6) Check if systemd has loaded both
  /run/systemd/generator.late/slapd.service &
  /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf

  $ systemctl cat slapd

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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

[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

[Heitor Alves de Siqueira]

** Patch added: "lp1821343-cosmic.debdiff"
   
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254686/+files/lp1821343-cosmic.debdiff

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Cosmic:
  Confirmed
Status in openldap package in Debian:
  New

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
     Memory: 712.6M
     CGroup: /system.slice/slapd.service
     └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  6) Check if systemd has loaded both
  /run/systemd/generator.late/slapd.service &
  /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf

  $ systemctl cat slapd

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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