[Touch-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick

[Kai-Heng Feng]

Does it work out of the box under Wayland session?

Seems like we need some manual config for Xorg:
https://wiki.gentoo.org/wiki/Sony_DualShock#Xorg

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

Title:
  Dualshock3 hid_sony accelerometer not registering as joystick

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

Bug description:
  [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25
  [12649.015925] input: Sony PLAYSTATION(R)3 Controller as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24
  [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 
Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90

  4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  
  perhaps this is only a config issue as when the new split gyro & analog 
sticks/buttons/triggers 
  both appeared as  joysticks while you can now see only Sony PLAYSTATION(R)3 
Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 
Controller Motion Sensors (input25) does not.

  Any questions I am happy to respond, I have every reason to believe this is 
actually not a bluez issue but google gives me no returns other than general 
compatibility issues over the new hid_sony driver splitting the gyro from the 
pad.  I use this to stay current on instrument flying while working out of town 
using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator 
that fis in my laptop bag.
  thanks
  dave

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Oct 31 15:06:00 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 60:F6:77:DD:DB:90  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:624605 acl:10743 sco:0 events:125 errors:0
TX bytes:5814 acl:12 sco:0 commands:106 errors:0

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

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

[Touch-packages] [Bug 1290542] Re: pulseaudio crashed with SIGSEGV in prepare_next_write_item()

[Daniel van Vugt]

This crash doesn't seem to make the top 100 crashes in pulseaudio on
14.04 or 18.04. So that means I can't yet find it on errors.ubuntu.com
:(

MOZGIII, do you have any more information you can share? Like a link to
your crash on errors.ubuntu.com?

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

Title:
  pulseaudio crashed with SIGSEGV in prepare_next_write_item()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  crashed while watching video via hdmi display port and hdmi
  displayport audio

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   2416 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 10 21:27:32 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-03-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   main ()
  Title: pulseaudio crashed with SIGSEGV in pa_mainloop_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1823573] Re: Bluetooth headset not available as output device

[Daniel van Vugt]

To get to the grub menu and select a different installed kernel, you
need to be fast. The instant the purple screen first appears on boot,
tap Escape.

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

Title:
  Bluetooth headset not available as output device

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Connecting my Bluetooth headset (Beoplay H8) appears to be working,
  and everything looks correct in the Bluetooth settings: However, the
  headset is not listed under "Output devices" in the sound menu after
  connecting, and all sounds are channeled through the built-in
  speakers.

  Media buttons on the headset are also rendered useless, not that there
  would be much use for them without sound anyways. Still worth noting,
  as everything including media buttons worked perfectly in 18.10.

  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
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stein  2603 F pulseaudio
   /dev/snd/pcmC0D0c:   stein  2603 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stein  2603 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 23:00:38 2019
  InstallationDate: Installed on 2018-05-09 (332 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago)
  dmi.bios.date: 10/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3PCN16WW(V2.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 510S-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 510S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80V0
  dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB
  dmi.product.version: Lenovo ideapad 510S-13IKB
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries

[Daniel van Vugt]

Awesome.

I guess the only remaining question is whether you can confirm that
downgrading to gnome-bluetooth 3.32.0 reintroduces the problem?

** Package changed: bluez (Ubuntu) => gnome-bluetooth (Ubuntu)

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

Title:
  Logitech M535 mouse only pairs successfully after 4-5 tries

Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  I've had my mouse (Logitech M535) paired and working since upgrading
  to 18.04. I had to re-do the pairing after connecting to a different
  machine and now it takes 4-5 tries of pair/remove to connect the
  mouse, on every reboot / sleep cycle.

  The logs show:
  cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info

  But neither actually seem critical as this is shown upon successful
  pairing as well.

  a bluetoothctl session of a failed pairing:
  [bluetooth]# pair 34:88:5D:3E:A1:A4 
  Attempting to pair with 34:88:5D:3E:A1:A4
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
  Pairing successful
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: no

  The mouse continues in pairing mode.

  When using the gnome-control-center Bluetooth module:
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)

  Finally when it connects:
  [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
  [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 15 07:46:38 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 12-9Q33
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago)
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 5C:51:4F:1D:50:3C  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN 
RX bytes:16702 acl:290 sco:0 events:716 errors:0
TX bytes:44162 acl:142 sco:0 commands:427 errors:0

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

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

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

[Daniel van Vugt]

** Also affects: gtk+3.0 (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Released

-- 
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 1823667] Re: SRU: pcre3 ftbfs with cosmic toolchain updates

[Matthias Klose]

the package built on all archs, and all triggered autopkg tests pass.

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

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

Title:
  SRU: pcre3 ftbfs with cosmic toolchain updates

Status in pcre3 package in Ubuntu:
  In Progress
Status in pcre3 source package in Cosmic:
  Fix Committed

Bug description:
  Fix the symbols file error by backporting the disco upload, marking
  more symbols as optional.

  Test case: the package builds, in current 18.10, and with the planned 
toolchain updates in ppa:ubuntu-toolchain-r/ppa.
  Regression potential: Should be the same as for every no-change rebuild.

  https://launchpadlibrarian.net/418304485/buildlog_ubuntu-cosmic-
  amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz

  dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
  dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
  --- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
  +++ dpkg-gensymbolsc5z0KV 2019-04-08 00:54:17.137602850 +
  @@ -80,9 +80,9 @@
    (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
    (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
    (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
  -#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  +#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
    (c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
  -#MISSING: 2:8.39-9# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  +#MISSING: 2:8.39-11# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
    (c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
    (c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
  - (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  +#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:116: binary-arch] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
  

  Build finished at 20190408-0054

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

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

[Touch-packages] [Bug 1823382] Re: backport openssl 1.1.1 fixes to bionic and cosmic

[Dimitri John Ledkov]

Spot checking both bionic and cosmic, these builds look good.

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

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

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

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

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

[Dimitri John Ledkov]

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

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

Title:
  desktop logout delays due to missing PropertiesChanged signal

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Disco:
  Fix Committed

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 1290542] Re: pulseaudio crashed with SIGSEGV in prepare_next_write_item()

[MOZGIII]

I just got the same issue at Ubuntu 18.04

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

Title:
  pulseaudio crashed with SIGSEGV in prepare_next_write_item()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  crashed while watching video via hdmi display port and hdmi
  displayport audio

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   2416 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 10 21:27:32 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-03-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   main ()
  Title: pulseaudio crashed with SIGSEGV in pa_mainloop_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1822370] Re: 19.04 beta openssh-client broken pipe

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:7.9p1-10

---
openssh (1:7.9p1-10) unstable; urgency=medium

  * Temporarily revert IPQoS defaults to pre-7.8 values until issues with
"iptables -m tos" and VMware have been fixed (closes: #923879, #926229;
LP: #1822370).

 -- Colin Watson   Mon, 08 Apr 2019 11:13:04 +0100

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

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Disco:
  Fix Released
Status in openssh package in Debian:
  Fix Released

Bug description:
  New versions of openssh (as in Ubuntu 19.04) are reported to trigger a
  connection issue:

 packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  In most of the cases this seems to affect VMWare based environments as
  there is a bug in their implementation in regard to the traffic
  shaping protocols.

  Until resolved by VMWare the workarounds for now are:

  Configure your client to use the old defaults permanently in
  =>  /etc/ssh/ssh_config 
  Host *
  IPQoS lowdelay throughput 
  # You might want to limit to your VMware based systems

  Or per command via:
   $ ssh IPQoS="latency throughput" user@host

  Two values as one is for interactive and one for non-interactive use
  cases.

   original report 

  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

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

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

[Jamie Strandboge]

"I can only think this is something cloud-image specific."

Can you provide the requested information in the earlier comments?

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1404762] Re: apparmor profile usr.sbin.clamd does not allow ScanOnAccess via fanotify

[Branden Pleines]

We ran into the same issue, but wanted to avoid installing apparmor-
utils.

In the /etc/apparmor.d/usr.sbin.clam profile, it is possible to set the
clamd profile to complain mode directly (we used Ansible) without having
to install apparmor-utils or use aa-complain.

Before:
/usr/sbin/clamd {

After:
/usr/sbin/clamd flags=(complain) {

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

Title:
  apparmor profile usr.sbin.clamd does not allow ScanOnAccess via
  fanotify

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I tried to enable the ScanOnAccess option in /etc/clamav.conf to get
  on-access scanning.

  Doing so, /var/log/clamav/clamav.log tells me:
  ERROR: ScanOnAccess: fanotify_init failed: Operation not permitted
  ScanOnAccess: clamd must be started by root

  Setting User to root in /etc/clamav/clamd.conf
  makes the clamav-daemon to fail with

  service clamav-daemon start
   * Starting ClamAV daemon clamd
  ERROR: initgroups() failed.

  I had to disable the apparmor.profile with a
  cd /etc/apparmor.d/disable
  ln -s ./../usr.sbin.clamd

  Then, the "ERROR: initgroups() failed." disappears.

  The apparmor itself came via apt-get packages. I did not edit it.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt-cache policy apparmor-profiles
  apparmor-profiles:
Installiert:   (keine)
Installationskandidat: 2.8.95~2430-0ubuntu5.1
Versionstabelle:
   2.8.95~2430-0ubuntu5.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   2.8.95~2430-0ubuntu5 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor-profiles (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 22 01:23:04 2014
  InstallationDate: Installed on 2014-11-29 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

marking upstream ureadahead as won't fix, since it was dropped from
Ubuntu starting in Cosmic.

** 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
+ 
+ [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
+  TERM=linux
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

** Changed in: ureadahead (Ubuntu)
   Status: Confirmed => Won't Fix

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

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

** Changed in: ureadahead (Ubuntu Bionic)
 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 Bionic:
  In Progress

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

  [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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

[Balint Reczey]

@juliank The proposed service would reopen LP: #1778219 , just for apt.
:-(

IMO command line apt should inhibit shutdown and systemd should respect
that even when running reboot as root.

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Triaged

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

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

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

[Touch-packages] [Bug 1657646] Re: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation

[bugproxy]

--- Comment From s...@us.ibm.com 2019-04-09 17:29 EDT---
Per above comment, this is a legitimate problem and needs to be worked. Not 
sure in which release it should be worked, though. But moving out of DEFERRED.

** Tags removed: targetmilestone-inin16042
** Tags added: targetmilestone-inin---

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

Title:
  Missing thin-provisioning-tools prevents VG with thin pool LV from
  being (de)activated, but not its creation

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 package in Debian:
  New

Bug description:
  Creating a thin pool LV is allowed even when thin-provisioning-tools
  is not installed. But deactivating or activating that VG fails. Since
  deactivating the VG usually only happens at reboot, the user might
  fail to notice this big problem until then.

  I think the lvconvert tool, used to combine the two "thin LVs" into a
  thin pool LV, should refuse to run if thin-provisioning-tools, or the
  needed scripts, aren't installed.

  Steps to reproduce:
  root@15-89:~# vgcreate vg /dev/vdb1
    Volume group "vg" successfully created

  root@15-89:~# vgs
    VG   #PV #LV #SN Attr   VSize  VFree
    vg 1   0   0 wz--n- 40.00g 40.00g

  root@15-89:~# lvcreate -n pool0 -l 90%VG vg
    Logical volume "pool0" created.

  root@15-89:~# lvcreate -n pool0meta -l 5%VG vg
    Logical volume "pool0meta" created.

  root@15-89:~# lvs
    LVVG   Attr   LSize  Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    pool0 vg   -wi-a- 36.00g
    pool0meta vg   -wi-a-  2.00g

  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root 100 Jun 21 14:15 ./
  drwxr-xr-x 20 root root3820 Jun 21 14:15 ../
  crw---  1 root root 10, 236 Jun 21 13:15 control
  lrwxrwxrwx  1 root root   7 Jun 21 14:14 vg-pool0 -> ../dm-0
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0meta -> ../dm-1

  root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0
    WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data 
and metadata volumes.
    THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
  Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y
    Converted vg/pool0 to thin pool.

  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root 120 Jun 21 14:15 ./
  drwxr-xr-x 20 root root3840 Jun 21 14:15 ../
  crw---  1 root root 10, 236 Jun 21 13:15 control
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0 -> ../dm-2
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1
  lrwxrwxrwx  1 root root   7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0
  root@15-89:~# lvs -a
    LV  VG   Attr   LSize  Pool Origin Data%  Meta%  Move Log 
Cpy%S
  ync Convert
    [lvol0_pmspare] vg   ewi---  2.00g
    pool0   vg   twi-a-tz-- 36.00g 0.00   0.01
    [pool0_tdata]   vg   Twi-ao 36.00g
    [pool0_tmeta]   vg   ewi-ao  2.00g

  If you now reboot the system, all that is gone:
  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root  60 Jun 21 14:28 ./
  drwxr-xr-x 19 root root3760 Jun 21 14:28 ../
  crw---  1 root root 10, 236 Jun 21 14:28 control

  The same happens if you deactivate the VG (which the reboot
  undoubtedly triggers). It fails because of a missing
  /usr/sbin/thin_check which is provided by the thin-provisioning-tools
  package:

  root@15-89:~# vgchange -a n
    /usr/sbin/thin_check: execvp failed: No such file or directory
    WARNING: Integrity check of metadata for pool vg/pool0 failed.
    0 logical volume(s) in volume group "vg" now active

  root@15-89:~# ll /dev/mapper/
  total 0
  drwxr-xr-x  2 root root  60 Jun 21 14:29 ./
  drwxr-xr-x 19 root root3760 Jun 21 14:29 ../
  crw---  1 root root 10, 236 Jun 21 14:28 control

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

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

[Touch-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

[Balint Reczey]

Verified 1.1ubuntu1.18.04.7~16.04.2 on Xenial, now without acpdid:

ubuntu@ip-172-31-3-29:~$ sudo service apt-daily-upgrade start & sleep 1; tail 
-f /var/log/unattended-upgrades/unattended-upgrades.log
[1] 1607
2019-04-09 20:58:27,975 INFO Initial blacklisted packages: 
2019-04-09 20:58:27,975 INFO Initial whitelisted packages: 
2019-04-09 20:58:27,975 INFO Starting unattended upgrades script
2019-04-09 20:58:27,975 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial
2019-04-09 20:58:31,986 INFO Packages that will be upgraded: busybox-initramfs 
busybox-static file libmagic1 libpam-systemd libpolkit-agent-1-0 
libpolkit-backend-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 linux-aws 
linux-headers-aws linux-image-aws ntfs-3g policykit-1 snapd systemd 
systemd-sysv ubuntu-core-launcher udev wget
2019-04-09 20:58:31,987 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2019-04-09 20:58:49,942 WARNING SIGTERM received, will stop
2019-04-09 20:58:52,944 WARNING SIGTERM received, will stop
2019-04-09 20:58:53,159 WARNING SIGNAL received, stopping

ubuntu@ip-172-31-3-29:~$ cat 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log .
Log started: 2019-04-09  20:58:35
(Reading database ... 76460 files and directories currently installed.)
Preparing to unpack .../libpolkit-gobject-1-0_0.105-14.1ubuntu0.5_amd64.deb ...
Unpacking libpolkit-gobject-1-0:amd64 (0.105-14.1ubuntu0.5) over 
(0.105-14.1ubuntu0.4) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Setting up libpolkit-gobject-1-0:amd64 (0.105-14.1ubuntu0.5) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Log ended: 2019-04-09  20:58:37
...
ubuntu@ip-172-31-3-29:~$ dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all  automatic 
installation of security upgrades
ubuntu@ip-172-31-3-29:~$ yes no | sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-aws-headers-4.4.0-1079 linux-headers-4.4.0-1079-aws 
linux-image-4.4.0-1079-aws
  linux-modules-4.4.0-1079-aws
The following packages will be upgraded:
  apt apt-transport-https apt-utils cloud-init distro-info-data file 
grub-common grub-legacy-ec2 grub-pc
  grub-pc-bin grub2-common libapt-inst2.0 libapt-pkg5.0 liblxc1 libmagic1 
libpam-systemd libsystemd0 libudev1
  linux-aws linux-headers-aws linux-image-aws login lxc-common ntfs-3g passwd 
policykit-1 python-apt-common
  python3-apt rsyslog snapd systemd systemd-sysv ubuntu-core-launcher udev 
uidmap
35 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/54.7 MB of archives.
After this operation, 118 MB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.
ubuntu@ip-172-31-3-29:~$ dpkg -l acpid
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
rc  acpid  1:2.0.26-1ubuntu amd64Advanced 
Configuration and Power Interface event d
ubuntu@ip-172-31-3-29:~$ journalctl -a
...
Apr 09 20:58:49 ip-172-31-3-29 kernel: PM: Hibernation mode set to 'platform'
Apr 09 20:58:53 ip-172-31-3-29 systemd[1]: Started Daily apt upgrade and clean 
activities.
Apr 09 20:58:53 ip-172-31-3-29 sudo[1607]: pam_unix(sudo:session): session 
closed for user root
Apr 09 20:58:55 ip-172-31-3-29 systemd-sleep[8427]: Suspending system...
Apr 09 20:59:46 ip-172-31-3-29 kernel: PM: Syncing filesystems ... done.
Apr 09 20:59:46 ip-172-31-3-29 kernel: Freezing user space processes ... 
(elapsed 0.000 seconds) done.
...

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

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

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status 

[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces

[Joi Owen]

I followed up with my coworker who originally built our two misbehaving
boxes.  He also ended up having to reboot the second box I left for him,
to get the br01 bridge configuration back in working order.  Simply
running 'netplan apply' and restarting the systemd network service did
not resolve it, but a full reboot did.  We are using the default 18.04
netplan setup, we haven't reversed back to ifupdown like the other
reporter.

Both hosts lost their networking immediately after the systemd update
was applied this morning, which installed version 237-3ubuntu10.19.  I
can delve through them to find any logs or config files you want.  These
are Supermicro rack mounts with dual 10G interfaces, built as headless
servers, so no ubuntu-desktop or X11 is installed on them.

We have sssd installed on these with the required pam customizations to
configure sssd to live in our Active Directory environment.  pam-auth-
updated printed about local mods to common-* so it wasn't updating.
Those are the only unusual outputs from this mornings unattended-
upgrades-dpkg.log file.

I can attach any logs or other files you care to view.

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

Title:
  After unattended-upgrade of systemd IP configuration removed from
  interfaces

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Info:
  Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 
2018).
  HP DL380 server

  I had this issue already twice in the past couple of months. After unattended 
upgrade of systemd my server's public IP address is removed from the interface.
  I statically configure the IP address using the interfaces file. I have opted 
out of the YML based network configuration. This is my apt history log:

  Start-Date: 2019-04-09  06:15:01
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:07

  Start-Date: 2019-04-09  06:15:12
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:56

  Start-Date: 2019-04-09  06:15:59
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 
237-3ubuntu10.19)
  End-Date: 2019-04-09  06:16:15

  
  After that my server was unavailable from the Internet. When I logged in via 
out of band management and simply brought down and up the interface everything 
went back to normal. As said above this is the second time I had this issue. 
Last time it was unattended upgrades and it was systemd again.

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

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

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

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted neon27 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neon27/0.30.2-3~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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.

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

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

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

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

[Touch-packages] [Bug 1823382] Re: backport openssl 1.1.1 fixes to bionic and cosmic

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted neon27 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neon27/0.30.2-3~ubuntu18.10.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: neon27 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

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

** Changed in: neon27 (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 neon27 in Ubuntu.
https://bugs.launchpad.net/bugs/1823382

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

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

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

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

[James Page]

I can only think this is something cloud-image specific.

FTR the policy is initially configured wide open (as the server may be
doing a number of other things the charm deploying does not know about)
and then the ports for swift/rsync are restricted to peers.

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1579580] Re: ureadahead reports relative path errors in journalctl output

[Josep Pujadas-Jubany]

Work-around #3 solved the problem for me. Thanks!

https://askubuntu.com/a/840567 explains very well the question.

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

Bug 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 1812760] Re: networkd: [Route] PreferredSource not working in *.network files

[Dan Streetman]

changing upstream github bug watch to manual, as the import of github
issue status seems broken

** Changed in: systemd
   Importance: Unknown => Undecided

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

** Changed in: systemd
 Remote watch: github.com/systemd/systemd/issues #5882 => None

** Changed in: systemd
   Status: New => 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/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 1812760] Re: networkd: [Route] PreferredSource not working in *.network files

[Dan Streetman]

cosmic (using systemd-networkd config from description test case):

ubuntu@lp1812760-c:~$ dpkg -l |grep 'ii  systemd '
ii  systemd 239-7ubuntu10.12amd64   
 system and service manager
ubuntu@lp1812760-c:~$ ip -6 r
::1 dev lo proto kernel metric 256 pref medium
fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium
fe80::/64 dev ens3 proto kernel metric 256 pref medium


ubuntu@lp1812760-c:~$ dpkg -l |grep 'ii  systemd '
ii  systemd 239-7ubuntu10.13amd64   
 system and service manager
ubuntu@lp1812760-c:~$ ip -6 r
::1 dev lo proto kernel metric 256 pref medium
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


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

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

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

[Dan Streetman]

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

** Tags removed: sts-sponsor sts-sponsor-ddstreet

-- 
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 1579580] Re: ureadahead reports relative path errors in journalctl output

[Josep Pujadas-Jubany]

18.04 LTS 64 bit Server up-to-date

Having the same problem when rebooting ...

uname -a

Linux 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   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:
  Confirmed

Bug 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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces

[Domonkos Tomcsanyi]

I have followed the instructions in the /etc/network/interfaces file to
ditch netplan and use ifupdown:

# To re-enable ifupdown on this system, you can run:
#sudo apt install ifupdown

As an extra measure I have removed netplan packages completely:

~# grep netplan .bash_history
apt remove nplan netplan.io

I have opened the bug against systemd, because I think it is the one 
responsible for the issue, but I could be wrong. It could be the 
unattended-upgrades package with the combination of systemd as well, or 
something different. I have written down the way my network configuration works 
so that enough information of my system is available - especially in this case 
where networking itself seems to have a hiccup.
Weirdly enough my virtual bridge (configured via the same 
/etc/network/interfaces file) supporting my VMs running on the server has not 
lost its IP configuration. This + Joi's experience indicate to me that this is 
not an issue of how the network configuration is applied on the server, it is 
an issue of something on a lower level possibly, and the loss of network 
connection is just an inconvenient result, and not the issue itself.

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

Title:
  After unattended-upgrade of systemd IP configuration removed from
  interfaces

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Info:
  Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 
2018).
  HP DL380 server

  I had this issue already twice in the past couple of months. After unattended 
upgrade of systemd my server's public IP address is removed from the interface.
  I statically configure the IP address using the interfaces file. I have opted 
out of the YML based network configuration. This is my apt history log:

  Start-Date: 2019-04-09  06:15:01
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:07

  Start-Date: 2019-04-09  06:15:12
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:56

  Start-Date: 2019-04-09  06:15:59
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 
237-3ubuntu10.19)
  End-Date: 2019-04-09  06:16:15

  
  After that my server was unavailable from the Internet. When I logged in via 
out of band management and simply brought down and up the interface everything 
went back to normal. As said above this is the second time I had this issue. 
Last time it was unattended upgrades and it was systemd again.

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

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

[Touch-packages] [Bug 1816642] Re: SRU of LXC 2.0.11

[Brian Murray]

Hello Stéphane, or anyone else affected,

Accepted golang-gopkg-lxc-go-lxc.v2 into xenial-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/golang-gopkg-lxc-go-
lxc.v2/0.0~git20161126.1.82a07a6-0ubuntu1~ubuntu16.04.2 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.

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  SRU of LXC 2.0.11

Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty:
  Triaged
Status in lxc source package in Trusty:
  Triaged
Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial:
  Fix Committed
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
  This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the 
changelog for both of them can be found below:

  LXC 2.0.11:
   - autotools: handle getgrgid_r on bionic
   - autotools: add memory_utils.h to Makefile.am
   - change version to 2.0.11 in configure.ac

  LXC 2.0.10:
   - tools: allow lxc-attach to undefined containers
   - utils: move memfd_create() definition
   - utils: add lxc_cloexec()
   - utils: add lxc_make_tmpfile()
   - utils: add lxc_getpagesize()
   - utils: add lxc_safe_long_long()
   - utils: parse_byte_size_string()
   - utils: add lxc_find_next_power2()
   - namespace: use lxc_getpagesize()
   - lxc-debian: allow creating `testing` and `unstable`
   - Call lxc_config_define_load from lxc_execute again
   - Fix typo in lxc-net script
   - Add missing lxc_container_put
   - lxc-debian: don't write C.* locales to /etc/locale.gen
   - attach: correctly handle namespace inheritance
   - cgfsng: fix cgroup2 detection
   - cgroups: enable container without CAP_SYS_ADMIN
   - lxc-start: remove unnecessary checks
   - start: close non-needed file descriptors
   - handler: make name argument const
   - start: close data socket in parent
   - monitor: do not log useless warnings
   - network: reap child in all cases
   - conf: reap child in all cases
   - storage: switch to ext4 as default filesystem
   - tools: fix help output of lxc-create
   - attach: handle namespace inheritance
   - cgroups/cgfsng: keep mountpoint intact
   - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown()
   - cgroups/cgfsng: support MS_READONLY with cgroup ns
   - log: check for i/o error with vsnprintf()
   - cgroupfs/cgfsng: tweak logging
   - cgroups/cgfsng: remove is_lxcfs()
   - cgroups/cgfsng: fix get_controllers() for cgroup2
   - cgroupfs/cgfsng: improve cgroup2 handling
   - config: remove SIGRTMIN+14 as lxc.signal.stop
   - commands: non-functional changes
   - console: non-functional changes
   - console: non-functional changes
   - lxc-test-unpriv: fix the overlayfs mount error
   - attach: allow attach with empty conf
   - tools/lxc_attach: removed api logging
   - console: fix console info message
   - Add missing dependency libunistring
   - cgroups/cgfsng: adapt to new cgroup2 delegation
   - console: report detach message on demand
   - lxccontainer: enable daemonized app containers
   - console: use correct escape sequence check
   - console: prepare for generic signal handler
   - console: exit mainloop on SIGTERM
   - commands: non-functional changes
   - lxccontainer: non-functional changes
   - commands: fix state socket implementation
   - lxc_init: set the control terminal in the child session
   - lxc-test-unpriv: check user existence before removing it
   - Fixed typo on lxc.spec.in
   - conf: move CAP_SYS_* definitions to utils.h
   - start.c: always switch uid and gid
   - Use AX_PTHREAD config script to detect pthread api
   - utils.h: Avoid 

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

[Brian Murray]

Hello Stéphane, or anyone else affected,

Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.11-0ubuntu1~16.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-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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1816642

Title:
  SRU of LXC 2.0.11

Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty:
  Triaged
Status in lxc source package in Trusty:
  Triaged
Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial:
  Fix Committed
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
  This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the 
changelog for both of them can be found below:

  LXC 2.0.11:
   - autotools: handle getgrgid_r on bionic
   - autotools: add memory_utils.h to Makefile.am
   - change version to 2.0.11 in configure.ac

  LXC 2.0.10:
   - tools: allow lxc-attach to undefined containers
   - utils: move memfd_create() definition
   - utils: add lxc_cloexec()
   - utils: add lxc_make_tmpfile()
   - utils: add lxc_getpagesize()
   - utils: add lxc_safe_long_long()
   - utils: parse_byte_size_string()
   - utils: add lxc_find_next_power2()
   - namespace: use lxc_getpagesize()
   - lxc-debian: allow creating `testing` and `unstable`
   - Call lxc_config_define_load from lxc_execute again
   - Fix typo in lxc-net script
   - Add missing lxc_container_put
   - lxc-debian: don't write C.* locales to /etc/locale.gen
   - attach: correctly handle namespace inheritance
   - cgfsng: fix cgroup2 detection
   - cgroups: enable container without CAP_SYS_ADMIN
   - lxc-start: remove unnecessary checks
   - start: close non-needed file descriptors
   - handler: make name argument const
   - start: close data socket in parent
   - monitor: do not log useless warnings
   - network: reap child in all cases
   - conf: reap child in all cases
   - storage: switch to ext4 as default filesystem
   - tools: fix help output of lxc-create
   - attach: handle namespace inheritance
   - cgroups/cgfsng: keep mountpoint intact
   - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown()
   - cgroups/cgfsng: support MS_READONLY with cgroup ns
   - log: check for i/o error with vsnprintf()
   - cgroupfs/cgfsng: tweak logging
   - cgroups/cgfsng: remove is_lxcfs()
   - cgroups/cgfsng: fix get_controllers() for cgroup2
   - cgroupfs/cgfsng: improve cgroup2 handling
   - config: remove SIGRTMIN+14 as lxc.signal.stop
   - commands: non-functional changes
   - console: non-functional changes
   - console: non-functional changes
   - lxc-test-unpriv: fix the overlayfs mount error
   - attach: allow attach with empty conf
   - tools/lxc_attach: removed api logging
   - console: fix console info message
   - Add missing dependency libunistring
   - cgroups/cgfsng: adapt to new cgroup2 delegation
   - console: report detach message on demand
   - lxccontainer: enable daemonized app containers
   - console: use correct escape sequence check
   - console: prepare for generic signal handler
   - console: exit mainloop on SIGTERM
   - commands: non-functional changes
   - lxccontainer: non-functional changes
   - commands: fix state socket implementation
   - lxc_init: set the control terminal in the child session
   - lxc-test-unpriv: check user existence before removing it
   - Fixed typo on lxc.spec.in
   - conf: move CAP_SYS_* definitions to utils.h
   - start.c: always switch uid and gid
   - Use AX_PTHREAD config script to detect pthread api
   - utils.h: Avoid duplicated sethostname implementation
   - tools/lxc_cgroup: remove internal logging
   - tools/lxc_autostart: remove internal logging
   - tools/lxc_clone: remove internal logging
   

[Touch-packages] [Bug 1824002] Re: python3-launchpadlib needs promotion from suggests

[Brian Murray]

Here is a comment indicating why things got switched around:

https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1192330/comments/3

For quite some time there was not a python3-launchpadlib and we didn't
want to keep holding python2 in the archive because of apport. However,
once python3-launchpadlib became available it was never moved back to a
Depend.

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

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

** Tags added: rls-ee-incoming

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

Title:
  python3-launchpadlib needs promotion from suggests

Status in apport package in Ubuntu:
  Triaged

Bug description:
  If one wants to apport-collect, one gets an error about
  python3-launchpadlib needing to be installed. One can easily install
  it, but it really should be a Recommend, if not a Depend so one
  doesn't have to go through this trouble. Right now, it's a Suggest. It
  seems that during the whole Python2/3 transition some things got
  switched around, but it had been a Depend for a long time before that.

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

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

[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces

[Dan Streetman]

> I statically configure the IP address using the interfaces file.

you mention the interfaces file, but this bug is against systemd - what
mechanism are you using to configure your network?  For a fresh install
of 18.04, you will get netplan by default, using systemd-networkd as its
backend; is that what you're using, or something else?

> I have opted out of the YML based network configuration.

you mean you replaced netplan with something else?  ifupdown?


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

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

Title:
  After unattended-upgrade of systemd IP configuration removed from
  interfaces

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Info:
  Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 
2018).
  HP DL380 server

  I had this issue already twice in the past couple of months. After unattended 
upgrade of systemd my server's public IP address is removed from the interface.
  I statically configure the IP address using the interfaces file. I have opted 
out of the YML based network configuration. This is my apt history log:

  Start-Date: 2019-04-09  06:15:01
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:07

  Start-Date: 2019-04-09  06:15:12
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:56

  Start-Date: 2019-04-09  06:15:59
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 
237-3ubuntu10.19)
  End-Date: 2019-04-09  06:16:15

  
  After that my server was unavailable from the Internet. When I logged in via 
out of band management and simply brought down and up the interface everything 
went back to normal. As said above this is the second time I had this issue. 
Last time it was unattended upgrades and it was systemd again.

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

-- 
Mailing list: https://launchpad.net/~touch-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 1823125] Re: tomcat9 fails to install in 18.04

[Steve Langasek]

This change is included in tomcat9 9.0.16-3~18.04.1 which is published
to bionic-proposed.  Changelog:

tomcat9 (9.0.16-3~18.04.1) bionic; urgency=medium

  * Don't set nologin shell in sysusers.d/tomcat9.conf
It is the default anyway and systemd-sysusers in 18.04 can't parse it.
(LP: #1823125)

Since this was a proposed-only issue, I am marking this resolved for
bionic.

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

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

Title:
  tomcat9 fails to install in 18.04

Status in systemd package in Ubuntu:
  Fix Released
Status in tomcat9 package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in tomcat9 source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in tomcat9 source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in tomcat9 source package in Disco:
  Fix Released

Bug description:
  # apt install tomcat9
  ...
  Setting up tomcat9 (9.0.16-3~18.04) ...
  [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

  Creating config file /etc/tomcat9/tomcat-users.xml with new version
  chown: invalid group: ‘root:tomcat’
  dpkg: error processing package tomcat9 (--configure):
   installed tomcat9 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.15) ...
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.
  Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
  Errors were encountered while processing:
   tomcat9
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1272380] Re: Missing whitespace between generated man page refentrys

[Roger Light]

This is no longer an issue in recent Ubuntu releases.

** Changed in: libxslt (Ubuntu)
   Status: New => Fix Released

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

Title:
  Missing whitespace between generated man page refentrys

Status in libxslt package in Ubuntu:
  Fix Released

Bug description:
  I am generating man pages from docbook xml using xsltproc and
  /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl

  My man page contains entries like this for the "See Also" section:

 
  mosquitto
  8
  
  
  mosquitto-conf
  5
  

  When I process the man pages using xsltproc from Saucy, the resulting
  code looks like:

  \fBmosquitto\fR(8)\fBmosquitto-conf\fR(5)

  When viewed in man, this looks like "mosquitto(8)mosquitto-conf(5)" -
  with no space between the two entries.

  On Precise, the output from the same man page is:

  \fBmosquitto\fR(8)
  \fBmosquitto-conf\fR(5)

  and when viewed in man this looks like "mosquitto(8) mosquitto-
  conf(5)" as expected.

  The xml man pages and Makefile to generate the troff output can be
  found in http://mosquitto.org/files/source/mosquitto-1.2.3.tar.gz in
  the man directory.

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

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

[Touch-packages] [Bug 1822966] Re: apport-bug locks up when selecting "Cancel"

[Roger Light]

Just to confirm, because Brian had a slightly different version number,
this still exists on 2.20.10-0ubuntu26.

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

Title:
  apport-bug locks up when selecting "Cancel"

Status in apport package in Ubuntu:
  New

Bug description:
  To reproduce:

  * Run "apport-bug" from the command line
  * Select "Other problem" from the "What kind of problem do you want to 
report?", then click OK.
  * The "What display problem do you observe?" dialogue pops up, I realise that 
doesn't match anything that I want to report and click Cancel.
  * Apport becomes completely unresponsive.

  Traceback after Ctrl-C suggests that there is a problem with a thread
  lock:

  Exception ignored in: 
  Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
  t.join()
File "/usr/lib/python3.7/threading.py", line 1032, in join
  self._wait_for_tstate_lock()
File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
  elif lock.acquire(block, timeout):
  KeyboardInterrupt

  This is on Kubuntu 19.04, apport 2.20.10-0ubuntu23

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

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

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.28.2-0ubuntu0.18.04.3

---
gnome-control-center (1:3.28.2-0ubuntu0.18.04.3) bionic; urgency=medium

  * debian/patches/power-Label-the-PENDING_CHARGING-state-as-Not-Charging.patch:
- Label the PENDING_CHARGING state as "Not Charging" (LP: #1745032)

 -- Marco Trevisan (Treviño)   Fri, 25 Jan 2019
19:04:00 +

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in upower source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Launchpad Bug Tracker]

This bug was fixed in the package upower - 0.99.7-2ubuntu0.18.04.1

---
upower (0.99.7-2ubuntu0.18.04.1) bionic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * debian/control: update mantainer to ubuntu
  * debian/gbp.conf: update branch to ubuntu/bionic
  * d/p/daemon-Consider-pending-charge-when-calculating-the-displ.patch:
- Detect AC state on pending state (LP: #1745032)

  [ Iain Lane ]
  * debian/control: Update Vcs-* for Launchpad
  * gbp.conf: Set debian-tag to create ubuntu/xxx tags

 -- Iain Lane   Fri, 25 Jan 2019 16:38:41 +

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

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in upower source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml

[Laurent Bonnaud]

I cannot reproduce the bug in Ubuntu 19.04.  Thanks for the fix!

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

Title:
  Unknown media types in /usr/share/mime/packages/kde.xml

Status in kdelibs:
  Won't Fix
Status in shared-mime-info:
  Won't Fix
Status in kde4libs package in Ubuntu:
  Confirmed
Status in shared-mime-info package in Ubuntu:
  Triaged
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  Here is the problem:

  # update-mime-database /usr/share/mime
  [...]
  Unknown media type in type 'uri/mms'

  Unknown media type in type 'uri/mmst'

  Unknown media type in type 'uri/mmsu'

  Unknown media type in type 'uri/pnm'

  Unknown media type in type 'uri/rtspt'

  Unknown media type in type 'uri/rtspu'

  It seems to come from this file:
/usr/share/mime/packages/kde.xml

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

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

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")

[Derk Willem te Bokkel]

okay apr 8 and apr 9 iso's have same issues kept logs of various boots
into the fresh installs .. no change in grub-source during testing was
made .. all with fresh installs

typical first boot is normal ..  no crash of xorg on first start ..
second boot shows lightdm briefly then xorg crashes while trying to use FBDEV 
last item before crash loads libfb.so then backtrace happens and crash ..

.. then xorg restarts with a working driver

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries

[Michał Sawicz]

Hey @vanvugt, just upgraded to 19.04 and indeed the problems seem to
have gone. The mouse pairs every time, and persistently.

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

Title:
  Logitech M535 mouse only pairs successfully after 4-5 tries

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I've had my mouse (Logitech M535) paired and working since upgrading
  to 18.04. I had to re-do the pairing after connecting to a different
  machine and now it takes 4-5 tries of pair/remove to connect the
  mouse, on every reboot / sleep cycle.

  The logs show:
  cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info

  But neither actually seem critical as this is shown upon successful
  pairing as well.

  a bluetoothctl session of a failed pairing:
  [bluetooth]# pair 34:88:5D:3E:A1:A4 
  Attempting to pair with 34:88:5D:3E:A1:A4
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
  Pairing successful
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: no

  The mouse continues in pairing mode.

  When using the gnome-control-center Bluetooth module:
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)

  Finally when it connects:
  [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
  [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 15 07:46:38 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 12-9Q33
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago)
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 5C:51:4F:1D:50:3C  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN 
RX bytes:16702 acl:290 sco:0 events:716 errors:0
TX bytes:44162 acl:142 sco:0 commands:427 errors:0

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

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

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

[Seth Arnold]

On Tue, Apr 09, 2019 at 03:15:26PM -, Lars wrote:
> 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:

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

Hello Lars, this is indicating that the dhcpd service is trying to use
root's capability to bypass permissions to use this file. I suggest
checking the owner, group, and permissions of all directories and the
lease file. (namei -l /test/var/lib/dhcp/dhcpd.leases can be handy
for this.)

If all those owners and permissions are as you intended and you want the
dhcpd service to use root powers to access the file, then you'll also need
to modify the profile to allow the dhcpd daemon to use the dac_override:

  capability dac_override,

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 1823862] Re: disco: unable to enable ufw

[Jamie Strandboge]

Another thing that might be useful is attaching a tarball of /lib/ufw,
/etc/ufw, and /etc/default/ufw.

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

[Julian Andres Klode]

Something like that Python script should be enough really to catch most
issues:

import apt_pkg, os

apt_pkg.init()

dir = apt_pkg.config.find_dir("Dir::Cache::Archives")
while True:
  try:
apt_pkg.get_lock(os.path.join(dir, "lock"))
break
  except:
continue

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Triaged

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

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

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

[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Sami Pietila]

I further tested this new 4.18.0-18-generic kernel and with this kernel
the wifi seems to work very good. I did not observe any slowness as I
did with the patched 4.18.0-16 kernel.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   

[Touch-packages] [Bug 1816642] Re: SRU of LXC 2.0.11

[Stéphane Graber]

Adding go-lxc to this as the fixes in 2.0.11 ended up showing bugs in
go-lxc's test logic, so we'll have to cherry-pick a couple of fixes from
upstream to have it be happy and give us a meaningful test result.

** Also affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu)
   Status: New => Fix Released

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Trusty)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

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

Title:
  SRU of LXC 2.0.11

Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty:
  Triaged
Status in lxc source package in Trusty:
  Triaged
Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial:
  In Progress
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
  This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the 
changelog for both of them can be found below:

  LXC 2.0.11:
   - autotools: handle getgrgid_r on bionic
   - autotools: add memory_utils.h to Makefile.am
   - change version to 2.0.11 in configure.ac

  LXC 2.0.10:
   - tools: allow lxc-attach to undefined containers
   - utils: move memfd_create() definition
   - utils: add lxc_cloexec()
   - utils: add lxc_make_tmpfile()
   - utils: add lxc_getpagesize()
   - utils: add lxc_safe_long_long()
   - utils: parse_byte_size_string()
   - utils: add lxc_find_next_power2()
   - namespace: use lxc_getpagesize()
   - lxc-debian: allow creating `testing` and `unstable`
   - Call lxc_config_define_load from lxc_execute again
   - Fix typo in lxc-net script
   - Add missing lxc_container_put
   - lxc-debian: don't write C.* locales to /etc/locale.gen
   - attach: correctly handle namespace inheritance
   - cgfsng: fix cgroup2 detection
   - cgroups: enable container without CAP_SYS_ADMIN
   - lxc-start: remove unnecessary checks
   - start: close non-needed file descriptors
   - handler: make name argument const
   - start: close data socket in parent
   - monitor: do not log useless warnings
   - network: reap child in all cases
   - conf: reap child in all cases
   - storage: switch to ext4 as default filesystem
   - tools: fix help output of lxc-create
   - attach: handle namespace inheritance
   - cgroups/cgfsng: keep mountpoint intact
   - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown()
   - cgroups/cgfsng: support MS_READONLY with cgroup ns
   - log: check for i/o error with vsnprintf()
   - cgroupfs/cgfsng: tweak logging
   - cgroups/cgfsng: remove is_lxcfs()
   - cgroups/cgfsng: fix get_controllers() for cgroup2
   - cgroupfs/cgfsng: improve cgroup2 handling
   - config: remove SIGRTMIN+14 as lxc.signal.stop
   - commands: non-functional changes
   - console: non-functional changes
   - console: non-functional changes
   - lxc-test-unpriv: fix the overlayfs mount error
   - attach: allow attach with empty conf
   - tools/lxc_attach: removed api logging
   - console: fix console info message
   - Add missing dependency libunistring
   - cgroups/cgfsng: adapt to new cgroup2 delegation
   - console: report detach message on demand
   - lxccontainer: enable daemonized app containers
   - console: use correct escape sequence check
   - console: prepare for generic signal handler
   - console: exit mainloop on SIGTERM
   - commands: non-functional changes
   - lxccontainer: non-functional changes
   - commands: fix state socket implementation
   - lxc_init: set the control terminal in the child session
   - lxc-test-unpriv: check user existence before removing it
   - Fixed typo on lxc.spec.in
   - conf: move CAP_SYS_* definitions to utils.h
   - start.c: always switch uid and gid
   - Use AX_PTHREAD config script to detect pthread api
   - utils.h: Avoid duplicated sethostname implementation
   - tools/lxc_cgroup: remove internal logging
   - tools/lxc_autostart: remove internal logging
   - tools/lxc_clone: remove internal logging
   - tools/lxc_console: remove internal logging
   - tools/lxc_create: remove internal logging
   - tools/lxc_destroy: remove internal logging
   - tools/lxc_device: remove internal logging
   - tools/lxc_execute: removed internal logging
   - tools/lxc_freeze: remove internal logging
   - tools/lxc_info: removed internal logging
   - criu: detect veth name
   - lxccontainer: various container creation 

[Touch-packages] [Bug 1824002] [NEW] python3-launchpadlib needs promotion from suggests

[Walter Lapchynski]

Public bug reported:

If one wants to apport-collect, one gets an error about
python3-launchpadlib needing to be installed. One can easily install it,
but it really should be a Recommend, if not a Depend so one doesn't have
to go through this trouble. Right now, it's a Suggest. It seems that
during the whole Python2/3 transition some things got switched around,
but it had been a Depend for a long time before that.

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

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

Title:
  python3-launchpadlib needs promotion from suggests

Status in apport package in Ubuntu:
  New

Bug description:
  If one wants to apport-collect, one gets an error about
  python3-launchpadlib needing to be installed. One can easily install
  it, but it really should be a Recommend, if not a Depend so one
  doesn't have to go through this trouble. Right now, it's a Suggest. It
  seems that during the whole Python2/3 transition some things got
  switched around, but it had been a Depend for a long time before that.

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

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

[Touch-packages] [Bug 1816642] Re: SRU of LXC 2.0.11

[Stéphane Graber]

For go-lxc, the goal is to get a clean autopkgtest result on all arches,
manual testing of the package did show that we should be getting that
now.

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

Title:
  SRU of LXC 2.0.11

Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty:
  Triaged
Status in lxc source package in Trusty:
  Triaged
Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial:
  In Progress
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
  This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the 
changelog for both of them can be found below:

  LXC 2.0.11:
   - autotools: handle getgrgid_r on bionic
   - autotools: add memory_utils.h to Makefile.am
   - change version to 2.0.11 in configure.ac

  LXC 2.0.10:
   - tools: allow lxc-attach to undefined containers
   - utils: move memfd_create() definition
   - utils: add lxc_cloexec()
   - utils: add lxc_make_tmpfile()
   - utils: add lxc_getpagesize()
   - utils: add lxc_safe_long_long()
   - utils: parse_byte_size_string()
   - utils: add lxc_find_next_power2()
   - namespace: use lxc_getpagesize()
   - lxc-debian: allow creating `testing` and `unstable`
   - Call lxc_config_define_load from lxc_execute again
   - Fix typo in lxc-net script
   - Add missing lxc_container_put
   - lxc-debian: don't write C.* locales to /etc/locale.gen
   - attach: correctly handle namespace inheritance
   - cgfsng: fix cgroup2 detection
   - cgroups: enable container without CAP_SYS_ADMIN
   - lxc-start: remove unnecessary checks
   - start: close non-needed file descriptors
   - handler: make name argument const
   - start: close data socket in parent
   - monitor: do not log useless warnings
   - network: reap child in all cases
   - conf: reap child in all cases
   - storage: switch to ext4 as default filesystem
   - tools: fix help output of lxc-create
   - attach: handle namespace inheritance
   - cgroups/cgfsng: keep mountpoint intact
   - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown()
   - cgroups/cgfsng: support MS_READONLY with cgroup ns
   - log: check for i/o error with vsnprintf()
   - cgroupfs/cgfsng: tweak logging
   - cgroups/cgfsng: remove is_lxcfs()
   - cgroups/cgfsng: fix get_controllers() for cgroup2
   - cgroupfs/cgfsng: improve cgroup2 handling
   - config: remove SIGRTMIN+14 as lxc.signal.stop
   - commands: non-functional changes
   - console: non-functional changes
   - console: non-functional changes
   - lxc-test-unpriv: fix the overlayfs mount error
   - attach: allow attach with empty conf
   - tools/lxc_attach: removed api logging
   - console: fix console info message
   - Add missing dependency libunistring
   - cgroups/cgfsng: adapt to new cgroup2 delegation
   - console: report detach message on demand
   - lxccontainer: enable daemonized app containers
   - console: use correct escape sequence check
   - console: prepare for generic signal handler
   - console: exit mainloop on SIGTERM
   - commands: non-functional changes
   - lxccontainer: non-functional changes
   - commands: fix state socket implementation
   - lxc_init: set the control terminal in the child session
   - lxc-test-unpriv: check user existence before removing it
   - Fixed typo on lxc.spec.in
   - conf: move CAP_SYS_* definitions to utils.h
   - start.c: always switch uid and gid
   - Use AX_PTHREAD config script to detect pthread api
   - utils.h: Avoid duplicated sethostname implementation
   - tools/lxc_cgroup: remove internal logging
   - tools/lxc_autostart: remove internal logging
   - tools/lxc_clone: remove internal logging
   - tools/lxc_console: remove internal logging
   - tools/lxc_create: remove internal logging
   - tools/lxc_destroy: remove internal logging
   - tools/lxc_device: remove internal logging
   - tools/lxc_execute: removed internal logging
   - tools/lxc_freeze: remove internal logging
   - tools/lxc_info: removed internal logging
   - criu: detect veth name
   - lxccontainer: various container creation fixes
   - storage: remove unused declaration
   - tools/lxc_ls: remove internal logging
   - tools/lxc_copy: remove internal logging
   - tools/lxc_monitor: removed internal logging
   - tools/lxc_snapshot: removed internal logging
   - tools/lxc_start: removed internal logging
   - tools/lxc_stop: removed internal logging
   - tools/lxc_top: removed internal logging
   - tools/lxc_unfreeze: removed internal logging
   - tools/lxc_unshare: removed internal logging
   - tools/lxc_usernsexec: removed internal logging
   - tools/lxc_wait: removed internal logging
   - confile: fix memory leak
   - utils: declare sethostname() static inline
   - lxc_unshare: 

[Touch-packages] [Bug 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress

[Julian Andres Klode]

Suggested workaround:

* Create a script that tries to lock the apt locks, until it succeeds, then 
exits
* Make that run in ExecStart in a service WantedBy=shutdown.target

Probably some issues regarding to services and stuff, but better than
nothing.

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

Title:
  Potential inconsistency due to system halt/reboot being allowed when
  package installation in progress

Status in apt package in Ubuntu:
  Triaged

Bug description:
  [System]
  Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, 
Cosmic).

  [Impact]
  Package installation turns into an inconsistent state if system is rebooted 
in the middle of an apt install/upgrade.

  [Test Case]
  1. User1 at Ubuntu box issues "sudo apt-get upgrade";
  2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI;
  3. System reboots and potentially turns into an inconsistent state.

  [Remarks]
  APT should automatically inhibit system halts/reboots while packages being 
installed/removed. A similar behavior to what is shown by unattended-upgrades.

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

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

[Jamie Strandboge]

FYI, I also tried the above with setting /etc/default/ufw to have
IPV6=no and everything works fine (and the v6 rules are not added).

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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

[Jamie Strandboge]

You said that the swift charm is disabling ipv6 in certain situations.
Is it updating /etc/default/ufw? Is it disabling it elsewhere? In the
failing instance, before trying to setup swift or run ufw or anything,
what is the output of 'sudo /usr/share/ufw/check-requirements'?

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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

[Jamie Strandboge]

The usefulness of the policy aside (it is configured wide open), I still
can't reproduce with http://cdimage.ubuntu.com/ubuntu-
server/daily/current/disco-server-amd64.iso that I just downloaded:

$ sudo ufw default allow incoming
Default incoming policy changed to 'allow'
(be sure to update your rules accordingly)
$ sudo ufw default allow outgoing
Default outgoing policy changed to 'allow'
(be sure to update your rules accordingly)
$ sudo ufw default allow routed
Default routed policy changed to 'allow'
(be sure to update your rules accordingly)
$ sudo ufw allow rsync
Rules updated
Rules updated (v6)
$ sudo ufw allow ssh
Rules updated
Rules updated (v6)
$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup

$ cat /proc/version_signature 
Ubuntu 5.0.0-8.9-generic 5.0.1

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1816642] Please test proposed package

[Brian Murray]

Hello Stéphane, or anyone else affected,

Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.11-0ubuntu1~16.04.2 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1816642

Title:
  SRU of LXC 2.0.11

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
  This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the 
changelog for both of them can be found below:

  LXC 2.0.11:
   - autotools: handle getgrgid_r on bionic
   - autotools: add memory_utils.h to Makefile.am
   - change version to 2.0.11 in configure.ac

  LXC 2.0.10:
   - tools: allow lxc-attach to undefined containers
   - utils: move memfd_create() definition
   - utils: add lxc_cloexec()
   - utils: add lxc_make_tmpfile()
   - utils: add lxc_getpagesize()
   - utils: add lxc_safe_long_long()
   - utils: parse_byte_size_string()
   - utils: add lxc_find_next_power2()
   - namespace: use lxc_getpagesize()
   - lxc-debian: allow creating `testing` and `unstable`
   - Call lxc_config_define_load from lxc_execute again
   - Fix typo in lxc-net script
   - Add missing lxc_container_put
   - lxc-debian: don't write C.* locales to /etc/locale.gen
   - attach: correctly handle namespace inheritance
   - cgfsng: fix cgroup2 detection
   - cgroups: enable container without CAP_SYS_ADMIN
   - lxc-start: remove unnecessary checks
   - start: close non-needed file descriptors
   - handler: make name argument const
   - start: close data socket in parent
   - monitor: do not log useless warnings
   - network: reap child in all cases
   - conf: reap child in all cases
   - storage: switch to ext4 as default filesystem
   - tools: fix help output of lxc-create
   - attach: handle namespace inheritance
   - cgroups/cgfsng: keep mountpoint intact
   - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown()
   - cgroups/cgfsng: support MS_READONLY with cgroup ns
   - log: check for i/o error with vsnprintf()
   - cgroupfs/cgfsng: tweak logging
   - cgroups/cgfsng: remove is_lxcfs()
   - cgroups/cgfsng: fix get_controllers() for cgroup2
   - cgroupfs/cgfsng: improve cgroup2 handling
   - config: remove SIGRTMIN+14 as lxc.signal.stop
   - commands: non-functional changes
   - console: non-functional changes
   - console: non-functional changes
   - lxc-test-unpriv: fix the overlayfs mount error
   - attach: allow attach with empty conf
   - tools/lxc_attach: removed api logging
   - console: fix console info message
   - Add missing dependency libunistring
   - cgroups/cgfsng: adapt to new cgroup2 delegation
   - console: report detach message on demand
   - lxccontainer: enable daemonized app containers
   - console: use correct escape sequence check
   - console: prepare for generic signal handler
   - console: exit mainloop on SIGTERM
   - commands: non-functional changes
   - lxccontainer: non-functional changes
   - commands: fix state socket implementation
   - lxc_init: set the control terminal in the child session
   - lxc-test-unpriv: check user existence before removing it
   - Fixed typo on lxc.spec.in
   - conf: move CAP_SYS_* definitions to utils.h
   - start.c: always switch uid and gid
   - Use AX_PTHREAD config script to detect pthread api
   - utils.h: Avoid duplicated sethostname implementation
   - tools/lxc_cgroup: remove internal logging
   - tools/lxc_autostart: remove internal logging
   - tools/lxc_clone: remove internal logging
   - tools/lxc_console: remove internal logging
   - tools/lxc_create: remove internal logging
   - tools/lxc_destroy: remove internal logging
   - tools/lxc_device: remove internal logging
   - tools/lxc_execute: removed 

[Touch-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

[Balint Reczey]

I need to verify this bug again because acpi was pulled in to the image.

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

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

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact (unattended-upgrades)]

   * Unattended-upgrades does not gracefully stop installing updates
  when the system goes to hibernation potentially letting the system to
  hibernate in a state where the system can't resume from.

  [Test Case (unattended-upgrades)]

   * Configure the system to have several 20+ packages upgradable by
  unattended-upgrades. One easy way of setting this up is starting with
  a system where packages from -security are installed but packages from
  -updates are not and enabling -updates in u-u:

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

  * Pre-download upgrades
# unattended-upgraded --download-only

  * Trigger unattended-upgrades run:
#  service apt-daily-upgrade start

  * Hibernate, then resume the system and watch unattended-upgrades
  being gracefully stopped, checking /var/log/unattended-upgrades
  /unattended-upgrades.log. There should be packages left to be
  upgraded.

  [Regression Potential (unattended-upgrades)]

   * The added hook for unattended-upgrades may block the system from
  hibernation for 25 minutes if unattended-upgrades (or most likely a
  package upgrades) hangs. There is a better solution proposed based on
  systemd's inhibitor interface at https://github.com/mvo5/unattended-
  upgrades/issues/162 .

  [Original Bug Text]

  I added a new script in /etc/pm/sleep.d/ that worked fine before the
  upgrade to vivid. I was wondering why it doesn't work and I find out
  that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
  logs from pm-suspend were on Apr 28, when I upgraded from utopic to
  vivid.

  The laptop suspends and wakes fine, it just seems that no pm scripts
  are run after suspend/powersave.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 15:36:26 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-12 (792 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[James Page]

this translates into:

ufw default allow incoming
ufw default allow outgoing
ufw default allow routed

ufw allow rsync
ufw allow ssh

ufw enable

which gets us to the:

ufw.enable(soft_fail=config('allow-ufw-ip6-softfail'))

which is where the failure to enable occurs.

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1823435] Re: session-migration ftbfs in disco

[Launchpad Bug Tracker]

This bug was fixed in the package session-migration - 0.3.4

---
session-migration (0.3.4) disco; urgency=medium

  * Fix failing tests due to keyfiles get from stdlib not keeping tuple
order. (LP: #1823435)

 -- Didier Roche   Tue, 09 Apr 2019 15:38:19 +0200

** Changed in: session-migration (Ubuntu Disco)
   Status: New => Fix Released

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

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  Fix Released
Status in session-migration source package in Disco:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
  AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
  - 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;

  
  --
  Ran 9 tests in 8.615s

  FAILED (failures=2)
  make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
  make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[2]: *** [Makefile:167: check] Error 2
  make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
  make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2

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

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

[James Page]

OK so there is a little modification of the policy prior to enablement:

def initialize_ufw():
"""Initialize the UFW firewall

Ensure critical ports have explicit allows

:return: None
"""

if not config('enable-firewall'):
log("Firewall has been administratively disabled", "DEBUG")
return

# this charm will monitor exclusively the ports used, using 'allow' as
# default policy enables sharing the machine with other services
ufw.default_policy('allow', 'incoming')
ufw.default_policy('allow', 'outgoing')
ufw.default_policy('allow', 'routed')
# Rsync manages its own ACLs
ufw.service('rsync', 'open')
# Guarantee SSH access
ufw.service('ssh', 'open')
# Enable
ufw.enable(soft_fail=config('allow-ufw-ip6-softfail'))

# Allow GRE traffic
add_ufw_gre_rule(os.path.join(UFW_DIR, 'before.rules'))
ufw.reload()

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[Balint Reczey]

@jarnos But thank you for your attention to details.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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

[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Sami Pietila]

** 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1818204

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  

[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

[Balint Reczey]

@jarnos Most likely i forgot running /etc/kernel/postinst.d/apt-auto-removal 
and -53- was still protected.
I don't have this system anymore, and I think the verification is convincing 
enough to not repeat it for this bug.

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

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

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

[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

[Balint Reczey]

@jarnos(#20) The running kernel's related packages are protected by u-u. There 
are the packages protected by apt, which are also not offered for autoremoval, 
hence u-u would not remove them either.
When the kernel package for -39- is protected by apt in 
/etc/apt/apt.conf.d/01autoremove-kernels u-u does not remove it either.

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

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Triaged
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  When running kernel version 4.4.0-78 (for example) and the unattended-upgrade 
packages installs a new kernel 4.4.0-79 (for example) the 
linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are 
removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel 
packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  [Test case (apt)]

  Make sure that linux-cloud-tools for protected kernels are listed in
  APT::NeverAutoRemove, for example, on cosmic:

     "^linux-cloud-tools-4\.17\.0-9-generic$";
     "^linux-cloud-tools-4\.18\.0-7-generic$";

  Those are in 01autoremove-kernels

  [Test case (unattended-upgrades)]

   * Check the running kernel and install relevant cloud-tools packages:
  # uname -a
  Linux x-uu-lp-1737637 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  root@x-uu-lp-1737637:~# apt-cache search 4.15.0-39-generic
  linux-cloud-tools-4.15.0-39-generic - Linux kernel version specific cloud 
tools for version 4.15.0-39
  linux-headers-4.15.0-39-generic - Linux kernel headers for version 4.15.0 on 
64 bit x86 SMP
  linux-image-4.15.0-39-generic - Signed kernel image generic
  linux-image-unsigned-4.15.0-39-generic - Linux kernel image for version 
4.15.0 on 64 bit x86 SMP
  linux-modules-4.15.0-39-generic - Linux kernel extra modules for version 
4.15.0 on 64 bit x86 SMP
  linux-modules-extra-4.15.0-39-generic - Linux kernel extra modules for 
version 4.15.0 on 64 bit x86 SMP
  # apt install linux-cloud-tools-4.15.0-39-generic
  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:
linux-cloud-tools-common linux-hwe-cloud-tools-4.15.0-39
  The following NEW packages will be installed:
linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common 
linux-hwe-cloud-tools-4.15.0-39
  0 upgraded, 3 newly installed, 0 to remove and 17 not upgraded.
  Need to get 119 kB of archives.
  After this operation, 854 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  ...

   * Mark them autoremovable and configure u-u to autoremove unused
  packages:

  # apt-mark auto linux-cloud-tools-4.15.0-39-generic
  linux-cloud-tools-4.15.0-39-generic set to automatically installed.
  ### set Unattended-Upgrade::Remove-Unused-Dependencies "true";
  # vi /etc/apt/apt.conf.d/50unattended-upgrades

   * The not fixed version of u-u removes the packages:

  # unattended-upgrade --dry-run --verbose
  ...
  All upgrades installed
  Packages that are auto removed: 'libfreetype6 
linux-cloud-tools-4.15.0-39-generic linux-cloud-tools-common 
linux-hwe-cloud-tools-4.15.0-39'
  Packages were successfully auto-removed
  # 

   * The fixed version does not:
   # unattended-upgrade --dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
  Removing unused kernel packages: linux-cloud-tools-common
  Keeping auto-removable linux-cloud-tools-common package(s) because it would 
also remove the following packages which should be kept in this step: 
linux-cloud-tools-4.15.0-39-generic linux-hwe-cloud-tools-4.15.0-39
  ...

  [Regression Potential]

   * some linux-cloud-tools will linger around, so it takes more 

[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw

[James Page]

I'm trying to figure out what is modifying /etc/default/ufw - the swift-
storage charm does but it just disables IPv6 in some situations.

I reported this from a different cloud instance - so probably worth
mentioning that this is a disco image running on openstack from the
daily image stream.

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Sami Pietila]

Now dist-upgrade found that kernel. I can confirm, with this kernel
rfkill reports the device unblocked.

ID TYPE  DEVICE SOFT  HARD
 0 wlan  ideapad_wlan  unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 3 wlan  phy0  unblocked unblocked
 4 bluetooth hci0  unblocked unblocked

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ 

[Touch-packages] [Bug 1823862] Re: disco: unable to enable ufw

[Jamie Strandboge]

I cannot reproduce. I notice that you said 'default install' but at a
minimum you have modified /etc/default/ufw to have:

DEFAULT_INPUT_POLICY="ACCEPT"

$ cat /proc/version_signature 
Ubuntu 5.0.0-8.9-generic 5.0.1

$ sudo ufw enable
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Started bpfilter
Firewall is active and enabled on system startup

Can you give exact steps to verify?

What is the output of 'sudo /usr/share/ufw/check-requirements'? What is
the output of that before you run 'ufw enable'?

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

** Changed in: ufw (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Status in ufw package in Ubuntu:
  Incomplete

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/ufw/+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 1455097] Re: /etc/pm/sleep.d/ is no more processed

[Balint Reczey]

Verified 1.1ubuntu1.18.04.7~16.04.2 on Xenial:

ubuntu@ip-172-31-9-2:~$ dpkg -l  unattended-upgrades  | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all  automatic 
installation of security upgrades


ubuntu@ip-172-31-9-2:~$ sudo service apt-daily-upgrade start &  tail -f 
/var/log/unattended-upgrades/unattended-upgrades.log
[2] 13368
2019-04-09 16:11:45,975 INFO Initial blacklisted packages: 
2019-04-09 16:11:45,975 INFO Initial whitelisted packages: 
2019-04-09 16:11:45,976 INFO Starting unattended upgrades script
2019-04-09 16:11:45,976 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-09 16:13:06,974 INFO Initial blacklisted packages: 
2019-04-09 16:13:06,974 INFO Initial whitelisted packages: 
2019-04-09 16:13:06,974 INFO Starting unattended upgrades script
2019-04-09 16:13:06,974 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-09 16:13:11,782 INFO Packages that will be upgraded: apt 
apt-transport-https apt-utils busybox-initramfs busybox-static cloud-init 
distro-info-data file grub-common grub-legacy-ec2 grub-pc grub-pc-bin 
grub2-common libapt-inst2.0 libapt-pkg5.0 libmagic1 libpam-systemd 
libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libsystemd0 
libudev1 linux-aws linux-headers-aws linux-image-aws ntfs-3g policykit-1 
rsyslog snapd systemd systemd-sysv ubuntu-core-launcher udev wget
2019-04-09 16:13:11,782 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2019-04-09 16:13:17,835 WARNING SIGTERM received, will stop
2019-04-09 16:13:18,514 WARNING SIGNAL received, stopping

... connection lost.

After resume:
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-aws-headers-4.4.0-1079 linux-headers-4.4.0-1079-aws 
linux-image-4.4.0-1079-aws linux-modules-4.4.0-1079-aws
The following packages will be upgraded:
  apt apt-transport-https apt-utils busybox-initramfs busybox-static cloud-init 
file grub-common grub-legacy-ec2 grub-pc grub-pc-bin grub2-common libapt-inst2.0
  libapt-pkg5.0 liblxc1 libmagic1 libpam-systemd libpolkit-agent-1-0 
libpolkit-backend-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 linux-aws 
linux-headers-aws
  linux-image-aws login lxc-common ntfs-3g passwd policykit-1 python-apt-common 
python3-apt rsyslog snapd systemd systemd-sysv ubuntu-core-launcher udev uidmap 
wget
40 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.9 MB/56.1 MB of archives.
After this operation, 118 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
ubuntu@ip-172-31-9-2:~$ journalctl -a
Apr 09 16:13:17 ip-172-31-9-2 systemd[1]: Reached target Sleep.
Apr 09 16:13:17 ip-172-31-9-2 systemd[1]: Starting Hibernate...
Apr 09 16:13:17 ip-172-31-9-2 kernel: PM: Hibernation mode set to 'platform'
Apr 09 16:13:19 ip-172-31-9-2 sudo[13368]: pam_unix(sudo:session): session 
closed for user root
Apr 09 16:13:19 ip-172-31-9-2 systemd[1]: Started Daily apt upgrade and clean 
activities.
Apr 09 16:13:19 ip-172-31-9-2 systemd-sleep[13502]: Suspending system...
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Syncing filesystems ... done.
Apr 09 16:15:58 ip-172-31-9-2 kernel: Freezing user space processes ... 
(elapsed 0.001 seconds) done.
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Marking nosave pages: [mem 
0x-0x0fff]
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Marking nosave pages: [mem 
0x0009e000-0x000f]
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Basic memory bitmaps created
...

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

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

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

[Balint Reczey]

All the referenced bugs are verified now. Please note that some of them
did not need SRU template, those are listed in this bug.

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

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

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.

  [Test Case]

  * Since this backport involves fixing several bugs and this bug itself
  covers the full backport this is an overview of all LP bugs the upload
  fixes:

  - most important bugs (feel free to add more)
     + LP: #1615381 : apt-get autoremove may remove current kernel

  All LP bugs fixed by the backport, comments are welcome:
     + LP: #1230246 could use SRU template but seems straightforward
     + LP: #1260041 SRU template ok
     + LP: #1396787 SRU template ok
     + LP: #1446552 SRU template ok
     + LP: #1455097 SRU template ok
     + LP: #1458204 could use SRU template but seems straightforward
     + LP: #1577215 could use SRU template but seems straightforward
     + LP: #1602536 SRU template ok
     + LP: #1615381 could use SRU template but seems straightforward
     + LP: #1624644 SRU template ok
     + LP: #1649709 not affecting xenial
     + LP: #1654070 could use SRU template but seems straightforward
     + LP: #1654600 SRU template ok
     + LP: #1675079 SRU template ok
     + LP: #1680599 could use SRU template but seems straightforward
     + LP: #1686470 SRU template ok
     + LP: #1690980 SRU template ok
     + LP: #1698159 SRU template ok
     + LP: #1702793 this bug
     + LP: #1714019 just a merge request
     + LP: #1718419 just a merge request
     + LP: #1719630 SRU template ok
     + LP: #1722426 just a merge request
     + LP: #1737442 SRU template ok
     + LP: #1737635 SRU template ok
     + LP: #1737637 SRU template ok
     + LP: #1737717 SRU template ok
     + LP: #1741579 SRU template ok
     + LP: #1764797 just a merge request
     + LP: #1773033 SRU template ok
     + LP: #1775292 SRU template ok
     + LP: #1775307 SRU template ok
     + LP: #1778219 SRU template ok
     + LP: #1778800 SRU template ok
     + LP: #1779157 SRU template ok
     + LP: #1781176 SRU template ok
     + LP: #1781183 SRU template ok
     + LP: #1781446 SRU template ok
     + LP: #1781586 SRU template ok
     + LP: #1785093 SRU template ok
     + LP: #1789637 SRU template ok
     + LP: #1803749 SRU template ok

  [Regression Potential]

  * Due to this update covering the full backport unattended-upgrades
  can regress in any imaginable way including failing to install,
  upgrade, run, or removing essential packages from the system. Those
  are unlikely.* There are open bugs about u-u being slower than in the
  past, thus this may be a likely regression but IMO the pending speed
  optimizations should not be blocking the backport because the
  reliability issues are more important to fix and speed optimizations
  can be cherry-picked later.

  [Other Info]

  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html

  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.

  [Original Bug Text]

  Changes to support day-of-week patching and logging to syslog were
  added to upstream (https://github.com/mvo5/unattended-upgrades) over a
  year ago. These changes are not present in the latest Xenial nor
  Trusty packages (0.90 and 0.82.1) - requesting that these changes be
  pulled from upstream.

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

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

[Touch-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick

[dave]

Got this back from the Sony dev Roderick Colenbrander,

"Unfortunately reverting the joydev patch is not an option. Let me
explain why. Joydev is an old legacy for using joysticks. It is very
limited and can only deal with buttons and sticks. It doesn't support
new features like force feedback / rumble (though already added 15+
years ago), multitouch, motion sensors and other features.

When we started offering motion sensors, this broke existing
applications which were never designed with motion sensor support.
Applications which would never get updated. Nor does joydev have a way
to distinguish motion sensor axes from regular joystick axes.

The recommended way for over a decade is to not use joydev, but use
evdev, which is also what is used for keyboard, mouse and other devices.
It offers all the features needed and it is supported fine for ds3 and
ds4."

I am playing with a hack that cam be found here:
https://askubuntu.com/questions/1088925/ubuntu-18-04-no-longer-adds-second-joystick-device-for-sony-dualshock3s-gyro-ac
which I have not gotten to fully work creating a joydev as I write this but I 
do now see both evdevs.  Unfortunately joydev is still pretty standard for 
things like Flightgear.

https://askubuntu.com/questions/1088925/ubuntu-18-04-no-longer-adds-
second-joystick-device-for-sony-dualshock3s-gyro-ac

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

Title:
  Dualshock3 hid_sony accelerometer not registering as joystick

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

Bug description:
  [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25
  [12649.015925] input: Sony PLAYSTATION(R)3 Controller as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24
  [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 
Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90

  4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  
  perhaps this is only a config issue as when the new split gyro & analog 
sticks/buttons/triggers 
  both appeared as  joysticks while you can now see only Sony PLAYSTATION(R)3 
Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 
Controller Motion Sensors (input25) does not.

  Any questions I am happy to respond, I have every reason to believe this is 
actually not a bluez issue but google gives me no returns other than general 
compatibility issues over the new hid_sony driver splitting the gyro from the 
pad.  I use this to stay current on instrument flying while working out of town 
using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator 
that fis in my laptop bag.
  thanks
  dave

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Oct 31 15:06:00 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 60:F6:77:DD:DB:90  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:624605 acl:10743 sco:0 events:125 errors:0
TX bytes:5814 acl:12 sco:0 commands:106 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1800839/+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 1823573] Re: Bluetooth headset not available as output device

[Potet]

I can't seem to figure out how to boot to an older kernel on this
laptop. Shift and Escape does noting, while the menus opened by
F-buttons fail to give advanced boot settings. It's all within the UEFI
safety net (which I kind of appreciate after years of BIOS trouble).

I know I have old kernel versions installed (if dpkg --list | grep
linux-image is anything to go by).

If it's any help, pavucontrol also fails to detect the headset, while
"bluetoothctl" returns "Agent registered // [Beoplay H8]#". So given
that pavucontrol is completely separate from Gnome control center, this
should not be a GUI problem?

I'm sorry for not being more helpful!

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

Title:
  Bluetooth headset not available as output device

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Connecting my Bluetooth headset (Beoplay H8) appears to be working,
  and everything looks correct in the Bluetooth settings: However, the
  headset is not listed under "Output devices" in the sound menu after
  connecting, and all sounds are channeled through the built-in
  speakers.

  Media buttons on the headset are also rendered useless, not that there
  would be much use for them without sound anyways. Still worth noting,
  as everything including media buttons worked perfectly in 18.10.

  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
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stein  2603 F pulseaudio
   /dev/snd/pcmC0D0c:   stein  2603 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stein  2603 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 23:00:38 2019
  InstallationDate: Installed on 2018-05-09 (332 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago)
  dmi.bios.date: 10/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3PCN16WW(V2.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 510S-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 510S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80V0
  dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB
  dmi.product.version: Lenovo ideapad 510S-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

[Lars]

Public bug reported:

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

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Balint Reczey]

Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial:

root@x-uu-lp-1690980:~# tail -f 
/var/log/unattended-upgrades/unattended-upgrades.log 
2019-04-09 13:08:24,515 INFO Initial blacklisted packages: 
2019-04-09 13:08:24,516 INFO Initial whitelisted packages: 
2019-04-09 13:08:24,516 INFO Starting unattended upgrades script
2019-04-09 13:08:24,516 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 
'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial', 
'o=Ubuntu,a=xenial-updates']
2019-04-09 15:01:44,987 INFO Initial blacklisted packages: 
2019-04-09 15:01:44,988 INFO Initial whitelisted packages: 
2019-04-09 15:01:44,988 INFO Starting unattended upgrades script
2019-04-09 15:01:44,988 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-09 15:02:06,773 INFO Packages that will be upgraded: adwaita-icon-theme 
dirmngr fontconfig fontconfig-config gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 
glib-networking glib-networking-common glib-networking-services gnupg-agent 
gnupg2 gstreamer1.0-plugins-base gstreamer1.0-plugins-good 
gstreamer1.0-pulseaudio gstreamer1.0-x hicolor-icon-theme humanity-icon-theme 
hwdata libarchive13 libavahi-client3 libavahi-common-data libavahi-common3 
libboost-filesystem1.58.0 libboost-iostreams1.58.0 libboost-system1.58.0 
libcaca0 libcups2 libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 
libegl1-mesa libepoxy0 libexempi3 libfontconfig1 libgbm1 libgd3 
libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx 
libglapi-mesa libgraphite2-3 libgstreamer-plugins-base1.0-0 
libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin 
libgtk-3-common libharfbuzz0b libinput10 libjpeg-turbo8 libksba8 liblcms2-2 
libllvm3.8 libmirclient9 libmirprotobuf3 libnautilus-extension1a libnspr4 
libnss3 libnss3-nssdb libpam-systemd libpulse0 libsane libsane-common 
libsndfile1 libsoup-gnome2.4-1 libsoup2.4-1 libsystemd0 libtiff5 
libtracker-sparql-1.0-0 libudev1 libvorbis0a libvorbisenc2 libwacom-bin 
libwacom-common libwacom2 libwavpack1 libwayland-client0 libwayland-cursor0 
libwayland-egl1-mesa libwayland-server0 libx11-xcb1 libxcursor1 libxkbcommon0 
libxpm4 systemd systemd-sysv ubuntu-mono udev wget x11-common
2019-04-09 15:02:06,774 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
^C
root@x-uu-lp-1690980:~# dbus-send --system --print-reply 
--dest=org.freedesktop.login1 /org/freedesktop/login1 
"org.freedesktop.login1.Manager.Reboot" boolean:false
method return time=1554822131.758122 sender=:1.1 -> destination=:1.7 serial=33 
reply_serial=2
root@x-uu-lp-1690980:~# 
root@x-uu-lp-1690980:~# tail -f 
/var/log/unattended-upgrades/unattended-upgrades.log 
2019-04-09 13:08:24,516 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 
'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial', 
'o=Ubuntu,a=xenial-updates']
2019-04-09 15:01:44,987 INFO Initial blacklisted packages: 
2019-04-09 15:01:44,988 INFO Initial whitelisted packages: 
2019-04-09 15:01:44,988 INFO Starting unattended upgrades script
2019-04-09 15:01:44,988 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-09 15:02:06,773 INFO Packages that will be upgraded: adwaita-icon-theme 
dirmngr fontconfig fontconfig-config gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 
glib-networking glib-networking-common glib-networking-services gnupg-agent 
gnupg2 gstreamer1.0-plugins-base gstreamer1.0-plugins-good 
gstreamer1.0-pulseaudio gstreamer1.0-x hicolor-icon-theme humanity-icon-theme 
hwdata libarchive13 libavahi-client3 libavahi-common-data libavahi-common3 
libboost-filesystem1.58.0 libboost-iostreams1.58.0 libboost-system1.58.0 
libcaca0 libcups2 libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 
libegl1-mesa libepoxy0 libexempi3 libfontconfig1 libgbm1 libgd3 
libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx 
libglapi-mesa libgraphite2-3 libgstreamer-plugins-base1.0-0 
libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin 
libgtk-3-common libharfbuzz0b libinput10 libjpeg-turbo8 libksba8 liblcms2-2 
libllvm3.8 libmirclient9 libmirprotobuf3 libnautilus-extension1a libnspr4 
libnss3 libnss3-nssdb libpam-systemd libpulse0 libsane libsane-common 
libsndfile1 libsoup-gnome2.4-1 libsoup2.4-1 libsystemd0 libtiff5 
libtracker-sparql-1.0-0 libudev1 libvorbis0a libvorbisenc2 libwacom-bin 
libwacom-common libwacom2 libwavpack1 libwayland-client0 libwayland-cursor0 
libwayland-egl1-mesa libwayland-server0 libx11-xcb1 libxcursor1 libxkbcommon0 
libxpm4 systemd systemd-sysv ubuntu-mono udev wget x11-common
2019-04-09 15:02:06,774 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2019-04-09 15:02:11,761 WARNING SIGTERM received, will stop
2019-04-09 15:02:14,904 WARNING SIGTERM received, will stop
2019-04-09 15:02:17,763 WARNING SIGTERM received, will stop
2019-04-09 

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Till Kamppeter]

Here is an updated debdiff for gtk+3.0 in Ubuntu Disco. It is based on
the current gtk_3.0 package of Disco with the patch of

https://gitlab.gnome.org/GNOME/gtk/merge_requests/717

applied, this patch exactly:

https://gitlab.gnome.org/GNOME/gtk/commit/8b85f38093ac7b22d7d34f634faf69dd607e942c.patch

Please sponsor the upload before Final Freeze this Thursday. Thanks.

** Patch added: "gtk+3.0_3.24.7-1ubuntu1_3.24.7-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+attachment/525/+files/gtk+3.0_3.24.7-1ubuntu1_3.24.7-1ubuntu2.debdiff

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in gtk+3.0 source package in Bionic:
  In Progress
Status in gtk+3.0 source package in Cosmic:
  In Progress

Bug description:
  [Impact]

  The problem occurs when the printer's driver package is updated and
  with this the PPD is replaced and one of the default settings of the
  queue is not available any more in the new PPD file. Then the setting
  is prefixed with "Custom." and with this the jobs fail.

  See comment #15 for more info.

  [Test Case]

  - Create a print queue with a PPD.
  - evince an arbitrary PDF file
  - Click the print icon
  - In the print dialog choose the newly created queue and choose some uncommon 
paper size (not custom). Click "Print".
  - Check /var/log/cups/error_log, the page size gets correctly received.
  - Close evince.
  - Stop CUPS, edit the PPD file removing the paper size you have selected for 
your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines.
  - Start CUPS.
  - Open the same PDF file again with evince, click Print and then select 
"Print" in the print dialog without changing anything.
  - The job fails, in /var/log/cups/error_log you see that the page size is 
prefixed with "Custom.".

  With the fixed package installed the job will print.

  [Regression Potential]

  The change applies only to saved settings of the print dialog not
  matching with any of the settings available in the PPD file. In rare
  cases the fix could fail by mis-understanding the setting and this way
  not being effective. For options which do not support setting custom
  values (the vast majority) the patch should always prevent a job
  failure though.

  [Other Info]

  Complete info about the bug and the fix in comment #15,

  Original bug description:

  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  

[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Christian Ehrhardt ]

** Description changed:

+ [Impact]
+ 
+  * If an update has a new conffile at a path that in a former version was 
+a directory like
+ old: /a/b/c
+ new: a/b
+Here b is the new file name and was a directory in the old version.
+Then unattended upgrades breaks on installing such a package.
+ 
+  * a recent qemu update has such a case and due to that triggered the 
+issue in >=Bionic
+ 
+  * The fix is to harden unattended upgrades to be able to handle the case 
+without aborting.
+ 
+ [Test Case]
+ 
+ Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12
+ That can be done with:
+   $ time uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic
+   $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic 
label=daily
+ 
+ Log in and apt update & upgrade all packages, then Install the release level 
qemu in there.
+   $ uvt-kvm ssh bionic-testuu
+   $ sudo apt update
+   $ sudo apt dist-upgrade
+   $ sudo apt install unattended-upgrades
+   $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7
+ 
+ All before was preparation, now force the unattended upgrade to trigger the 
bug.
+   $ sudo unattended-upgrade -d
+ 
+ With the bug you'll find some error like:
+ found pkg: qemu-guest-agent
+ conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191
+ current md5: f61a64ac1e48993023018fd1cff85191
+ conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 
15f6ff42cbc5550a07ee21c2a471d905
+ /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles 
/etc/init.d/qemu-guest-agent
+ /etc/qemu/fsfreeze-hook
+ found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status
+ Traceback (most recent call last):
+   File "/usr/bin/unattended-upgrade", line 2057, in 
+ sys.exit(main(options))
+   File "/usr/bin/unattended-upgrade", line 1773, in main
+ if conffile_prompt(item.destfile):
+   File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt
+ with open(prefix + conf_file, 'rb') as fp:
+ IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'
+ 
+ [Regression Potential]
+ 
+ TODO: rbalint who writes the fix
+  * discussion of how regressions are most likely to manifest as a result of 
this change. 
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * n/a
+ 
+ ---
+ 
  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.
  
  That all worked fine and moved the conffile.
  
  It was now reported that due to some pre-checks that unattended upgrades
  might do this might do some checks on its own.
  
  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)
  
- 
  --- original report copied ---
  
  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:
  
  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
-   File "/usr/bin/unattended-upgrade", line 1998, in 
- sys.exit(main(options))
-   File "/usr/bin/unattended-upgrade", line 1714, in main
- if conffile_prompt(item.destfile):
-   File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
- with open(prefix + conf_file, 'rb') as fp:
+   File "/usr/bin/unattended-upgrade", line 1998, in 
+ sys.exit(main(options))
+   File "/usr/bin/unattended-upgrade", line 1714, in main
+ if conffile_prompt(item.destfile):
+   File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
+ with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'
  
  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...
  
  This prevents security updates to be installed. The unattended-upgrade
  logs do not contain the trace, only the messages:
  
  2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
  2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
  2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
  2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'
  
  And that's it.
  
  You can't really get out of this without manually running 'apt-get
  install qemu-guest-agent' because at this point, unattended-upgrade
  can't 

[Touch-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

[Iain Lane]

** No longer affects: upower (Ubuntu)

** No longer affects: upower (Ubuntu Bionic)

** No longer affects: upower (Ubuntu Cosmic)

** No longer affects: upower (Ubuntu Disco)

** No longer affects: gnome-shell (Ubuntu Bionic)

** No longer affects: gnome-shell (Ubuntu Cosmic)

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1823175/+subscriptions

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

** 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 vspk systemd-tmpfiles[81]: Failed to validate path 
/var/run/zabbix: Too many levels of symbol
  ic links  
   
  Mar  6 12:32:54 vspk systemd-tmpfiles[81]: fchownat() of /run/log/journal 
failed: 

[Touch-packages] [Bug 1823435] Re: session-migration ftbfs in disco

[Iain Lane]

** Also affects: session-migration (Ubuntu Disco)
   Importance: High
 Assignee: Didier Roche (didrocks)
   Status: New

** Tags removed: rls-dd-incoming

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

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  New
Status in session-migration source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
  AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
  - 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;

  
  --
  Ran 9 tests in 8.615s

  FAILED (failures=2)
  make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
  make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[2]: *** [Makefile:167: check] Error 2
  make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
  make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2

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

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

[Touch-packages] [Bug 1823432] Re: openexr ftbfs in disco (i386 only)

[Iain Lane]

** Also affects: openexr (Ubuntu Disco)
   Importance: High
 Assignee: Sebastien Bacher (seb128)
   Status: New

** Tags removed: rls-cc-incoming rls-dd-incoming
** Tags added: rls-cc-notfixing

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  New
Status in openexr source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

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

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

[Will Cooke]

** Changed in: librsvg (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

-- 
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:
  New
Status in librsvg source package in Disco:
  New

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 1823426] Re: librsvg ftbfs in disco (i386 only)

[Iain Lane]

** Also affects: librsvg (Ubuntu Disco)
   Importance: High
 Assignee: Olivier Tilloy (osomon)
   Status: New

** Tags removed: rls-dd-incoming

-- 
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:
  New
Status in librsvg source package in Disco:
  New

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 1823432] Re: openexr ftbfs in disco (i386 only)

[Will Cooke]

** Changed in: openexr (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  New
Status in openexr source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

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

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

** Tags removed: rls-bb-incoming

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

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 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick

[dave]

kaihengfeng, emailed Roderick Colenbrander the commit at Sony and we
will see.

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

Title:
  Dualshock3 hid_sony accelerometer not registering as joystick

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

Bug description:
  [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25
  [12649.015925] input: Sony PLAYSTATION(R)3 Controller as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24
  [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 
Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90

  4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  
  perhaps this is only a config issue as when the new split gyro & analog 
sticks/buttons/triggers 
  both appeared as  joysticks while you can now see only Sony PLAYSTATION(R)3 
Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 
Controller Motion Sensors (input25) does not.

  Any questions I am happy to respond, I have every reason to believe this is 
actually not a bluez issue but google gives me no returns other than general 
compatibility issues over the new hid_sony driver splitting the gyro from the 
pad.  I use this to stay current on instrument flying while working out of town 
using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator 
that fis in my laptop bag.
  thanks
  dave

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Oct 31 15:06:00 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 60:F6:77:DD:DB:90  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:624605 acl:10743 sco:0 events:125 errors:0
TX bytes:5814 acl:12 sco:0 commands:106 errors:0

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

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

[Touch-packages] [Bug 1823435] Re: session-migration ftbfs in disco

[Launchpad Bug Tracker]

** Branch linked: lp:session-migration

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

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
  AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
  - 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;

  
  --
  Ran 9 tests in 8.615s

  FAILED (failures=2)
  make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
  make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[2]: *** [Makefile:167: check] Error 2
  make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
  make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2

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

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

[Eric Desrochers]

Sponsored in disco.

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

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  In Progress
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 1785629] Re: [MIR] gupnp-av

[Didier Roche]

Let's turn those as incomplete to get off the list until we get over
them again (probably next cycle).

** Changed in: gupnp-av (Ubuntu)
   Status: New => Incomplete

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

Title:
  [MIR] gupnp-av

Status in gupnp-av package in Ubuntu:
  Incomplete

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

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

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

debdiff v2 with fixed author information

** Patch added: "v2-lp1821343-disco.debdiff"
   
https://bugs.launchpad.net/debian/+source/openldap/+bug/1821343/+attachment/5254440/+files/v2-lp1821343-disco.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:
  Confirmed
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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces

[Joi Owen]

Two of our Ubuntu 18.04 hosts applied this update this morning and both
dropped offline.  They're both using netplan and have bonded interfaces.
The bond layer was offline.  I had to reboot to get the network stack
running again.  I left one host offline so the coworker who configured
them can look it over later this morning.  Two identical hosts did not
apply this systemd update this morning and they're both still online.

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

Title:
  After unattended-upgrade of systemd IP configuration removed from
  interfaces

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Info:
  Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 
2018).
  HP DL380 server

  I had this issue already twice in the past couple of months. After unattended 
upgrade of systemd my server's public IP address is removed from the interface.
  I statically configure the IP address using the interfaces file. I have opted 
out of the YML based network configuration. This is my apt history log:

  Start-Date: 2019-04-09  06:15:01
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:07

  Start-Date: 2019-04-09  06:15:12
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:56

  Start-Date: 2019-04-09  06:15:59
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 
237-3ubuntu10.19)
  End-Date: 2019-04-09  06:16:15

  
  After that my server was unavailable from the Internet. When I logged in via 
out of band management and simply brought down and up the interface everything 
went back to normal. As said above this is the second time I had this issue. 
Last time it was unattended upgrades and it was systemd again.

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

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

[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces

[Launchpad Bug Tracker]

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

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

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

Title:
  After unattended-upgrade of systemd IP configuration removed from
  interfaces

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Info:
  Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 
2018).
  HP DL380 server

  I had this issue already twice in the past couple of months. After unattended 
upgrade of systemd my server's public IP address is removed from the interface.
  I statically configure the IP address using the interfaces file. I have opted 
out of the YML based network configuration. This is my apt history log:

  Start-Date: 2019-04-09  06:15:01
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:07

  Start-Date: 2019-04-09  06:15:12
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:56

  Start-Date: 2019-04-09  06:15:59
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 
237-3ubuntu10.19)
  End-Date: 2019-04-09  06:16:15

  
  After that my server was unavailable from the Internet. When I logged in via 
out of band management and simply brought down and up the interface everything 
went back to normal. As said above this is the second time I had this issue. 
Last time it was unattended upgrades and it was systemd again.

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

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

[Touch-packages] [Bug 1742714] Re: MIR: mesa-vulkan-drivers FFE: install by default

[Didier Roche]

** Changed in: mesa (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/1742714

Title:
  MIR: mesa-vulkan-drivers FFE: install by default

Status in mesa package in Ubuntu:
  Invalid
Status in vulkan-loader package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  MIR mesa-vulkan-drivers:
  - is from mesa, which is already in main
  - maintained just as mesa is, by ubuntu-x-swat

  MIR vulkan-loader:
  https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711

  FFE:
  - new packages in the default install (mesa-vulkan-drivers, libvulkan1)
    -> no chance of regressing anything

  --

  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

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

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

[Touch-packages] [Bug 1783272] Re: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces

[Dan Streetman]

@lathiat,

the patches for bug 1812760 should fix this, can you retest with the pkg
in -proposed?

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

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

** Changed in: systemd (Ubuntu Cosmic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1783272

Title:
  upgrading systemd package restarts systemd-networkd and briefly takes
  down network interfaces

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

Bug description:
  Upgrading the systemd package, which contains systemd-networkd,
  appears to restart networkd and subsequently reconfigure network
  interfaces causing a brief connectivity outage.

  This is a bionic system which has a network bridge as it's primary
  interface through netplan.

  You can see from the logs that the interface appears to have been briefly 
taken down
  > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered 
disabled state

  We also see logs of networkd restarting
  > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service...
  > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service.
  > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service...

  Based on the ordering of the messages from Avahi, I also believe that
  the IP address was first removed, then it was taken down, brought back
  up, and the IP re-added. But I can not state that with 100% certainty.
  However if you just set an interface down manually (ip link set br0
  down), usually Avahi notes the interface is relevant before the
  address was removed.  We see the opposite here.  It's possible the
  ordering is just not entirely deterministic though.

  Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 
10.48.134.22 on br0.
  Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer 
relevant for mDNS.

  The main reason I noticed this, is that the unofficial oracle-
  java8-installer package upgraded at the same time - and it's wget to
  download java failed due to "Network is unreachable" as it was
  upgraded as the same time. To be clear, I'm not suggesting necessarily
  that this specific package was affected is the bug, but it's the
  reason I noticed the restart and it did cause an upgrade failure which
  I resumed with "dpkg --configure -a".  However there are many other
  implications of the network interface being reconfigured.

  Generally it's probably just not ideal to have networkd restart and
  reconfigure the network interfaces - no matter the possible causes.
  But from a quick thought about realistic implications

   - it seems the bridge was not deleted/re-created which would be bad
  for systems using libvirt/lxd/etc where the VMs may drop off the
  bridge. The interface index didn't change so hopefully we're safe from
  this one ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev
  exists, using existing without changing its parameters")

   - Another use case other than oracle-java8-installer that is highly
  likely to be impacted is daemons configured to bind to a specific IP
  address. By default, those binds will fail if the IP address doesn't
  exist. It's possible these two restarts will race and those services
  will fail to restart. An example where this could happen, is Apache2.
  It would probably be hard to reproduce but logically likely to occur
  in some small number of cases.

   - we potentially do want networkd to ideally restart to upgrade the
  code, but ideally it would "diff" the network interface config and not
  tear things down. I am using a 'switchport' match in my netplan
  config, I wonder if this is related?

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

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

[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

[Vital Koshalew]

@seth-arnold,

You are talking about a different type of vulnerability scanning that is
not part of the Qualys service in question (External vulnerability scan,
"black box" scan methodology). PCI DSS also mandates regular internal
scans and penetration tests. Qualys, as well as other vendors provides
such services.

As for determining package version directly vs. by version banner, I
don't see any difference *in this case* as by default full ubuntu-
specific package version is displayed in SSH version banner and Qualys
requires users not to interfere with the scanning.

The issue that @root(mysky) has stems from the fact that Qualys is
usually very fast when including a vulnerable product in their detector
but sometimes slow to exclude fixed versions as in this case. This isn't
a big deal as they have False Positive Report mechanism that allows a
live service representative to asses the situation and allow your system
to pass even if the automatic scanner detects a non-existent
vulnerability.

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  Fix Released

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

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

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

[Eric Desrochers]

** Description changed:

  [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
+    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)
+    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.

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

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

[Ioanna Alifieraki]

VERIFICATION Cosmic

- Using configuration file from description

$ dpkg -l | grep systemd
ii  systemd   239-7ubuntu10.12   
amd64system and service manager   

$ ip rule
0:  from all lookup local 
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 


-- Install systemd from -proposed

$ dpkg -l | grep systemd
ii  systemd   239-7ubuntu10.13   
amd64system and service manager

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

$ sudo systemctl restart systemd-networkd

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


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

-- 
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 1821343] Re: slapd process failure is not detected by systemd

[Heitor R. Alves de Siqueira]

@slashd I don't think we need anything special for systemd in the
debian/{control,rules} files, since we're not shipping full systemd
support with this. The slapd service is still handled by systemd-sysv-
generator(8), so there's no service units that we need to include or
activate in dh_systemd rules.

To make sure things are working fine I went ahead and tested a package
upgrade with this debdiff:

ubuntu@disco:~$ dpkg -l | grep slapd
ii  slapd   2.4.47+dfsg-3ubuntu1amd64
OpenLDAP server (slapd)

ubuntu@disco:~$ sudo apt-get --only-upgrade install slapd

ubuntu@disco:~$ dpkg -l | grep slapd
ii  slapd   2.4.47+dfsg-3ubuntu2amd64
OpenLDAP server (slapd)

ubuntu@disco:~$ systemctl cat slapd
# /run/systemd/generator.late/slapd.service
# Automatically generated by systemd-sysv-generator

[Unit]
Documentation=man:systemd-sysv-generator(8)
SourcePath=/etc/init.d/slapd
Description=LSB: OpenLDAP standalone server (Lightweight Directory Access 
Protocol)
Before=multi-user.target
Before=multi-user.target
Before=multi-user.target
Before=graphical.target
After=remote-fs.target
After=network-online.target
Wants=network-online.target

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
SuccessExitStatus=5 6
ExecStart=/etc/init.d/slapd start
ExecStop=/etc/init.d/slapd stop

# /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf
[Service]
Type=forking
RemainAfterExit=no

Thanks!

-- 
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:
  Confirmed
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)

  [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 

[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  
  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...

  This prevents security updates to be installed. The unattended-upgrade
  logs do not contain the trace, only the messages:

  2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
  2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
  2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
  2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'

  And that's it.

  You can't really get out of this without manually running 'apt-get
  install qemu-guest-agent' because at this point, unattended-upgrade
  can't update itself anymore.

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

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

[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Launchpad Bug Tracker]

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

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

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  
  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...

  This prevents security updates to be installed. The unattended-upgrade
  logs do not contain the trace, only the messages:

  2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
  2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
  2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
  2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'

  And that's it.

  You can't really get out of this without manually running 'apt-get
  install qemu-guest-agent' because at this point, unattended-upgrade
  can't update itself anymore.

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

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

[Touch-packages] [Bug 1822745] Re: /usr/bin/unattended-upgrade:IsADirectoryError:/usr/bin/unattended-upgrade@2138:main:run:conffile_prompt

[Balint Reczey]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Incomplete

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => In Progress

** This bug has been marked a duplicate of bug 1823872
   Fixing fsfreeze-hook can break unattended upgrades

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

Title:
  /usr/bin/unattended-upgrade:IsADirectoryError:/usr/bin/unattended-
  upgrade@2138:main:run:conffile_prompt

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.5ubuntu3.18.10.3, the problem page at 
https://errors.ubuntu.com/problem/7551745f47e60a92582dfa16b5ae7f1c0383d5f7 
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/unattended-upgrades/+bug/1822745/+subscriptions

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

[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Balint Reczey]

I already found this in the dup-ed bug and will fix it in u-u.
The fix is almost done, I'm adding a few extra tests.

I made this the master bug because it has nicer description, thanks! :-)

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  
  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...

  This prevents security updates to be installed. The unattended-upgrade
  logs do not contain the trace, only the messages:

  2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
  2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
  2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
  2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'

  And that's it.

  You can't really get out of this without manually running 'apt-get
  install qemu-guest-agent' because at this point, unattended-upgrade
  can't update itself anymore.

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

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

[Touch-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick

[Kai-Heng Feng]

Thanks for pointing out the regression commit. The patch author is from
Sony, so it's better to ask the patch author directly the justification
behind blacklisting.

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

Title:
  Dualshock3 hid_sony accelerometer not registering as joystick

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

Bug description:
  [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25
  [12649.015925] input: Sony PLAYSTATION(R)3 Controller as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24
  [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 
Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90

  4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  
  perhaps this is only a config issue as when the new split gyro & analog 
sticks/buttons/triggers 
  both appeared as  joysticks while you can now see only Sony PLAYSTATION(R)3 
Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 
Controller Motion Sensors (input25) does not.

  Any questions I am happy to respond, I have every reason to believe this is 
actually not a bluez issue but google gives me no returns other than general 
compatibility issues over the new hid_sony driver splitting the gyro from the 
pad.  I use this to stay current on instrument flying while working out of town 
using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator 
that fis in my laptop bag.
  thanks
  dave

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Oct 31 15:06:00 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 60:F6:77:DD:DB:90  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:624605 acl:10743 sco:0 events:125 errors:0
TX bytes:5814 acl:12 sco:0 commands:106 errors:0

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

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

[Touch-packages] [Bug 1783272] Re: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces

[Launchpad Bug Tracker]

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

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

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

Title:
  upgrading systemd package restarts systemd-networkd and briefly takes
  down network interfaces

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Upgrading the systemd package, which contains systemd-networkd,
  appears to restart networkd and subsequently reconfigure network
  interfaces causing a brief connectivity outage.

  This is a bionic system which has a network bridge as it's primary
  interface through netplan.

  You can see from the logs that the interface appears to have been briefly 
taken down
  > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered 
disabled state

  We also see logs of networkd restarting
  > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service...
  > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service.
  > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service...

  Based on the ordering of the messages from Avahi, I also believe that
  the IP address was first removed, then it was taken down, brought back
  up, and the IP re-added. But I can not state that with 100% certainty.
  However if you just set an interface down manually (ip link set br0
  down), usually Avahi notes the interface is relevant before the
  address was removed.  We see the opposite here.  It's possible the
  ordering is just not entirely deterministic though.

  Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 
10.48.134.22 on br0.
  Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer 
relevant for mDNS.

  The main reason I noticed this, is that the unofficial oracle-
  java8-installer package upgraded at the same time - and it's wget to
  download java failed due to "Network is unreachable" as it was
  upgraded as the same time. To be clear, I'm not suggesting necessarily
  that this specific package was affected is the bug, but it's the
  reason I noticed the restart and it did cause an upgrade failure which
  I resumed with "dpkg --configure -a".  However there are many other
  implications of the network interface being reconfigured.

  Generally it's probably just not ideal to have networkd restart and
  reconfigure the network interfaces - no matter the possible causes.
  But from a quick thought about realistic implications

   - it seems the bridge was not deleted/re-created which would be bad
  for systems using libvirt/lxd/etc where the VMs may drop off the
  bridge. The interface index didn't change so hopefully we're safe from
  this one ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev
  exists, using existing without changing its parameters")

   - Another use case other than oracle-java8-installer that is highly
  likely to be impacted is daemons configured to bind to a specific IP
  address. By default, those binds will fail if the IP address doesn't
  exist. It's possible these two restarts will race and those services
  will fail to restart. An example where this could happen, is Apache2.
  It would probably be hard to reproduce but logically likely to occur
  in some small number of cases.

   - we potentially do want networkd to ideally restart to upgrade the
  code, but ideally it would "diff" the network interface config and not
  tear things down. I am using a 'switchport' match in my netplan
  config, I wonder if this is related?

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

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

[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

[Christian Ehrhardt ]

Fix might be in qemu (add even more special cases) or in unattended
upgrades (to properly handle or at least not die). Added a bug task for
that.

** Description changed:

  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.
  
  That all worked fine and moved the conffile.
  
  It was now reported that due to some pre-checks that unattended upgrades
  might do this might do some checks on its own.
  
  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)
+ 
+ 
+ --- original report copied ---
+ 
+ just wanted to add: This bug also crashes unattended-upgrade and thus
+ prevents security updates on 18.04:
+ 
+ root@mailin1:~# unattended-upgrade
+ Traceback (most recent call last):
+   File "/usr/bin/unattended-upgrade", line 1998, in 
+ sys.exit(main(options))
+   File "/usr/bin/unattended-upgrade", line 1714, in main
+ if conffile_prompt(item.destfile):
+   File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
+ with open(prefix + conf_file, 'rb') as fp:
+ IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'
+ 
+ Basically, unattended-upgrade wants to compare old/new conffiles and
+ doesn't like it when the old conffile turns out to be a directory...
+ 
+ This prevents security updates to be installed. The unattended-upgrade
+ logs do not contain the trace, only the messages:
+ 
+ 2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
+ 2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
+ 2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
+ 2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'
+ 
+ And that's it.
+ 
+ You can't really get out of this without manually running 'apt-get
+ install qemu-guest-agent' because at this point, unattended-upgrade
+ can't update itself anymore.

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  
  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...

  This prevents security updates to be installed. The unattended-upgrade
  logs do not contain the trace, only the messages:

  2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
  2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
  2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
  2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'

  And that's it.

  You can't really get out of this without manually running 'apt-get
  install qemu-guest-agent' because at this point, unattended-upgrade
  can't update itself anymore.

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

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

[Ioanna Alifieraki]

** 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 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 1823872] [NEW] Fixing fsfreeze-hook can break unattended upgrades

[Christian Ehrhardt ]

Public bug reported:

As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

That all worked fine and moved the conffile.

It was now reported that due to some pre-checks that unattended upgrades
might do this might do some checks on its own.

Next step:
- check unattended upgrades through this change
- check if it only affects cases were the former config was modified (minority) 
or the default file layout (majority)


--- original report copied ---

just wanted to add: This bug also crashes unattended-upgrade and thus
prevents security updates on 18.04:

root@mailin1:~# unattended-upgrade
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1998, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1714, in main
if conffile_prompt(item.destfile):
  File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
with open(prefix + conf_file, 'rb') as fp:
IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

Basically, unattended-upgrade wants to compare old/new conffiles and
doesn't like it when the old conffile turns out to be a directory...

This prevents security updates to be installed. The unattended-upgrade
logs do not contain the trace, only the messages:

2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'

And that's it.

You can't really get out of this without manually running 'apt-get
install qemu-guest-agent' because at this point, unattended-upgrade
can't update itself anymore.

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

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  
  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  Basically, unattended-upgrade wants to compare old/new conffiles and
  doesn't like it when the old conffile turns out to be a directory...

  This prevents security updates to be installed. The unattended-upgrade
  logs do not contain the trace, only the messages:

  2019-04-05 13:24:24,851 INFO Initial blacklisted packages:
  2019-04-05 13:24:24,853 INFO Initial whitelisted packages:
  2019-04-05 13:24:24,853 INFO Starting unattended upgrades script
  2019-04-05 13:24:24,854 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic'

  And that's it.

  You can't really get out of this without manually running 'apt-get
  install qemu-guest-agent' because at this point, unattended-upgrade
  can't update itself anymore.

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

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