date:20190207

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

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

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

Title:
  Unable to enable/disable  a repository in Software and Updates GUI

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  When I click the checkbox to enable/disable a repository nothing
  happens. On 16.04 I was able to enable/disable repository in GUI, now
  I can't.

  Release Ubuntu 18.04.1 LTS
  package software-properties-gtk 0.96.24.32.5
  I expect to enable/disable repository in GUI
  Nothing happens when I click the check box.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  8 02:55:00 2018
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2016-03-31 (981 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-09-18 (80 days ago)

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

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

[Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100

This bug was fixed in the package procps - 2:3.3.15-2ubuntu2

---
procps (2:3.3.15-2ubuntu2) disco; urgency=medium

  * 10-network-security.conf: change the rp_filter default from 1 to 2,
the strict mode isn't compatible with the n-m handling of
captive portals (lp: #1814262)

 -- Sebastien Bacher   Thu, 07 Feb 2019 23:46:43
+0100

** Changed in: procps (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Wired interface gets impossibly high metric 20100

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  Actually this might be a heisenbug. I've had an issue with this all
  morning since network-manager got an update this morning, but just now
  *while this bug was being submitted* it decided to correct itself.

  What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
  a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the
  network-manager update I noticed everything was slower than I was used
  to, and in gnome-shell the network icon showing was the WiFi one, not
  the wired one.

  Looking at the output of route, or route -n for simplicity, I would
  see this:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 
enp63s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So the metric on the default route on enp63s0 had 20,000 mysteriously
  added to it, which would obviously make it extremely low-priority. The
  system was choosing the wifi connection instead, which isn't that
  great in my office, hence observable slowness.

  Now, this morning, this seemed to be the sticky situation. It didn't
  show any sign of changing, whatever I did, after restarts of network-
  manager, undock/redock, reboots, etc. I could change it manually with
  ifmetric (and it would work), but that was about it.

  I would have reported the bug then, but I had to go out. When I got
  back I plugged in and initially saw the same thing again (that's where
  the above snippet was pasted from). But *while* the ubuntu-bug
  network-manager command was running, I noticed the gnome-shell network
  icon switch to wired, checked again, and saw:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG10000 
enp63s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So now the wifi connection has 20,000 added to it, which may still be
  wrong? But I wouldn't otherwise have noticed it because the system is
  again *behaving* as expected.

  This all seemed to happen after the network-manager upgrade (from
  1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
  metric+20,000 values were present before then, because I didn't have
  any cause to go looking at it, it always just worked. Could it be some
  issue with how the newer network-manager, or one of its associated
  packages, is figuring out the metrics on new connections? Like it's
  running some new heuristic to determine which one should really be the
  preferred? If it's like it was just now, when it fixed itself after a
  minute or so, that's not really a problem, but if it's like it was
  this morning when it just seemed to be stuck with the ethernet
  connection at 20100, it is.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 13:15:06 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2019-02-07 Thread VanVan

@avreon Keep in mind there is two different fixes to the kernel depending on 
your hardware :
- Fix for UX333, UX433, UX533 and some others starting from 4.19.10
- Fix for UX391UA and some others starting from kernel 5.0-rc1

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+subscriptions

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

[Touch-packages] [Bug 882825] Re: Does not save the configuration file under ~/.config/

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

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

Title:
  Does not save the configuration file under ~/.config/

Status in The Gimp:
  Fix Released
Status in adobe-flashplugin package in Ubuntu:
  New
Status in bash package in Ubuntu:
  New
Status in bzr package in Ubuntu:
  Fix Released
Status in compiz package in Ubuntu:
  Confirmed
Status in dbus package in Ubuntu:
  New
Status in dia package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  Triaged
Status in gegl package in Ubuntu:
  Fix Released
Status in gimp package in Ubuntu:
  Confirmed
Status in gl-117 package in Ubuntu:
  New
Status in gnome-games package in Ubuntu:
  Fix Released
Status in gnupg package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  Confirmed
Status in hydrogen package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Fix Released
Status in onboard package in Ubuntu:
  Fix Released
Status in python-launchpadlib package in Ubuntu:
  Invalid
Status in shotwell package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  New
Status in w3m package in Ubuntu:
  New
Status in xchat package in Ubuntu:
  Triaged

Bug description:
  It does not save the configuration file(s) and/or the cache under the
  right location for configuration file storage which is under
  ~/.config/ and ~/.cache/

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

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

[Touch-packages] [Bug 1815101] Re: netplan removes keepalived configuration

2019-02-07 Thread Leroy Tennison

I am trying ifupdown.  Do I need to do anythnig else or is what I've
done adequate?

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

Title:
  netplan removes keepalived configuration

Status in netplan:
  Invalid
Status in keepalived package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth2:
  addresses:
- 12.13.14.18/29
- 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone
  }
  vrrp_instance wan {
  state MASTER
  interface eth2
  virtual_router_id 77
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass BlahBlah
  }
  virtual_ipaddress {
  12.13.14.20
  }
  }
  vrrp_instance lan {
  state MASTER
  interface eth3
  virtual_router_id 78
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MoreBlah
  }
  virtual_ipaddress {
  10.22.11.13/24
  }
  }
  vrrp_instance phone {
  state MASTER
  interface eth4
  virtual_router_id 79
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MostBlah
  }
  virtual_ipaddress {
  10.22.14.3/24
  }
  }

  At boot the affected interfaces have:
  5: eth4:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff
  inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4
 valid_lft forever preferred_lft forever
  inet 10.22.14.3/24 scope global secondary eth4
 valid_lft forever preferred_lft forever
  inet6 fe80::ae1f:6bff:fe90:c0e3/64 scope link 
 valid_lft forever preferred_lft forever
  7: eth3:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether ab:cd:ef:b0:26:29 brd ff:ff:ff:ff:ff:ff
  inet 10.22.11.6/24 brd 10.22.11.255 scope global eth3
 valid_lft forever preferred_lft forever
  inet 10.22.11.13/24 scope global secondary eth3
 valid_lft forever preferred_lft forever
  inet6 fe80::ae1f:6bff:feb0:2629/64 scope link 
 valid_lft forever preferred_lft forever
  9: eth2:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether ab:cd:ef:b0:26:2b brd ff:ff:ff:ff:ff:ff
  inet 12.13.14.18/29 brd 12.13.14.23 scope global eth2
 valid_lft forever preferred_lft forever
  inet 12.13.14.20/32

[Touch-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract

2019-02-07 Thread Edson José dos Santos

The Ubuntu version is this:


edson@edson-p6540br:~$ neofetch
.-/+oooo+/-.   edson@edson-p6540br 
`:+ss+:`   --- 
  -+ssyy+- OS: Ubuntu Disco Dingo (development  
.ossdMMMNyo.   Host: p6540br xxx0204GR0 
   /ssshdmmNNmmyNhss/  Kernel: 4.19.0-12-generic 
  +shmydMMMNy+ Uptime: 41 mins 
 /hNMMMyhhhmNMMMNh/Packages: 2137 (dpkg), 8 (snap) 
.dMMMNhsshNMMMd.   Shell: bash 5.0.2 
+hhhyNMMNyyNMMMysss+   Resolution: 1024x768 
ossyNMMMNyMMhsshmmmhssso   DE: GNOME 3.30.2 
ossyNMMMNyMMhsshmmmhssso   WM: GNOME Shell 
+hhhyNMMNyyNMMMysss+   WM Theme: Adwaita 
.dMMMNhsshNMMMd.   Theme: Yaru [GTK2/3] 
 /hNMMMyhhhdNMMMNh/Icons: Yaru [GTK2/3] 
  +sdmydy+ Terminal: gnome-terminal 
   /ssshdmmyNhss/  CPU: Intel i3 540 (4) @ 3.067GHz 
.ossdMMMNyo.   GPU: Intel Core Processor 
  -+syyy+- Memory: 3216MiB / 7710MiB 
`:+ss+:`
.-/+oooo+/-.   


edson@edson-p6540br:~$ 


The requested is attached.

Or Ruindows 10 is eating less memory than the gnome.


** Attachment added: "Jornalclt log"
   
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1815089/+attachment/5236881/+files/Jornalclt%20log

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

Title:
  100% CPU / usr / lib / tracker / tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  The / usr / lib / tracker / tracker-extract is using almost 100% CPU
  resources see attached image

  After updates on today's date 07/02/2019 has improved the crashes, but
  the hunger for CPU continues.

  **

  O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos
  da CPU vide imagem em anexo

  Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
  mas a fome por CPU continua.

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

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

[Touch-packages] [Bug 1635803] Re: middle mouse shortcut broken

The issue is a gtk one, https://gitlab.gnome.org/GNOME/gtk/issues/1512

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- middle mouse shortcut broken
+ ragging file with middle mouse button doesn't show "Copy/Move/Link" context 
menu

** Summary changed:

- ragging file with middle mouse button doesn't show "Copy/Move/Link" context 
menu
+ dragging file with middle mouse button doesn't show "Copy/Move/Link" context 
menu

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

Title:
  dragging file with middle mouse button doesn't show "Copy/Move/Link"
  context menu

Status in Nautilus:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  middle mouse a file, drag and drop it used to bring out a copy, move, etc 
dialog. This is now missing in 16.10.
  Can we please have this back, and an option to make the shortcut using 
rightclick + drag would be an improvement also.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 22 19:14:18 2016
  InstallationDate: Installed on 2016-10-14 (8 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Touch-packages] [Bug 1635803] [NEW] middle mouse shortcut broken

You have been subscribed to a public bug:

middle mouse a file, drag and drop it used to bring out a copy, move, etc 
dialog. This is now missing in 16.10.
Can we please have this back, and an option to make the shortcut using 
rightclick + drag would be an improvement also.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 22 19:14:18 2016
InstallationDate: Installed on 2016-10-14 (8 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

** Affects: nautilus
 Importance: Medium
 Status: Invalid

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: amd64 apport-bug third-party-packages yakkety
-- 
middle mouse shortcut broken
https://bugs.launchpad.net/bugs/1635803
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1792978] Re: initscript avahi-daemon, action "start" failed

2019-02-07 Thread Alexander Balderson

** Tags added: cdo-qa

** Tags added: foundations-engine

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

Title:
  initscript avahi-daemon, action "start" failed

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  When installing maas-region-controller, avahi-deamon failed to install
  because it was it seemed to already be running.

  
  $ apt-get -q install -y maas-region-controller
  
  [1invoke-rc.d: initscript avahi-daemon, action "start" failed.
  [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack
 Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor 
preset: enabled)
 Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 
19:42:29 UTC; 9ms ago
 Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, 
status=255)[0m
   Main PID: 22726 (code=exited, status=255)
   
  Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
  Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 
21868
  Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main 
process exit.../a[0m
  Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi 
mDNS/DNS-SD Stack.[0m
  Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit 
entered fail...e.[0m
  Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed 
with resul...'.[0m
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: error processing package avahi-daemon (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of avahi-utils:
   avahi-utils depends on avahi-daemon; however:
Package avahi-daemon is not configured yet.

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

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

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

2019-02-07 Thread Eric Desrochers

** Changed in: apt (Ubuntu Trusty)
 Assignee: Heitor R. Alves de Siqueira (halves) => (unassigned)

** Changed in: apt (Ubuntu Trusty)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  In Progress

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.2.10ubuntu1   | xenial   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
   apt | 1.6.1   | bionic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.7.0   | cosmic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.8.0~rc2   | disco| source, amd64, arm64, 
armhf, i386, ppc64el, s390x


  [Test Case]
  Unfortunately, this issue is not easy to reproduce. It seems to trigger 
randomly when "apt-cache policy" is called on a system under memory pressure, 
triggering the failure path in the mmap() allocations.

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2019-02-07 Thread antubis

I have the issue that Maksym is talking about. Indeed using 4.19.18
"fixed" the problem but it seems to be fixed somehow randomly. When I
restart the laptop and enter my paassword, Linux Mint tries to play an
intro chime but it gets cut off at the middle or at the end. I have to
restart, login and it may or maynot fix the issue. After few restarts it
starts working permanently for the duration of the session but this is
not a real solution, isn't it? If someone is aware how to fix this issue
please raise your voice!

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+subscriptions

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

[Touch-packages] [Bug 1811248] Re: systemd--networkd mounts denied for lxc guest

2019-02-07 Thread km

Whilst 'lxc.apparmor.profile: unconfined' appears the only way to keep
unprivileged lxc guests with systemd v240 alive it defeats the purpose
of AppArmor.

Notwithstanding, the tail riding on this bug

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813622
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=030919ba5e4931d6ee576d0259fae67fe4ed9770

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

Title:
  systemd--networkd mounts denied for lxc guest

Status in apparmor package in Ubuntu:
  New

Bug description:
  Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7
  Guest Arch Linux | systemd 240.0

  After having upgraded in the guest systemd from 239.370 to 240.0 the
  host's AA is exhibiting

  > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED"
  operation="mount" info="failed flags match" error=-13 profile="lxc-
  container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw,
  rslave"

  and the guest

  > systemd-networkd.service: Failed to set up mount namespacing: Permission 
denied
  > systemd-networkd.service: Failed at step NAMESPACE spawning 
/usr/lib/systemd/systemd-networkd: Permission denied

  According to lxc bug tracker https://github.com/lxc/lxc/issues/2778

  > While we'd like to allow such mounts we cannot do so until the
  apparmor_parser is fixed to handle them correctly.

  other cross references

  https://github.com/systemd/systemd/issues/11371
  https://bugs.archlinux.org/task/61313

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

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

Re: [Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-02-07 Thread Kaj Printz Madsen

Another thing I noticed is a noticeably lower max output volume when using
the stereo output device, I'm no sure if that's a bug or intended but now
you know.

On Thu, 7 Feb 2019 at 19:45, Kaj Printz Madsen 
wrote:

> As the picture shows the ppa seems to be working fine. The stereo device
> has the profiles, "Analog Stereo Output" and "Analog Mono Output + Analog
> Stereo Output + Analog Mono Input" but selecting the former profile
> automatically selects the mono device which is confusing to me.
>
>
>
> [image: Screenshot from 2019-02-07 19-37-11.png]
>
>
>
> On Thu, 7 Feb 2019 at 19:21, Kaj Printz Madsen 
> wrote:
>
>> Yeah I will.
>>
>> On Tue, 5 Feb 2019 at 19:25, Dave Chiluk <1758...@bugs.launchpad.net>
>> wrote:
>>
>>> @Kaj Printz Madsen
>>>
>>> I know you opened this a long time ago, but is there any chance you
>>> could test the ppa for me?
>>>
>>> Thanks.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1758736
>>>
>>> Title:
>>>   [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
>>>   mono playback
>>>
>>> Status in pulseaudio package in Ubuntu:
>>>   Confirmed
>>> Status in pulseaudio source package in Bionic:
>>>   In Progress
>>> Status in pulseaudio source package in Cosmic:
>>>   Confirmed
>>> Status in pulseaudio source package in Disco:
>>>   Confirmed
>>>
>>> Bug description:
>>>   There is not stereo playback only mono playback
>>>
>>>   ProblemType: Bug
>>>   DistroRelease: Ubuntu 17.10
>>>   Package: pulseaudio 1:10.0-2ubuntu3.1
>>>   ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
>>>   Uname: Linux 4.13.0-37-generic x86_64
>>>   ApportVersion: 2.20.7-0ubuntu3.7
>>>   Architecture: amd64
>>>   AudioDevicesInUse:
>>>USERPID ACCESS COMMAND
>>>/dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
>>>/dev/snd/controlC1:  kaj1755 F pulseaudio
>>>/dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
>>>/dev/snd/controlC0:  kaj1755 F pulseaudio
>>>   CurrentDesktop: ubuntu:GNOME
>>>   Date: Sun Mar 25 21:30:50 2018
>>>   InstallationDate: Installed on 2018-03-08 (17 days ago)
>>>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
>>> (20180105.1)
>>>   SourcePackage: pulseaudio
>>>   Symptom: audio
>>>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7
>>> successful
>>>   Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
>>>   Symptom_PulsePlaybackTest: PulseAudio playback test failed
>>>   Symptom_Type: No sound at all
>>>   Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
>>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>>   dmi.bios.date: 03/09/2016
>>>   dmi.bios.vendor: LENOVO
>>>   dmi.bios.version: R06ET35W (1.09 )
>>>   dmi.board.asset.tag: Not Available
>>>   dmi.board.name: 20FMS2AV00
>>>   dmi.board.vendor: LENOVO
>>>   dmi.board.version: SDK0J40697 WIN
>>>   dmi.chassis.asset.tag: No Asset Information
>>>   dmi.chassis.type: 10
>>>   dmi.chassis.vendor: LENOVO
>>>   dmi.chassis.version: None
>>>   dmi.modalias:
>>> dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
>>>   dmi.product.family: ThinkPad T460
>>>   dmi.product.name: 20FMS2AV00
>>>   dmi.product.version: ThinkPad T460
>>>   dmi.sys.vendor: LENOVO
>>>
>>> To manage notifications about this bug go to:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
>>>
>>


** Attachment added: "Screenshot from 2019-02-07 19-37-11.png"
   
https://bugs.launchpad.net/bugs/1758736/+attachment/5236870/+files/Screenshot%20from%202019-02-07%2019-37-11.png

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  Confirmed
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)

[Touch-packages] [Bug 1815129] Re: apt segfaults when generating cache file

2019-02-07 Thread Eric Desrochers

** Also affects: apt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Changed in: apt (Ubuntu Trusty)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

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

** Tags added: sts

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  In Progress

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.2.10ubuntu1   | xenial   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
   apt | 1.6.1   | bionic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.7.0   | cosmic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.8.0~rc2   | disco| source, amd64, arm64, 
armhf, i386, ppc64el, s390x


  [Test Case]
  Unfortunately, this issue is not easy to reproduce. It seems to trigger 
randomly when "apt-cache policy" is called on a system under memory pressure, 
triggering the failure path in the mmap() allocations.

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1815129] [NEW] apt segfaults when generating cache file

2019-02-07 Thread Heitor R. Alves de Siqueira

Public bug reported:

[Impact]
apt crashes (core dump) during cache creation

[Description]
When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

Upstream commit: https://salsa.debian.org/apt-
team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

$ git describe --contains 6789e01e9370
1.1_exp16~5

$ rmadison apt
 apt | 1.0.1ubuntu2| trusty   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
 apt | 1.0.1ubuntu2.19 | trusty-security  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
 apt | 1.0.1ubuntu2.19 | trusty-updates   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
 apt | 1.2.10ubuntu1   | xenial   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
 apt | 1.6.1   | bionic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
 apt | 1.7.0   | cosmic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
 apt | 1.8.0~rc2   | disco| source, amd64, arm64, 
armhf, i386, ppc64el, s390x


[Test Case]
Unfortunately, this issue is not easy to reproduce. It seems to trigger 
randomly when "apt-cache policy" is called on a system under memory pressure, 
triggering the failure path in the mmap() allocations.

[Regression Potential]
The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
We also have a confirmation from an impacted user that the upstream patch fixes 
their issue without further problems.

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

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

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

Title:
  apt segfaults when generating cache file

Status in apt package in Ubuntu:
  New
Status in apt source package in Trusty:
  New

Bug description:
  [Impact]
  apt crashes (core dump) during cache creation

  [Description]
  When executing apt-cache several times on a memory constrained system, 
apt-cache can sometimes crash with a core dump file. This is related to mmap() 
failing allocations during cache generation, according to an upstream bug 
report (803417).
  There is an upstream patch for this bug (6789e01e do not segfault in cache 
generation on mmap failure) and it's included in the apt package for other 
series (see below), so we only need to backport it to Trusty.

  Upstream commit: https://salsa.debian.org/apt-
  team/apt/commit/6789e01e9370b3b7f65d52138c5657eaa712b4d1

  $ git describe --contains 6789e01e9370
  1.1_exp16~5

  $ rmadison apt
   apt | 1.0.1ubuntu2| trusty   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-security  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.0.1ubuntu2.19 | trusty-updates   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
   apt | 1.2.10ubuntu1   | xenial   | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
   apt | 1.6.1   | bionic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.7.0   | cosmic   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
   apt | 1.8.0~rc2   | disco| source, amd64, arm64, 
armhf, i386, ppc64el, s390x


  [Test Case]
  Unfortunately, this issue is not easy to reproduce. It seems to trigger 
randomly when "apt-cache policy" is called on a system under memory pressure, 
triggering the failure path in the mmap() allocations.

  [Regression Potential]
  The regression potential for this should be low, as it's a change in the 
failure path for memory allocations. This shouldn't be triggered during normal 
usage, and we'll thoroughly test the patched package with autopkgtests and 
perform scripted runs in memory-constrained systems with stress-ng.
  We also have a confirmation from an impacted user that the upstream patch 
fixes their issue without further problems.

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

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

[Touch-packages] [Bug 1815125] [NEW] constant video freezes in firefox with x-x-v-amdgpu 18.1.0

2019-02-07 Thread Timo Aaltonen

Public bug reported:

[Impact]

There are constant video freezes in firefox (e.g. on youtube) with xf86
-video-amdgpu-18.1.0, which is included in the HWE stack in 18.04.2

https://bugs.freedesktop.org/show_bug.cgi?id=107992

[Test case]

test firefox with youtube on radeon

[Regression potential]

it's a single commit from upstream 1.6.7, shouldn't regress anything

** Affects: libx11 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: libx11 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

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

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

** Summary changed:

- periodic video freezes in firefox with x-x-v-amdgpu 18.1.0
+ constant video freezes in firefox with x-x-v-amdgpu 18.1.0

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

Title:
  constant video freezes in firefox with x-x-v-amdgpu 18.1.0

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  New

Bug description:
  [Impact]

  There are constant video freezes in firefox (e.g. on youtube) with
  xf86-video-amdgpu-18.1.0, which is included in the HWE stack in
  18.04.2

  https://bugs.freedesktop.org/show_bug.cgi?id=107992

  [Test case]

  test firefox with youtube on radeon

  [Regression potential]

  it's a single commit from upstream 1.6.7, shouldn't regress anything

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

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

[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window

apport will first try using xdg-open and that also appears as being
found in the strace output. What happens if your run 'xdg-open
http://bugs.launchpad.net'?

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

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

Title:
  ubuntu-bug never (any longer) opens browser window

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the one 
that is correct (/usr/bin/firefox, which returned a successful stat call).  
I'll attach the trace output from
 
 strace -f -o /tmp/strace.log ubuntu-bug apport

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

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

[Touch-packages] [Bug 1228895] Re: package libx11-xcb-dev doesn't allow for amd64 to be installed alongside i386

2019-02-07 Thread Timo Aaltonen

should be fixed by now

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

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

Title:
  package libx11-xcb-dev doesn't allow for amd64 to be installed
  alongside i386

Status in libx11 package in Ubuntu:
  Fix Released

Bug description:
  On a x86-64 system, if I type:
  $ sudo apt-get install libx11-xcb-dev:i386

  I am informed that libx11-xcb-dev will be uninstalled.

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

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

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

This bug was fixed in the package landscape-client -
16.03-0ubuntu2.16.04.5

---
landscape-client (16.03-0ubuntu2.16.04.5) xenial; urgency=medium

  * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor (LP: #1788219)
  * Fixes for release-upgrade (LP: #1699179).
- debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu-
  release-upgrader is running before apt-update. (LP: #1699179)
- debian/patches/release-upgrade-success.patch: Enable landscape-client to
  survive trusty upgrade. (LP: #1670291)
- debian/patches/post-upgrade-reboot.patch: Force reboot operation in
  case systemd fails. (LP: #1670291)
  * debian/patches/1616116-resync-loop.patch:
Clear hash id database on package resync. (LP: #1616116)

 -- Simon Poirier   Tue, 27 Nov 2018
09:24:22 -0500

** Changed in: landscape-client (Ubuntu Trusty)
   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/1670291

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

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

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

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

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

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

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

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

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

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

This bug was fixed in the package landscape-client -
14.12-0ubuntu6.14.04.4

---
landscape-client (14.12-0ubuntu6.14.04.4) trusty; urgency=medium

  * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor. (LP: #1788219)
  * Fixes for release-upgrade (LP: #1699179).
- debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu-
  release-upgrader is running before apt-update. (LP: #1699179)
- debian/patches/release-upgrade-success.patch: Enable landscape-client to
  survive trusty upgrade. (LP: #1670291)
- debian/patches/post-upgrade-reboot.patch: Force reboot operation in
  case systemd fails. (LP: #1670291)
  * debian/patches/1616116-resync-loop.patch:
Clear hash id database on package resync. (LP: #1616116)

 -- Simon Poirier   Tue, 27 Nov 2018
09:24:22 -0500

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

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

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

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

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

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

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

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

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

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

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

This bug was fixed in the package landscape-client - 18.01-0ubuntu4.1

---
landscape-client (18.01-0ubuntu4.1) cosmic; urgency=medium

  * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor. (LP: #1788219)
  * Fixes for release-upgrade:
- debian/patches/release-upgrade-success.patch: Enable landscape-client to
  survive trusty upgrade. (LP: #1670291)
- debian/patches/post-upgrade-reboot.patch: Force reboot operation in
  case systemd fails. (LP: #1670291)
  * debian/patches/unicode-tags-script.patch: Permit environments
containing unicode chars for script execution. (LP: #1765518)
  * debian/patches/1616116-resync-loop.patch:
Clear hash id database on package resync. (LP: #1616116)

 -- Simon Poirier   Tue, 27 Nov 2018
09:24:22 -0500

** Changed in: landscape-client (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

** Changed in: landscape-client (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/1670291

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

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

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

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

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

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

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

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

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

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

This bug was fixed in the package landscape-client - 18.01-0ubuntu3.2

---
landscape-client (18.01-0ubuntu3.2) bionic; urgency=medium

  * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor. (LP: #1788219)
  * Fixes for release-upgrade:
- debian/patches/release-upgrade-success.patch: Enable landscape-client to
  survive trusty upgrade. (LP: #1670291)
- debian/patches/post-upgrade-reboot.patch: Force reboot operation in
  case systemd fails. (LP: #1670291)
  * debian/patches/unicode-tags-script.patch: Permit environments
containing unicode chars for script execution. (LP: #1765518)
  * debian/patches/1616116-resync-loop.patch:
Clear hash id database on package resync. (LP: #1616116)

 -- Simon Poirier   Tue, 27 Nov 2018
09:24:22 -0500

** Changed in: landscape-client (Ubuntu Xenial)
   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/1670291

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

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

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

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

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

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

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

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

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

[Touch-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract

Thank you for your bug report. On what Ubuntu serie are you? Could you
add your journalctl log to the bug?

** Package changed: gnome-software (Ubuntu) => tracker (Ubuntu)

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

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

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

Title:
  100% CPU / usr / lib / tracker / tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  The / usr / lib / tracker / tracker-extract is using almost 100% CPU
  resources see attached image

  After updates on today's date 07/02/2019 has improved the crashes, but
  the hunger for CPU continues.

  **

  O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos
  da CPU vide imagem em anexo

  Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
  mas a fome por CPU continua.

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

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

[Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Status: New => In Progress

** Package changed: network-manager (Ubuntu) => procps (Ubuntu)

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

Title:
  Wired interface gets impossibly high metric 20100

Status in procps package in Ubuntu:
  In Progress

Bug description:
  Actually this might be a heisenbug. I've had an issue with this all
  morning since network-manager got an update this morning, but just now
  *while this bug was being submitted* it decided to correct itself.

  What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
  a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the
  network-manager update I noticed everything was slower than I was used
  to, and in gnome-shell the network icon showing was the WiFi one, not
  the wired one.

  Looking at the output of route, or route -n for simplicity, I would
  see this:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 
enp63s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So the metric on the default route on enp63s0 had 20,000 mysteriously
  added to it, which would obviously make it extremely low-priority. The
  system was choosing the wifi connection instead, which isn't that
  great in my office, hence observable slowness.

  Now, this morning, this seemed to be the sticky situation. It didn't
  show any sign of changing, whatever I did, after restarts of network-
  manager, undock/redock, reboots, etc. I could change it manually with
  ifmetric (and it would work), but that was about it.

  I would have reported the bug then, but I had to go out. When I got
  back I plugged in and initially saw the same thing again (that's where
  the above snippet was pasted from). But *while* the ubuntu-bug
  network-manager command was running, I noticed the gnome-shell network
  icon switch to wired, checked again, and saw:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG10000 
enp63s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So now the wifi connection has 20,000 added to it, which may still be
  wrong? But I wouldn't otherwise have noticed it because the system is
  again *behaving* as expected.

  This all seemed to happen after the network-manager upgrade (from
  1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
  metric+20,000 values were present before then, because I didn't have
  any cause to go looking at it, it always just worked. Could it be some
  issue with how the newer network-manager, or one of its associated
  packages, is figuring out the metrics on new connections? Like it's
  running some new heuristic to determine which one should really be the
  preferred? If it's like it was just now, when it fixed itself after a
  minute or so, that's not really a problem, but if it's like it was
  this morning when it just seemed to be stuck with the ethernet
  connection at 20100, it is.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 13:15:06 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true

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

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

---
upower (0.99.8-2ubuntu0.2) cosmic; urgency=medium

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

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Detect AC state on pending state. (LP: #1745032)
  * debian/gbp.conf: update branch to ubuntu/cosmic

 -- Iain Lane   Fri, 25 Jan 2019 16:23:16 +

** Changed in: upower (Ubuntu Cosmic)
   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:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
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] Update Released

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
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

This bug was fixed in the package gnome-control-center -
1:3.30.2-1ubuntu0.18.10.2

---
gnome-control-center (1:3.30.2-1ubuntu0.18.10.2) cosmic; 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:08:03 +

** Changed in: gnome-control-center (Ubuntu Cosmic)
   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:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
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 1815089] [NEW] 100% CPU / usr / lib / tracker / tracker-extract

You have been subscribed to a public bug:

The / usr / lib / tracker / tracker-extract is using almost 100% CPU
resources see attached image

After updates on today's date 07/02/2019 has improved the crashes, but
the hunger for CPU continues.

**

O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos da
CPU vide imagem em anexo

Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
mas a fome por CPU continua.

** Affects: tracker (Ubuntu)
 Importance: High
 Status: Incomplete


** Tags: 100 cpu
-- 
100% CPU / usr / lib / tracker / tracker-extract
https://bugs.launchpad.net/bugs/1815089
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to tracker in Ubuntu.

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

[Touch-packages] [Bug 1815115] [NEW] Hangs on or restarts frequently

2019-02-07 Thread Ramalingam Ganapathy

Public bug reported:

My computer hangs on or restarts automatically. It happens frequently.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CompositorRunning: None
Date: Fri Feb  8 00:33:36 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] 
(rev d4) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Kaveri [Radeon R7 Graphics] [1849:130f]
InstallationDate: Installed on 2017-10-16 (478 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=31761012-8def-42cc-8154-70ebb1afe3e4 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: A88M-G/3.1
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic ubuntu

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

Title:
  Hangs on or restarts frequently

Status in xorg package in Ubuntu:
  New

Bug description:
  My computer hangs on or restarts automatically. It happens frequently.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Feb  8 00:33:36 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (rev d4) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Kaveri [Radeon R7 Graphics] [1849:130f]
  InstallationDate: Installed on 2017-10-16 (478 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=31761012-8def-42cc-8154-70ebb1afe3e4 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1

[Touch-packages] [Bug 1815110] [NEW] CMake configuration files are missing

2019-02-07 Thread Alex K

Public bug reported:

The CMake configuration files are only generated if CMake is used when building 
this package instead of autotools (see [1]).
I think it would be really nice if the ubunu package would include the cmake 
configure files in /lib/cmake/glog/ either by maually adding them or by 
switching the package build to CMake.

[1] https://github.com/google/glog/issues/4#issuecomment-442001197

** Affects: google-glog (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  CMake configuration files are missing

Status in google-glog package in Ubuntu:
  New

Bug description:
  The CMake configuration files are only generated if CMake is used when 
building this package instead of autotools (see [1]).
  I think it would be really nice if the ubunu package would include the cmake 
configure files in /lib/cmake/glog/ either by maually adding them or by 
switching the package build to CMake.

  [1] https://github.com/google/glog/issues/4#issuecomment-442001197

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

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

Re: [Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-02-07 Thread Kaj Printz Madsen

As the picture shows the ppa seems to be working fine. The stereo device
has the profiles, "Analog Stereo Output" and "Analog Mono Output + Analog
Stereo Output + Analog Mono Input" but selecting the former profile
automatically selects the mono device which is confusing to me.


[image: Screenshot from 2019-02-07 19-37-11.png]


On Thu, 7 Feb 2019 at 19:21, Kaj Printz Madsen 
wrote:

> Yeah I will.
>
> On Tue, 5 Feb 2019 at 19:25, Dave Chiluk <1758...@bugs.launchpad.net>
> wrote:
>
>> @Kaj Printz Madsen
>>
>> I know you opened this a long time ago, but is there any chance you
>> could test the ppa for me?
>>
>> Thanks.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1758736
>>
>> Title:
>>   [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
>>   mono playback
>>
>> Status in pulseaudio package in Ubuntu:
>>   Confirmed
>> Status in pulseaudio source package in Bionic:
>>   In Progress
>> Status in pulseaudio source package in Cosmic:
>>   Confirmed
>> Status in pulseaudio source package in Disco:
>>   Confirmed
>>
>> Bug description:
>>   There is not stereo playback only mono playback
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 17.10
>>   Package: pulseaudio 1:10.0-2ubuntu3.1
>>   ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
>>   Uname: Linux 4.13.0-37-generic x86_64
>>   ApportVersion: 2.20.7-0ubuntu3.7
>>   Architecture: amd64
>>   AudioDevicesInUse:
>>USERPID ACCESS COMMAND
>>/dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
>>/dev/snd/controlC1:  kaj1755 F pulseaudio
>>/dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
>>/dev/snd/controlC0:  kaj1755 F pulseaudio
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Sun Mar 25 21:30:50 2018
>>   InstallationDate: Installed on 2018-03-08 (17 days ago)
>>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
>> (20180105.1)
>>   SourcePackage: pulseaudio
>>   Symptom: audio
>>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7
>> successful
>>   Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
>>   Symptom_PulsePlaybackTest: PulseAudio playback test failed
>>   Symptom_Type: No sound at all
>>   Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 03/09/2016
>>   dmi.bios.vendor: LENOVO
>>   dmi.bios.version: R06ET35W (1.09 )
>>   dmi.board.asset.tag: Not Available
>>   dmi.board.name: 20FMS2AV00
>>   dmi.board.vendor: LENOVO
>>   dmi.board.version: SDK0J40697 WIN
>>   dmi.chassis.asset.tag: No Asset Information
>>   dmi.chassis.type: 10
>>   dmi.chassis.vendor: LENOVO
>>   dmi.chassis.version: None
>>   dmi.modalias:
>> dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
>>   dmi.product.family: ThinkPad T460
>>   dmi.product.name: 20FMS2AV00
>>   dmi.product.version: ThinkPad T460
>>   dmi.sys.vendor: LENOVO
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
>>
>


** Attachment added: "Screenshot from 2019-02-07 19-37-11.png"
   
https://bugs.launchpad.net/bugs/1758736/+attachment/5236809/+files/Screenshot%20from%202019-02-07%2019-37-11.png

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  Confirmed
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed

Re: [Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback

2019-02-07 Thread Kaj Printz Madsen

Yeah I will.

On Tue, 5 Feb 2019 at 19:25, Dave Chiluk <1758...@bugs.launchpad.net>
wrote:

> @Kaj Printz Madsen
>
> I know you opened this a long time ago, but is there any chance you
> could test the ppa for me?
>
> Thanks.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758736
>
> Title:
>   [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
>   mono playback
>
> Status in pulseaudio package in Ubuntu:
>   Confirmed
> Status in pulseaudio source package in Bionic:
>   In Progress
> Status in pulseaudio source package in Cosmic:
>   Confirmed
> Status in pulseaudio source package in Disco:
>   Confirmed
>
> Bug description:
>   There is not stereo playback only mono playback
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: pulseaudio 1:10.0-2ubuntu3.1
>   ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
>   Uname: Linux 4.13.0-37-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.7
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
>/dev/snd/controlC1:  kaj1755 F pulseaudio
>/dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
>/dev/snd/controlC0:  kaj1755 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 25 21:30:50 2018
>   InstallationDate: Installed on 2018-03-08 (17 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20180105.1)
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
>   Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
>   Symptom_PulsePlaybackTest: PulseAudio playback test failed
>   Symptom_Type: No sound at all
>   Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 03/09/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: R06ET35W (1.09 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20FMS2AV00
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0J40697 WIN
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad T460
>   dmi.product.name: 20FMS2AV00
>   dmi.product.version: ThinkPad T460
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
>

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

Title:
  [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
  mono playback

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Cosmic:
  Confirmed
Status in pulseaudio source package in Disco:
  Confirmed

Bug description:
  There is not stereo playback only mono playback

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   kaj1755 F...m pulseaudio
   /dev/snd/controlC1:  kaj1755 F pulseaudio
   /dev/snd/pcmC0D0c:   kaj1755 F...m pulseaudio
   /dev/snd/controlC0:  kaj1755 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 21:30:50 2018
  InstallationDate: Installed on 2018-03-08 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
  Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS2AV00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias:

[Touch-packages] [Bug 1815101] Re: netplan removes keepalived configuration

2019-02-07 Thread Mathieu Trudel-Lapierre

Kept a task for keepalived (Incomplete) in case it turns out there's
something we can do there.

Also added a task for systemd, since that would definitely require
development work.

Marked Invalid for netplan, as since netplan only translates config from
the YAML to what networkd or NetworkManager require, there isn't really
anything I see we can do in netplan directly. Applying absolutely does
need to 'poke' the renderer somehow for the configuration to be applied;
but if it turns out there's something to change in netplan we can update
the task.

Turns out there isn't really a PR about foreign addresses handling;
though two are somewhat relevant:

https://github.com/systemd/systemd/pull/9956
and
https://github.com/systemd/systemd/pull/7403

But neither will completely address the problem: systemd-networks
expects to be authoritative on the network setup, which is somewhat
counter to its use in conjunction with keepalived.

As a workaround, for now, one can use /etc/network/interfaces (and/or no
configuration in netplan for the interfaces handled by keepalived) to
configure the network.

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

Title:
  netplan removes keepalived configuration

Status in netplan:
  Invalid
Status in keepalived package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth2:
  addresses:
- 12.13.14.18/29
- 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone
  }
  vrrp_instance wan {
  state MASTER
  interface eth2
  virtual_router_id 77
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass BlahBlah
  }
  virtual_ipaddress {
  12.13.14.20
  }
  }
  vrrp_instance lan {
  state MASTER
  interface eth3
  virtual_router_id 78
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MoreBlah
  }
  virtual_ipaddress {
  10.22.11.13/24
  }
  }
  vrrp_instance phone {
  state MASTER
  interface eth4
  virtual_router_id 79
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MostBlah
  }
  virtual_ipaddress {
  10.22.14.3/24
  }
  }

  At boot the affected interfaces have:
  5: eth4:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether ab:cd:ef:90:c0:e3 brd

[Touch-packages] [Bug 1815101] Re: netplan removes keepalived configuration

2019-02-07 Thread Mathieu Trudel-Lapierre

This isn't netplan, it's systemd-networkd. Netplan only writes
configuration for the chosen renderer (in this case, systemd-networkd).

Either systemd needs to not wipe out foreign addresses (I believe there
is a PR in git for that) or keepalived should somehow interface with
systemd so they can collaborate on setting and keeping up the IP
addresses.

Reassigning.

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

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

** No longer affects: ubuntu

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

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

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

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

Title:
  netplan removes keepalived configuration

Status in netplan:
  Invalid
Status in keepalived package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth2:
  addresses:
- 12.13.14.18/29
- 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone
  }
  vrrp_instance wan {
  state MASTER
  interface eth2
  virtual_router_id 77
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass BlahBlah
  }
  virtual_ipaddress {
  12.13.14.20
  }
  }
  vrrp_instance lan {
  state MASTER
  interface eth3
  virtual_router_id 78
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MoreBlah
  }
  virtual_ipaddress {
  10.22.11.13/24
  }
  }
  vrrp_instance phone {
  state MASTER
  interface eth4
  virtual_router_id 79
  priority 150
  advert_int 1
  smtp_alert
  authentication {
  auth_type PASS
  auth_pass MostBlah
  }
  virtual_ipaddress {
  10.22.14.3/24
  }
  }

  At boot the affected interfaces have:
  5: eth4:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff
  inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4
 valid_lft forever preferred_lft forever
  inet 10.22.14.3/24 scope global secondary eth4
 valid_lft forever preferred_lft forever
  inet6 fe80::ae1f:6bff:fe90:c0e3/64 scope link 
 valid_lft forever preferred_lft forever
  7: eth3:  mtu 1500 qdisc mq

[Touch-packages] [Bug 1811225] Re: Mesa 18.2.8 stable release

2019-02-07 Thread Łukasz Zemczak

Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.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.

** Changed in: mesa (Ubuntu Bionic)
   Status: Confirmed => 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1811225

Title:
  Mesa 18.2.8 stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point 
release of the series. This will also be backported to 18.04 as part of the HWE 
stack update.

  Upstream changes:

  18.2.3
  - Different patches for the DirectX9 and DRI state trackers.
  - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza 
and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky.
  - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, 
anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in
  Radeonsi.
  - State Trackers also get different fixes and corrections.
  - Finally, fixes for GLSL and NIR are also in this queue.

  18.2.4
  - Different fixes for different drivers: freedreno, radeonsi, swr, anv and 
radv.
  - Also there are fixes for ac, gallium, spirv and blorp.

  18.2.5
  - A patch for nine state tracker that fixes several crashes using nine's
  thread_submit feature. There are other patches to other state trackers.
  - A couple of patches for Meson build system, as well as for autotools.
  - In the drivers side, there are a couple of fixes for RADV, one regarding
  subgroups and another regarding conditional rendering. There are also fixes 
for virgl, r600, and i965.
  - Finally, the queue contains a couple of fixes for NIR, Wayland, and other
  components.

  18.2.6
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.7
  - Several patches fixing leaks in glsl, winsys and r600.
  - Improvements in the scripts that helps in preparing releases.
  - Added PCI IDs for Amber Lake and Whiskey Lake.
  - Fixes for radv, anv, i965 and vc4 drivers.
  - A couple of fixes in NIR backend.
  - Finally, several fixes in meson build system.

  18.2.8
  - Several fixes in Meson build system.
  - Also several fixes for st/nine subcomponent.
  - Patch for RADV driver that fixes a hang in Yakuza using DXVK.
  - There are also fixes for Virgl driver.
  - Added PCI IDs for VegaM, Vega20 and Vega10.

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

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems, this is the last of the 
series so should be safe to update to.

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

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

[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2019-02-07 Thread Łukasz Zemczak

Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.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.

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Touch-packages] [Bug 1815094] Re: [FTBFS] cast between incompatible function types from ‘bool ()(nux::TextEntry)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco)

2019-02-07 Thread Alberts Muktupāvels

This seems to be caused by bool and gboolean incompatibility, but it is
not only build error...

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

Title:
  [FTBFS] cast between incompatible function types from ‘bool
  (*)(nux::TextEntry*)’ to ‘GSourceFunc’  gcc >= 8.1 (Disco)

Status in nux package in Ubuntu:
  Confirmed

Bug description:
  In disco it doesn't compile. I get

  cast between incompatible function types from ‘bool
  (*)(nux::TextEntry*)’ to ‘GSourceFunc’

  Either we should build it with -Wextra -Wno-cast-function-type in
  configure.ac or fix pointer to function for g++ > 8.1

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

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

[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running

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

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

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

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

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

Title:
  apport-autoreport.service fails if whoopsie isn't running

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  In Progress
Status in apport source package in Cosmic:
  Fix Released

Bug description:
  Impact
  --
  If automatic crash reporting is enabled and apport-autoreport.service starts 
before whoopsie on boot then crash reports that happened during shutdown or 
start up will not be automatically uploaded to the error tracker.

  Test Case
  -
  1) install apport-noui
  2) sudo service apport stop
  3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating 
the situation where whoopsie isn't running. I did this by copying lines 159,160 
to 161,162 and unindenting them. N.B. this isn't necessary if you are on a 
system where whoopsie is starting after apport.
  4) touch /var/crash/my.crash
  5) reboot
  5) run 'systemctl status apport-autoreport.service' and observe it failed 
because whoopsie isn't running

  When testing the proposed version of apport you'll want to revert the
  changes you made to whoopsie-upload-all. With the version of apport
  from -proposed you should no longer see the failure message for the
  apport-autoreport.service. The best test case is just having an
  affected system test the package from -proposed though.

  Regression Potential
  
  We are clearly fixing something that was a mistake in the original service so 
there is little chance for regression.

  

  ProblemType: BugDistroRelease: Ubuntu 18.10
  Package: apport 2.20.10-0ubuntu7
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportLog:

  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 18 11:48:00 2018
  InstallationDate: Installed on 2017-10-13 (308 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1799048] Re: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2019-02-07 Thread Gianfranco Costamagna

I would try an apt-get install --reinstall of the package.

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

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

Title:
  package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libffi package in Ubuntu:
  Incomplete

Bug description:
  1 st time system get restart

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libffi6:i386 3.2.1-8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Oct 20 23:57:30 2018
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  DuplicateSignature:
   package:libffi6:i386:3.2.1-8
   Setting up vlc-plugin-visualization:amd64 (3.0.3-1-1ubuntu1) ...
   dpkg: error processing package libffi6:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: libffi
  Title: package libffi6:i386 3.2.1-8 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

2019-02-07 Thread Corrado Mencar

Same issue with a fresh new install of Mint 19.1 (booted from USB) on a
Dell Inspiron 7778 and bluetooth mouse HP Z5000. No problems with Mint
18.3

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

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

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

[Touch-packages] [Bug 1813648] Re: error reports

*** This bug is a duplicate of bug 1787729 ***
https://bugs.launchpad.net/bugs/1787729

** This bug has been marked a duplicate of bug 1787729
   apport-autoreport.service fails if whoopsie isn't running

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

Title:
  error reports

Status in systemd package in Ubuntu:
  New

Bug description:
  Failed to start Process error reports when automatic reporting is
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.11
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Jan 28 21:34:51 2019
  InstallationDate: Installed on 2019-01-08 (20 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Dell System Inspiron N4110
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=UUID=ad0093a3-2f77-455d-ae55-b1d6d778d01d ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 05TM8C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Inspiron N4110
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1814235] Re: error reports

*** This bug is a duplicate of bug 1787729 ***
https://bugs.launchpad.net/bugs/1787729

** This bug has been marked a duplicate of bug 1813648
   error reports

** This bug is no longer a duplicate of bug 1813648
   error reports
** This bug has been marked a duplicate of bug 1787729
   apport-autoreport.service fails if whoopsie isn't running

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

Title:
  error reports

Status in systemd package in Ubuntu:
  New

Bug description:
  Failed to start Process error reports when automatic reporting is
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.11
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Feb  1 11:49:23 2019
  InstallationDate: Installed on 2019-01-08 (23 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Dell System Inspiron N4110
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=ad0093a3-2f77-455d-ae55-b1d6d778d01d ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 05TM8C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemInspironN4110:pvr:rvnDellInc.:rn05TM8C:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Inspiron N4110
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1815094] Re: [FTBFS] cast between incompatible function types from ‘bool ()(nux::TextEntry)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco)

2019-02-07 Thread Khurshid Alam

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

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

Title:
  [FTBFS] cast between incompatible function types from ‘bool
  (*)(nux::TextEntry*)’ to ‘GSourceFunc’  gcc >= 8.1 (Disco)

Status in nux package in Ubuntu:
  Confirmed

Bug description:
  In disco it doesn't compile. I get

  cast between incompatible function types from ‘bool
  (*)(nux::TextEntry*)’ to ‘GSourceFunc’

  Either we should build it with -Wextra -Wno-cast-function-type in
  configure.ac or fix pointer to function for g++ > 8.1

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

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

[Touch-packages] [Bug 1815094] [NEW] [FTBFS] cast between incompatible function types from ‘bool ()(nux::TextEntry)’ to ‘GSourceFunc’ gcc >= 8.1 (Disco)

2019-02-07 Thread Khurshid Alam

Public bug reported:

In disco it doesn't compile. I get

cast between incompatible function types from ‘bool
(*)(nux::TextEntry*)’ to ‘GSourceFunc’

Either we should build it with -Wextra -Wno-cast-function-type in
configure.ac or fix pointer to function for g++ > 8.1

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


** Tags: disco

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

Title:
  [FTBFS] cast between incompatible function types from ‘bool
  (*)(nux::TextEntry*)’ to ‘GSourceFunc’  gcc >= 8.1 (Disco)

Status in nux package in Ubuntu:
  New

Bug description:
  In disco it doesn't compile. I get

  cast between incompatible function types from ‘bool
  (*)(nux::TextEntry*)’ to ‘GSourceFunc’

  Either we should build it with -Wextra -Wno-cast-function-type in
  configure.ac or fix pointer to function for g++ > 8.1

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

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

[Touch-packages] [Bug 1805027] Re: systemd-resolved can't resolve Comcast mail server addresses

*** This bug is a duplicate of bug 1811471 ***
https://bugs.launchpad.net/bugs/1811471

I installed the version of systemd from -updates for Ubuntu 18.04 and
Ubuntu 18.10, with those versions of systemd I was no longer able to
recreate the problem regarding resolving imap.comcast.net. As such I am
marking this bug as a duplicate of bug 1811471.

** This bug has been marked a duplicate of bug 1811471
   local resolver stub fails to handle multiple TCP dns queries

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

Title:
  systemd-resolved can't resolve Comcast mail server addresses

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  1) Ubuntu release:  18.10
  2) systemd-resolved version: (Default latest version that comes with Ubuntu 
18.10)
  3) Expected behavior: Comcast's POP3 mail server addresses to be resolved to 
IP addresses
  4) Actual behavior:  Comcast's POP3 mail server addresses can't be resolved 
to IP addresses

  Starting on Monday, November 19, 2018, Comcast made a DNS change
  related to its POP3 mail servers (mail.comcast.net and
  pop3.comcast.net) that prevent resolved from being able to resolve
  those domains into IP addresses.  When I try to ping either host
  (mail.comcast.net or pop2.comcast.net), I get this error:

  tom@deathstar:~$ ping mail.comcast.net
  ping: mail.comcast.net: Name or service not known
  tom@deathstar:~$

  When I manually lookup up the domain, I get these results:

  tom@deathstar:~$ nslookup mail.comcast.net
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  mail.comcast.net  canonical name = imap.ge.xfinity.com.
  Name: imap.ge.xfinity.com
  Address: 96.118.242.209
  Name: imap.ge.xfinity.com
  Address: 96.118.242.197
  Name: imap.ge.xfinity.com
  Address: 96.118.242.233
  Name: imap.ge.xfinity.com
  Address: 96.118.242.225
  Name: imap.ge.xfinity.com
  Address: 96.118.242.226
  Name: imap.ge.xfinity.com
  Address: 96.118.242.217
  Name: imap.ge.xfinity.com
  Address: 96.118.242.208
  Name: imap.ge.xfinity.com
  Address: 96.118.242.230
  Name: imap.ge.xfinity.com
  Address: 96.118.242.232
  Name: imap.ge.xfinity.com
  Address: 96.118.242.218
  Name: imap.ge.xfinity.com
  Address: 96.118.242.211
  Name: imap.ge.xfinity.com
  Address: 96.118.242.242
  Name: imap.ge.xfinity.com
  Address: 96.118.242.221
  Name: imap.ge.xfinity.com
  Address: 96.118.242.196
  Name: imap.ge.xfinity.com
  Address: 96.118.208.40
  Name: imap.ge.xfinity.com
  Address: 96.118.208.99
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee8:4f07
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe7d:1b0c
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe25:5ae5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fef6:babc
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe87:c172
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee6:7a57
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe0f:a4a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:2:f816:3eff:fec7:cb93
  Name: imap.ge.xfinity.com
  Address: 2001:558:fee2:1000:f816:3eff:fe42:4f14
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe33:9aaa
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:feb2:8c0d
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fef1:25a5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:febd:320a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe36:aba3
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe3f:76f2
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe45:1d1e

  tom@deathstar:~$ dig mail.comcast.net

  ; <<>> DiG 9.11.4-3ubuntu5-Ubuntu <<>> mail.comcast.net
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mail.comcast.net.IN  A

  ;; ANSWER SECTION:
  mail.comcast.net. 15  IN  CNAME   imap.ge.xfinity.com.
  imap.ge.xfinity.com.  12  IN  A   96.117.3.119
  imap.ge.xfinity.com.  12  IN  A   96.117.3.96
  imap.ge.xfinity.com.  12  IN  A   96.117.3.143
  imap.ge.xfinity.com.  12  IN  A   96.117.3.145
  imap.ge.xfinity.com.  12  IN  A   96.117.3.129
  imap.ge.xfinity.com.  12  IN  A   96.117.3.148
  imap.ge.xfinity.com.  12  IN  A   96.117.3.201
  imap.ge.xfinity.com.  12  IN  A   96.117.3.136
  imap.ge.xfinity.com.  12  IN  A   96.118.133.238
  imap.ge.xfinity.com.  12  IN  A   96.117.3.128
  imap.ge.xfinity.com.  12  IN

[Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100

Thanks for the investigation work, I emailed the Ubuntu devel list about 
changing the default, let's see how the discussion goes
https://lists.ubuntu.com/archives/ubuntu-devel/2019-February/040588.html

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

Title:
  Wired interface gets impossibly high metric 20100

Status in network-manager package in Ubuntu:
  New

Bug description:
  Actually this might be a heisenbug. I've had an issue with this all
  morning since network-manager got an update this morning, but just now
  *while this bug was being submitted* it decided to correct itself.

  What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
  a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the
  network-manager update I noticed everything was slower than I was used
  to, and in gnome-shell the network icon showing was the WiFi one, not
  the wired one.

  Looking at the output of route, or route -n for simplicity, I would
  see this:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 
enp63s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So the metric on the default route on enp63s0 had 20,000 mysteriously
  added to it, which would obviously make it extremely low-priority. The
  system was choosing the wifi connection instead, which isn't that
  great in my office, hence observable slowness.

  Now, this morning, this seemed to be the sticky situation. It didn't
  show any sign of changing, whatever I did, after restarts of network-
  manager, undock/redock, reboots, etc. I could change it manually with
  ifmetric (and it would work), but that was about it.

  I would have reported the bug then, but I had to go out. When I got
  back I plugged in and initially saw the same thing again (that's where
  the above snippet was pasted from). But *while* the ubuntu-bug
  network-manager command was running, I noticed the gnome-shell network
  icon switch to wired, checked again, and saw:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG10000 
enp63s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So now the wifi connection has 20,000 added to it, which may still be
  wrong? But I wouldn't otherwise have noticed it because the system is
  again *behaving* as expected.

  This all seemed to happen after the network-manager upgrade (from
  1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
  metric+20,000 values were present before then, because I didn't have
  any cause to go looking at it, it always just worked. Could it be some
  issue with how the newer network-manager, or one of its associated
  packages, is figuring out the metrics on new connections? Like it's
  running some new heuristic to determine which one should really be the
  preferred? If it's like it was just now, when it fixed itself after a
  minute or so, that's not really a problem, but if it's like it was
  this morning when it just seemed to be stuck with the ethernet
  connection at 20100, it is.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 13:15:06 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true

[Touch-packages] [Bug 311029] Re: curl and pycurl is not compiled with sftp support

2019-02-07 Thread Alexander Blinne

Please, please, please backport this fix to bionic!

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

Title:
  curl and pycurl is not compiled with sftp support

Status in curl package in Ubuntu:
  Fix Released
Status in curl package in Debian:
  Fix Released

Bug description:
  Binary package hint: curl

  Running curl --version, I see:
  Protocols: tftp ftp telnet dict ldap ldaps http file https ftps
  SFTP is obviously missing, although it is supported by curl upstream
  The SFTP is also missing from python-pycurl, probably because libcurl doesn't 
have it.

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

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

[Touch-packages] [Bug 1807286] Re: systemd SEGV freezing on install of virtualbox

2019-02-07 Thread Gianfranco Costamagna

should be fixed in the systemd in disco

** Changed in: virtualbox (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  systemd SEGV freezing on install of virtualbox

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released

Bug description:
  most of the information has been reported at VBox here:
  https://forums.virtualbox.org/viewtopic.php?f=7=90643

  when installing VBox this happens:
  _
  sudo ./VirtualBox-5.2.23-126798-Linux_amd64.run
  [sudo] password for kinghat: 
  Verifying archive integrity... All good.
  Uncompressing VirtualBox for Linux installation.
  VirtualBox Version 5.2.23 r126798 (2018-11-20T16:12:47Z) installer
  Installing VirtualBox to /opt/VirtualBox
  Python found: python, installing bindings...

  Broadcast message from systemd-journald@kinghat-kubuntu (Thu
  2018-12-06 16:33:50 CST):

  systemd[1]: Caught , dumped core as pid 5201.

  
  Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 
16:33:50 CST):

  systemd[1]: Freezing execution.

  Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
  Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
  Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
  Failed to enable unit: Connection timed out
  Failed to start vboxdrv.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
  See system logs and 'systemctl status vboxdrv.service' for details.
  Failed to start vboxballoonctrl-service.service: Connection timed out
  See system logs and 'systemctl status vboxballoonctrl-service.service' for 
details.
  Failed to start vboxautostart-service.service: Connection timed out
  See system logs and 'systemctl status vboxautostart-service.service' for 
details.
  Failed to start vboxweb-service.service: Connection timed out
  See system logs and 'systemctl status vboxweb-service.service' for details.

  VirtualBox has been installed successfully.

  You will find useful information about using VirtualBox in the user manual
/opt/VirtualBox/UserManual.pdf
  and in the user FAQ
http://www.virtualbox.org/wiki/User_FAQ

  We hope that you enjoy using VirtualBox.
  _

  VB then starts fine. after reboot none of the VMs fail to launch. ive
  had weird install issues with VBox on 18.10 for many months.

  Description:Ubuntu 18.10
  Release:18.10

  VirtualBox-5.2.23-126798-Linux_amd64.run

  http://paste.debian.net/hidden/ee22b12a/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: virtualbox (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Dec  6 17:21:15 2018
  InstallationDate: Installed on 2018-08-20 (108 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (57 days ago)

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

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

[Touch-packages] [Bug 1814109] Re: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu

** Also affects: libarchive (Ubuntu Disco)
   Importance: High
   Status: Triaged

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

Title:
  Nautilus corrupts 7z archive files when extracting via 'Extract here'
  context menu

Status in libarchive package in Ubuntu:
  Triaged
Status in libarchive source package in Disco:
  Triaged

Bug description:
  Nautilus corrupts 7z archive files when extracting via 'Extract here' context 
menu.
  Extractions completes without errors, but the files are corrupted (mangled 
bytes, wrong size).
  This does happen only when extracting with 'Extract here' context menu action.
  Using 7z or p7zip via command line or opening the archive via file-roller and 
then drag
  single files or directory to a folder works well.
  This only happens with this particular archive, others 7z archives are 
extracted correctly.

  Original 7z archive:
  https://drive.google.com/open?id=1eZJm1ST3P-52tFSvHXbUn9-WSe_B3Ag9

  Re-zipped corrupted archive here:
  https://drive.google.com/open?id=1N--99RuWdmg6oUGrAz7pLoRpuJOIBEE5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 15:03:45 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'222'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1133x703+51+273'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-05-31 (245 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (103 days ago)
  usr_lib_nautilus:

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

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

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

Tested 1.1ubuntu1.18.04.7~16.04.1. Candidates are adjusted and u-u does
not crash:

root@x-uu-ref:~# 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.1 all  automatic 
installation of security upgrades
root@x-uu-ref:~# grep invoke /var/lib/dpkg/info/unattended-upgrades.prerm
root@x-uu-ref:~# unattended-upgrade --dry-run --verbose --debug
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
Using 
(^linux-image|^linux-headers|^linux-image-extra|^linux-modules|^linux-modules-extra|^linux-signed-image|^kfreebsd-image|^kfreebsd-headers|^gnumach-image|^.*-modules|^.*-kernel|^linux-backports-modules-.*|^linux-modules-.*|^linux-tools|^linux-cloud-tools)
 regexp to find kernel packages
Using 
(^linux-image.*4.19.0-12-generic|^linux-headers.*4.19.0-12-generic|^linux-image-extra.*4.19.0-12-generic|^linux-modules.*4.19.0-12-generic|^linux-modules-extra.*4.19.0-12-generic|^linux-signed-image.*4.19.0-12-generic|^kfreebsd-image.*4.19.0-12-generic|^kfreebsd-headers.*4.19.0-12-generic|^gnumach-image.*4.19.0-12-generic|4.19.0-12-generic.*-modules|4.19.0-12-generic.*-kernel|^linux-backports-modules-.*.*4.19.0-12-generic|^linux-modules-.*.*4.19.0-12-generic|^linux-tools.*4.19.0-12-generic|^linux-cloud-tools.*4.19.0-12-generic)
 regexp to find running kernel packages
Checking: cloud-init ([])
adjusting candidate version: cloud-init=0.7.7~bzr1212-0ubuntu1
Checking: kmod ([])
adjusting candidate version: kmod=22-1ubuntu5
Checking: libc-bin ([])
adjusting candidate version: libc-bin=2.23-0ubuntu10
Checking: libc6 ([])
adjusting candidate version: libc6=2.23-0ubuntu10
Checking: libkmod2 ([])
adjusting candidate version: libkmod2=22-1ubuntu5
Checking: locales ([])
adjusting candidate version: locales=2.23-0ubuntu10
Checking: multiarch-support ([])
adjusting candidate version: multiarch-support=2.23-0ubuntu10
Checking: python-apt-common ([])
adjusting candidate version: python-apt-common=1.1.0~beta1build1
Checking: snapd ([])
adjusting candidate version: snapd=2.0.2
Checking: ubuntu-core-launcher ([])
adjusting candidate version: ubuntu-core-launcher=1.0.27.1
pkgs that look like they should be upgraded: 
Fetched 0 B in 0s (0 B/s)   
  
fetch.run() result: 0
blacklist: []
whitelist: []
No packages found that can be upgraded unattended and no pending auto-removals
root@x-uu-ref:~#

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

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

   * Run sudo unattended-upgrade --dry-run --verbose --debug
   * Observe lines "adjusting

[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

2019-02-07 Thread Dmitry Shachnev

That definitely is not related to my changes. However, it could be
caused by the fact that qtbase is rebuilt against new OpenSSL or
something like that. I found a similar bug in Debian:
https://bugs.debian.org/907339.

Let’s see if retrying the tests against kdeconnect 1.3.3 (which just
migrated to -updates) fixes it.

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

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  Confirmed
Status in qtdeclarative-opensource-src source package in Cosmic:
  Confirmed
Status in qttools-opensource-src source package in Cosmic:
  Confirmed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

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

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

[Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100

2019-02-07 Thread Rachel Greenham

Follow up comment on the upstream bug pointed to a commit where it
suggests the rp_filter default should actually now be 2 rather than 1:
https://github.com/systemd/systemd/commit/230450d4e4f1f5fc9fa4295ed9185eea5b6ea16e

Think at this point I need to just let you guys talk amongst yourself.
:-) For me, my fix for now is to uninstall the connectivity-check
package, which disables the functionality. I'm not going to mess about
changing procps defaults.

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

Title:
  Wired interface gets impossibly high metric 20100

Status in network-manager package in Ubuntu:
  New

Bug description:
  Actually this might be a heisenbug. I've had an issue with this all
  morning since network-manager got an update this morning, but just now
  *while this bug was being submitted* it decided to correct itself.

  What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
  a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the
  network-manager update I noticed everything was slower than I was used
  to, and in gnome-shell the network icon showing was the WiFi one, not
  the wired one.

  Looking at the output of route, or route -n for simplicity, I would
  see this:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 
enp63s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So the metric on the default route on enp63s0 had 20,000 mysteriously
  added to it, which would obviously make it extremely low-priority. The
  system was choosing the wifi connection instead, which isn't that
  great in my office, hence observable slowness.

  Now, this morning, this seemed to be the sticky situation. It didn't
  show any sign of changing, whatever I did, after restarts of network-
  manager, undock/redock, reboots, etc. I could change it manually with
  ifmetric (and it would work), but that was about it.

  I would have reported the bug then, but I had to go out. When I got
  back I plugged in and initially saw the same thing again (that's where
  the above snippet was pasted from). But *while* the ubuntu-bug
  network-manager command was running, I noticed the gnome-shell network
  icon switch to wired, checked again, and saw:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG10000 
enp63s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So now the wifi connection has 20,000 added to it, which may still be
  wrong? But I wouldn't otherwise have noticed it because the system is
  again *behaving* as expected.

  This all seemed to happen after the network-manager upgrade (from
  1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
  metric+20,000 values were present before then, because I didn't have
  any cause to go looking at it, it always just worked. Could it be some
  issue with how the newer network-manager, or one of its associated
  packages, is figuring out the metrics on new connections? Like it's
  running some new heuristic to determine which one should really be the
  preferred? If it's like it was just now, when it fixed itself after a
  minute or so, that's not really a problem, but if it's like it was
  this morning when it just seemed to be stuck with the ethernet
  connection at 20100, it is.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  1 13:15:06 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000

[Touch-packages] [Bug 1778800] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

Tested 1.1ubuntu1.18.04.7~16.04.1:

root@x-uu-ref:~# 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.1 all  automatic 
installation of security upgrades
root@x-uu-ref:~# grep invoke /var/lib/dpkg/info/unattended-upgrades.prerm
root@x-uu-ref:~# 


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

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

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

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

Bug description:
  [Impact]

   * Upgrading unattended-upgrades during shutdown fails due to postinst
  trying to start the unattended-upgrades service. This can break
  installation of other security-fixes, too.

   * Unattended-upgrades is regularly SRU-d and this bug can break
  installing other important updates.

   * The fix is not starting/stopping the init.d script in postinst
  which is not useful during package installation anyway.

  [Test Case]

   * Check prerm that invoke-rc.d is not called:
  --- prerm.old 2018-06-07 01:30:55.0 +0200
  +++ /var/lib/dpkg/info/unattended-upgrades.prerm  2018-07-12 
14:04:12.294677476 +0200
  @@ -40,11 +40,6 @@
   # dh_installdeb will replace this with shell code automatically
   # generated by other debhelper scripts.
   
  -# Automatically added by dh_installinit/11.1.6ubuntu2
  -if [ -x "/etc/init.d/unattended-upgrades" ] && [ "$1" = remove ]; then
  - invoke-rc.d unattended-upgrades stop || exit 1
  -fi
  -# End automatically added section
   
   
   exit 0

  
   * Check postinst that invoke-rc.d is not called:
  --- postinst.old  2018-06-07 01:30:55.0 +0200
  +++ /var/lib/dpkg/info/unattended-upgrades.postinst   2018-07-12 
14:04:12.242676369 +0200
  @@ -108,8 +108,7 @@
   # Automatically added by dh_installinit/11.1.6ubuntu2
   if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -x "/etc/init.d/unattended-upgrades" ]; then
  - update-rc.d unattended-upgrades defaults >/dev/null
  - invoke-rc.d unattended-upgrades start || exit 1
  + update-rc.d unattended-upgrades defaults >/dev/null || exit 1
fi
   fi
   # End automatically added section

  
  [Regression Potential] 

  * Unattended-upgrades.service may fail to start upon first
  installation. This is not an issue in default configuration since apt
  starts u-u based on timers and stops it gracefully upon shutdown.

  [Original Bug Text]

  update did not install.
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage notifications about this bug go to:

[Touch-packages] [Bug 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install

The problem still exists in 1.1ubuntu1.18.04.7~16.04.1 (and
1.1ubuntu1.18.04.8):

https://errors.ubuntu.com/problem/dc828b331e8948ac9875455b6f5653eeaf9f1022

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

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: Fix Committed => 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/1779157

Title:
  /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-
  upgrade@1927:main:do_install

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

Bug description:
  [Impact]

   * Unattended-upgrades can be crashing when packages are marked for removal 
after collecting upgradable packages.
   * The fix clear the cache when it may be in an invalid state to lose 
markings.

  [Test Case]

   * Observe
  https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2
  not occurring in fixed versions.

  [Regression Potential]

   * The extra cache.clear() can take extra CPU time when invoked
  needlessly or can cause skipping updates when invoked at the wrong
  time. However the fix received extensive testing in newer releases
  making unnoticed regressions unlikely to surface.

  [Original Bug Text]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 
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/.

  Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1782, in main
  logfile_dpkg)
    File "/usr/bin/unattended-upgrade", line 1057, in do_install
  "removal:%s" % "".join([pkg.name for pkg in marked_delete]))
  AssertionError: Internal error. The following packages are marked for 
removal:linux-headers-4.15.0-20-generic

  Also seen as:
  https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5

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

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

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

2019-02-07 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2019-02-07 09:42 EDT---
@Canonical. any update available here? Thx

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

Title:
  Fix for openssl 1.0.2 backport

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

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

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

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

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

[Touch-packages] [Bug 1711805] Re: [X450CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

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

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

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

Title:
  [X450CA, Realtek ALC270, Black Headphone Out, Left] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  no sound from headphone

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: alsa-base 1.0.25+dfsg-0ubuntu5 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rr 1333 F...m pulseaudio
   /dev/snd/controlC0:  rr 1333 F pulseaudio
  CurrentDesktop: Pantheon
  Date: Sat Aug 19 14:18:48 2017
  InstallationDate: Installed on 2017-08-16 (3 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rr 1333 F...m pulseaudio
   /dev/snd/controlC0:  rr 1333 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [X450CA, Realtek ALC270, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X450CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X450CA
  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.:bvrX450CA.208:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnX450CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X450CA
  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/alsa-driver/+bug/1711805/+subscriptions

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

[Touch-packages] [Bug 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

The fix is incomplete in Xenail the same way as it is incomplete in Bionic.
Tested version: 1.1ubuntu1.18.04.7~16.04.1

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

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Fix Released => 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/1781176

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

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

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * Listing the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
    apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
    liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
    python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
    unattended-upgrades update-manager-core update-notifier-common
  27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 24.1 MB of archives.
  After this operation, 1454 kB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.

  * blacklist ebtables, set up emails from u-u, then run u-u again:
  $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
  $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: ebtables
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Packages that will be upgraded:

  * Observe ebtables listed as being kept back and having upgradable origin 
with buggy u-u:
  $ sudo cat /var/mail/mail
  ...
  Packages with upgradable origin but kept back:
   ebtables=20
  ...

  * Upgrade u-u to a fixed version and run it, observing ebtables to be
  not listed as having upgradable origin

  [Regression Potential]

   * Regressions may make packages incorrectly missing from u-u's
  report, but the autopkgtests also cover that to some extent.

  [Other Info]

   * Original report: https://github.com/mvo5/unattended-
  upgrades/issues/116

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

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

[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs

2019-02-07 Thread Jurit

Resolved, but I dont know how...

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

Title:
  systemd-tmpfiles-setup.service fails on btrfs

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

Bug description:
  [Impact]

   * Last security update introduced a regression on btrfs based systems, 
causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded 
machines.
   * Cherrypick upstream fixes to resolve this.

  [Test Case]

   * Install VM using btrfs for /
   * Boot, check that systemd-tmpfiles-setup.service is started successfully 
with:
  $ systemctl status systemd-tmpfiles-setup.service

  [Regression Potential]

   * btrfs fd doesn't support the set of flags that systemd used, with
  this patch, a compat set of flags is set instead, thus resolving the
  introduced regression. The worst case scenario is that creating
  subvolumes/directories is still broken (as in, the current status
  quo).

  [Other Info]
   
   * Example bad output

  
  After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails 
with:

  Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and 
Directories...
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/var": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/home": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory 
or subvolume "/srv": Bad file descriptor
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed 
with result 'exit-code'.
  Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files 
and Directories.

  This happens on btrfs root filesystems in real hardware and on our
  virtualized servers as well. 237-3ubuntu10.6 didnt show this errors
  and going back to 237-3ubuntu10 removes them as well.

  # lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  # apt-cache policy systemd
  systemd:
    Installiert:   237-3ubuntu10.9
    Installationskandidat: 237-3ubuntu10.9
    Versionstabelle:
   *** 237-3ubuntu10.9 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1396787] Re: checking trust of archives eats a lot of cpu

Tested with 1.1ubuntu1.18.04.7~16.04.1:

On the autopkgtest infrastructure u-u runs for 20s when all packages are
installed from xenial-security but none from xenial-updates:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unattended-upgrades/20181213_182038_2962e@/log.gz
...
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
Packages that will be upgraded: 
19.18user 1.17system 0:20.53elapsed 99%CPU (0avgtext+0avgdata 77720maxresident)k
0inputs+123512outputs (0major+38986minor)pagefaults 0swaps
...

On a 2012 MacBook Air inside a KVM qemu vm autopkgtest runner it is ~8s:
...
adt-2.log-Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
adt-2.log-Packages that will be upgraded: 
adt-2.log:7.64user 0.31system 0:08.00elapsed 99%CPU (0avgtext+0avgdata 
76516maxresident)k
..

This is basically the same speed as with 0.90ubuntu0.10.
There is a 12% speed regression when testing in qemu with kvm on a 19.04 host:

...
adt-1549534420.log-Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial
adt-1549534420.log-Packages that will be upgraded: 
adt-1549534420.log:6.72user 0.30system 0:07.07elapsed 99%CPU (0avgtext+0avgdata 
77812maxresident)k
...
vs.
..
adt-2.log-Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
adt-2.log-Packages that will be upgraded: 
adt-2.log:7.64user 0.31system 0:08.00elapsed 99%CPU (0avgtext+0avgdata 
76516maxresident)k
...

Or a 24% speedup with a smaller set of upgradable packages measured in
two 16.04 lxc containers running on the same 19.04 development system:

ii  unattended-upgrades 0.90ubuntu0.10 all  automatic
installation of security upgrades

# for i in $(seq 5); do time unattended-upgrade --dry-run; done

real0m4.326s
user0m4.245s
sys 0m0.043s

real0m4.309s
user0m4.239s
sys 0m0.070s
...
# apt list --upgradable 
Listing... Done
cloud-init/xenial-proposed 18.5-21-g8ee294d5-0ubuntu1~16.04.1 all [upgradable 
from: 18.4-0ubuntu1~16.04.2]
kmod/xenial-proposed 22-1ubuntu5.2 amd64 [upgradable from: 22-1ubuntu5.1]
libc-bin/xenial-proposed 2.23-0ubuntu11 amd64 [upgradable from: 2.23-0ubuntu10]
libc6/xenial-proposed 2.23-0ubuntu11 amd64 [upgradable from: 2.23-0ubuntu10]
libkmod2/xenial-proposed 22-1ubuntu5.2 amd64 [upgradable from: 22-1ubuntu5.1]
locales/xenial-proposed 2.23-0ubuntu11 all [upgradable from: 2.23-0ubuntu10]
multiarch-support/xenial-proposed 2.23-0ubuntu11 amd64 [upgradable from: 
2.23-0ubuntu10]
python-apt-common/xenial-proposed 1.1.0~beta1ubuntu0.16.04.3 all [upgradable 
from: 1.1.0~beta1ubuntu0.16.04.2]
python3-apt/xenial-proposed 1.1.0~beta1ubuntu0.16.04.3 amd64 [upgradable from: 
1.1.0~beta1ubuntu0.16.04.2]
snapd/xenial-proposed 2.37.1 amd64 [upgradable from: 2.34.2]
ubuntu-core-launcher/xenial-proposed 2.37.1 amd64 [upgradable from: 2.34.2]
unattended-upgrades/xenial-proposed 1.1ubuntu1.18.04.7~16.04.1 all [upgradable 
from: 0.90ubuntu0.10]
#

vs.

ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1 all
automatic installation of security upgrades

# for i in $(seq 5); do time unattended-upgrade --dry-run; done

real0m3.269s
user0m3.194s
sys 0m0.076s

real0m3.277s
user0m3.135s
sys 0m0.115s
...
root@x-uu-ref:~# apt list --upgradable 
Listing... Done
cloud-init/xenial-proposed 18.5-21-g8ee294d5-0ubuntu1~16.04.1 all [upgradable 
from: 18.4-0ubuntu1~16.04.2]
kmod/xenial-proposed 22-1ubuntu5.2 amd64 [upgradable from: 22-1ubuntu5.1]
libc-bin/xenial-proposed 2.23-0ubuntu11 amd64 [upgradable from: 2.23-0ubuntu10]
libc6/xenial-proposed 2.23-0ubuntu11 amd64 [upgradable from: 2.23-0ubuntu10]
libkmod2/xenial-proposed 22-1ubuntu5.2 amd64 [upgradable from: 22-1ubuntu5.1]
locales/xenial-proposed 2.23-0ubuntu11 all [upgradable from: 2.23-0ubuntu10]
multiarch-support/xenial-proposed 2.23-0ubuntu11 amd64 [upgradable from: 
2.23-0ubuntu10]
python-apt-common/xenial-proposed 1.1.0~beta1ubuntu0.16.04.3 all [upgradable 
from: 1.1.0~beta1ubuntu0.16.04.2]
snapd/xenial-proposed 2.37.1 amd64 [upgradable from: 2.34.2]
ubuntu-core-launcher/xenial-proposed 2.37.1 amd64 [upgradable from: 2.34.2]
root@x-uu-ref:~# 



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

Title:
  checking trust of archives eats a lot of cpu

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

Bug description:
  [Impact]

   * Unattended-upgrades consumes tens of seconds or even minutes of CPU
  time

[Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100

2019-02-07 Thread Rachel Greenham

Reporting back on this:

The opinion there seems to be that the problem is down to the sys
net.ipv4.conf.*.rp_filter values being set to 1 instead of defaulting to
0. This is done in the procps package, and I'm guessing is the way it is
as a protection against IP spoofing. kernel doc page I was pointed to
says:

Current recommended practice in RFC3704 is to enable strict mode
to prevent IP spoofing from DDos attacks. If using asymmetric routing
or other complicated routing, then loose mode is recommended.

The max value from conf/{all,interface}/rp_filter is used
when doing source validation on the {interface}.

Default value is 0. Note that some distributions enable it
in startup scripts.

Presumably Ubuntu enables by default (I can see it does, in a file in
the procps package) and Red Hat, where it seems the NetworkManager
maintainers sit, does not.

This is going to have to be argued out between procps and network-
manager maintainers I guess. You can have IP spoofing protection or you
can have connectivity checking. Choose one, or argue who should fix it.
:-) Personally, at least for now, my solution is to remove the
connectivity-check package, which was presumably brought in by
something, and keep the procps defaults.

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

Title:
  Wired interface gets impossibly high metric 20100

Status in network-manager package in Ubuntu:
  New

Bug description:
  Actually this might be a heisenbug. I've had an issue with this all
  morning since network-manager got an update this morning, but just now
  *while this bug was being submitted* it decided to correct itself.

  What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
  a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the
  network-manager update I noticed everything was slower than I was used
  to, and in gnome-shell the network icon showing was the WiFi one, not
  the wired one.

  Looking at the output of route, or route -n for simplicity, I would
  see this:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG60000 wlp2s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20100  00 
enp63s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So the metric on the default route on enp63s0 had 20,000 mysteriously
  added to it, which would obviously make it extremely low-priority. The
  system was choosing the wifi connection instead, which isn't that
  great in my office, hence observable slowness.

  Now, this morning, this seemed to be the sticky situation. It didn't
  show any sign of changing, whatever I did, after restarts of network-
  manager, undock/redock, reboots, etc. I could change it manually with
  ifmetric (and it would work), but that was about it.

  I would have reported the bug then, but I had to go out. When I got
  back I plugged in and initially saw the same thing again (that's where
  the above snippet was pasted from). But *while* the ubuntu-bug
  network-manager command was running, I noticed the gnome-shell network
  icon switch to wired, checked again, and saw:

  rachel@rainbow:~$ route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.254   0.0.0.0 UG10000 
enp63s0
  0.0.0.0 192.168.1.254   0.0.0.0 UG20600  00 wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 wlp2s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 10000 
enp63s0
  192.168.1.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  So now the wifi connection has 20,000 added to it, which may still be
  wrong? But I wouldn't otherwise have noticed it because the system is
  again *behaving* as expected.

  This all seemed to happen after the network-manager upgrade (from
  1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these
  metric+20,000 values were present before then, because I didn't have
  any cause to go looking at it, it always just worked. Could it be some
  issue with how the newer network-manager, or one of its associated
  packages, is figuring out the metrics on new connections? Like it's
  running some new heuristic to determine which one should really be the
  preferred? If it's like it was just now, when it fixed itself after a
  minute or so, that's not really a problem, but if it's like it was
  this morning

[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

2019-02-07 Thread Trinché Kévin

Same here, Debian 9 Stretch, Sony WH1000-XM3.

I have to disconnect and reconnect my Headset manually from UI in order to get 
the sound of my music.
Actually the issue comes when the Headset connects automatically.

Maybe someone competent could tell us where it is ? There's not update
since a while...

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1815045] [NEW] Failed unmounting /var when it is a separate filesystem

2019-02-07 Thread André Burkhardt

Public bug reported:

In a fresh install of Ubuntu Server 18.04.1 LTS with the /var-Filesystem
on a separate partition (LVM), there are Errors on shutdown/reboot
(Failed unmounting /var).

1) The release
Release: Ubuntu 18.04.1 LTS

2) The version
Version:apt-cache policy systemd
systemd:  Installed: 237-3ubuntu10.12
  Candidate: 237-3ubuntu10.12

3) What you expected to happen
Clean unmount of /var Filesystem without Failure

4) What happened instead
Console output on shutdown/reboot
[...]
[  OK  ] Stopped Flush Journal to Persistent Storage.
[  OK  ] Stopped target Local File Systems.
 Unmounting /boot...
 Unmounting /var...
 Unmounting /run/user/1000...
[FAILED] Failed unmounting /var.
[  OK  ] Stopped File System Check on /dev/mapper/vg_system-lv_var.
[  OK  ] Unmounted /run/user/1000
[...]

Extract from journalctl
[...]
Feb 07 13:13:31 x systemd[1]: Stopped Flush Journal to Persistent Storage.
Feb 07 13:13:31 x systemd[1]: Stopped target Local File Systems.
Feb 07 13:13:31 x systemd[1]: Unmounting /boot...
Feb 07 13:13:31 x systemd[1]: Unmounting /var...
Feb 07 13:13:31 x systemd[1]: Unmounting /run/user/1000...
Feb 07 13:13:31 x umount[1775]: umount: /var: target is busy.
Feb 07 13:13:31 x systemd[1]: var.mount: Mount process exited, code=exited 
status=32
Feb 07 13:13:31 x systemd[1]: Failed unmounting /var.
Feb 07 13:13:31 x systemd[1]: Stopped File System Check on 
/dev/mapper/vg_system-lv_var.
Feb 07 13:13:31 x systemd[1]: Unmounted /run/user/1000.
[...]

Applying the changes described here:

https://github.com/systemd/systemd/issues/867#issuecomment-250202183

let the Error-Messages go away. But are there any side-effects?

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

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

Title:
  Failed unmounting /var when it is a separate filesystem

Status in systemd package in Ubuntu:
  New

Bug description:
  In a fresh install of Ubuntu Server 18.04.1 LTS with the /var-
  Filesystem on a separate partition (LVM), there are Errors on
  shutdown/reboot (Failed unmounting /var).

  1) The release
  Release: Ubuntu 18.04.1 LTS

  2) The version
  Version:apt-cache policy systemd
  systemd:  Installed: 237-3ubuntu10.12
Candidate: 237-3ubuntu10.12

  3) What you expected to happen
  Clean unmount of /var Filesystem without Failure

  4) What happened instead
  Console output on shutdown/reboot
  [...]
  [  OK  ] Stopped Flush Journal to Persistent Storage.
  [  OK  ] Stopped target Local File Systems.
   Unmounting /boot...
   Unmounting /var...
   Unmounting /run/user/1000...
  [FAILED] Failed unmounting /var.
  [  OK  ] Stopped File System Check on /dev/mapper/vg_system-lv_var.
  [  OK  ] Unmounted /run/user/1000
  [...]

  Extract from journalctl
  [...]
  Feb 07 13:13:31 x systemd[1]: Stopped Flush Journal to Persistent Storage.
  Feb 07 13:13:31 x systemd[1]: Stopped target Local File Systems.
  Feb 07 13:13:31 x systemd[1]: Unmounting /boot...
  Feb 07 13:13:31 x systemd[1]: Unmounting /var...
  Feb 07 13:13:31 x systemd[1]: Unmounting /run/user/1000...
  Feb 07 13:13:31 x umount[1775]: umount: /var: target is busy.
  Feb 07 13:13:31 x systemd[1]: var.mount: Mount process exited, 
code=exited status=32
  Feb 07 13:13:31 x systemd[1]: Failed unmounting /var.
  Feb 07 13:13:31 x systemd[1]: Stopped File System Check on 
/dev/mapper/vg_system-lv_var.
  Feb 07 13:13:31 x systemd[1]: Unmounted /run/user/1000.
  [...]

  Applying the changes described here:

  https://github.com/systemd/systemd/issues/867#issuecomment-250202183

  let the Error-Messages go away. But are there any side-effects?

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

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

[Touch-packages] [Bug 1781586] Re: Skip rebuilding python-apt in upgrade autopkgtests

Tested with 1.1ubuntu1.18.04.7~16.04.1:

Python-apt is not rebuilt in the test:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20181213_182038_2962e@/log.gz


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

Title:
  Skip rebuilding python-apt in upgrade autopkgtests

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

Bug description:
  [Impact]

   * Python-apt has a new build dependency making the rebuilding as is
  failing and the reference handling issue is worked around in
  unattended-upgrades already.

   * Table updates of python-apt may make u-u autopkgtest fail without
  the u-u package having any problem when it is installed.

  
  [Test Case]

   * Check upgrade-all-security autopkgtest output, it should not
  rebuild the python-apt package.

  [Regression Potential]

   * Autopkgtest may fail due running it with not rebuilt python-apt.
  This problem can be caught easily when testing the package.

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

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

[Touch-packages] [Bug 1781446] Re: Autopkgtest upgrade-all-security is failing due to apt printing to stderr in Bionic

Tested with 1.1ubuntu1.18.04.7~16.04.1:

Autopkgtest is passing:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20181213_182038_2962e@/log.gz

...
autopkgtest [18:20:27]: test upgrade-between-snapshots:  - - - - - - - - - - 
results - - - - - - - - - -
autopkgtest [18:20:27]:  summary
run-testsPASS
test-systemd.py  PASS
upgrade-all-security PASS
upgrade-between-snapshots PASS
...

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

Title:
  Autopkgtest upgrade-all-security is failing due to apt printing to
  stderr in Bionic

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

Bug description:
  [Impact] 
   * The following error can be seen in autopkgtest, holding back u-u from 
migration:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180712_151033_c44d8@/log.gz
 :
  ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ...
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  Reading package lists...
  ...
  autopkgtest [14:17:33]: test upgrade-all-security:  - - - - - - - - - - 
results - - - - - - - - - -
  upgrade-all-security FAIL stderr: W: APT had planned for dpkg to do more than 
it reported back (2370 vs 2372).
  autopkgtest [14:17:34]: test upgrade-all-security:  - - - - - - - - - - 
stderr - - - - - - - - - -
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  autopkgtest [14:17:34]: test upgrade-between-snapshots: preparing testbed
  ...

  [Test Case]

   * upgrade-all-security autopkgtest

  [Regression Potential]

   * Valid errors manifesting themselves only as output from stderr may
  not fail the autopkgtest.

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

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

[Touch-packages] [Bug 1785093] Re: RecursionError error in call_adjusted()

The error is still not appearing on 16.04:

https://errors.ubuntu.com/?release=Ubuntu%2016.04=unattended-
upgrades=year=1.1ubuntu1.18.04.7~16.04.1


It is not surprising since the regression was not present in 16.04 without the 
fix.

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

Title:
  RecursionError error in call_adjusted()

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

Bug description:
  [Impact]

   * Unattended-upgrades may crash and stop installing security updates on 
users' system due to entering infinite loop.
   * The fix ensures terminating the recursive calls.

  [Test Case]

   * TODO / observe the crash not being reported for fixed releases on
  errors.ubuntu.com.

  [Regression Potential]

   * Unattended-upgrades now adjusts package candidates only to lower versions 
than the one originally offered by apt's resolver. This is a change in behavior 
which aligns well with the default configuration, i.e. installing packages from 
-security but not from -updates, since -updates almost always have higher 
version numbers. This change may cause using different upgrade paths when PPAs 
are involved and all packages can't be upgraded to the highest versions found 
in allowed origins, because of Conflicts: for example.
   * Unexpected regressions can cause candidate adjustments not taking place, 
but please note that autopkgtest now includes applying all outstanding security 
updates for the release thus the new code is covered, too.

  [Original Bug report]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/fa706afe2f0e04b661fe54da0a59b9fc3da50734 
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/.

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1991, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1647, in main
  cache, options, allowed_origins, blacklisted_pkgs, whitelisted_pkgs)
    File "/usr/bin/unattended-upgrade", line 1349, in calculate_upgradable_pkgs
  whitelisted_pkgs)
    File "/usr/bin/unattended-upgrade", line 1288, in try_to_upgrade
  cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed)
    File "/usr/bin/unattended-upgrade", line 212, in mark_upgrade_adjusted
  self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs)
    File "/usr/bin/unattended-upgrade", line 206, in call_adjusted
  self.call_adjusted(function, pkg, **kwargs)
    File "/usr/bin/unattended-upgrade", line 206, in call_adjusted

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

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

[Touch-packages] [Bug 1260041] Re: Unattended-Upgrades crashes with a dpkg error

Tested with 0.90ubuntu0.10 (not fixed) and 1.1ubuntu1.18.04.7~16.04.1
(fixed):

With the not fixed version the lock is lost by u-u, while u-u kept running:
...
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "", line 1, in 
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "", line 1, in 
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
True
True
True
True
True
True
True
True
True
True
...


With the fixed version but keeping unfixed python-apt the lock is still lost by 
u-u, but u-u crashes. This is expected and is safer than the unfixed behaviour:
...
conffile line: /etc/rsyslog.d/21-cloudinit.conf d4cf2e5d3cb9914cf7e6cdc08d298339
current md5: d4cf2e5d3cb9914cf7e6cdc08d298339
blacklist: []
whitelist: []
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: cloud-init curl kmod libc-bin libc6 
libcurl3-gnutls libkmod2 locales multiarch-support python-apt-common 
python3-apt snapd ubuntu-core-launcher
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['python-apt-common']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 
/var/cache/apt/archives/python-apt-common_1.1.0~beta1ubuntu0.16.04.3_all.deb 
/usr/bin/dpkg --status-fd 11 --configure python-apt-common:all 
/usr/bin/dpkg --status-fd 13 --configure --pending 
Exception happened during upgrade.
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 374, in __exit__
apt_pkg.pkgsystem_lock_inner()
AttributeError: module 'apt_pkg' has no attribute 'pkgsystem_lock_inner'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 558, in cache_commit
res = cache.commit(install_progress=iprogress)
  File "/usr/bin/unattended-upgrade", line 376, in __exit__
apt_pkg.pkgsystem_lock()
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
Exception happened during upgrade.
NoneType
Installing the upgrades failed!
error message: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
dpkg returned a error! See 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log for details
InstCount=0 DelCount=0 BrokenCount=0
root@x-uu:~#

With both u-u and python-apt fixed u-u keeps the lock for the whole run:
...
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "", line 1, in 
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
Traceback (most recent call last):
  File "", line 1, in 
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?

Traceback (most recent call last):
  File "", line 1, in 
SystemError: E:Could not get lock /var/lib/dpkg/lock-frontend - open (11: 
Resource temporarily unavailable), E:Unable to acquire the dpkg frontend lock 
(/var/lib/dpkg/lock-frontend), is another process using it?
True
True
...

...
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['python-apt-common']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 
/var/cache/apt/archives/python-apt-common_1.1.0~beta1ubuntu0.16.04.3_all.deb 
/usr/bin/dpkg --status-fd 11 --configure python-apt-common:all 
/usr/bin/dpkg --status-fd 13 --configure --pending 
left to upgrade {'libc-bin', 'libcurl3-gnutls', 'libkmod2', 'curl', 'libc6', 
'ubuntu-core-launcher', 'multiarch-support', 'snapd', 'locales', 'kmod', 
'cloud-init'}
applying set ['libc-bin']
/usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure 
/var/cache/apt/archives/libc-bin_2.23-0ubuntu11_amd64.deb 
/usr/bin/dpkg --status-fd 11 --configure libc-bin:amd64 
/usr/bin/dpkg --status-fd 13 --configure --pending

[Touch-packages] [Bug 1230246] Re: Add Auto-Submitted header to email report

Tested with 1.1ubuntu1.18.04.7~16.04.1:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20181213_182038_2962e@/log.gz

...
>From root@autopkgtest Thu Dec 13 17:15:02 2018
Return-path: 
Envelope-to: root@autopkgtest
Delivery-date: Thu, 13 Dec 2018 17:15:02 +
Received: from root by autopkgtest with local (Exim 4.86_2)
(envelope-from )
id 1gXUZi-0007kS-6h
for root@autopkgtest; Thu, 13 Dec 2018 17:15:02 +
Subject: [package on hold] unattended-upgrades result for autopkgtest: True
To: root@autopkgtest
Auto-Submitted: auto-generated
MIME-Version: 1.0
...



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

Title:
  Add Auto-Submitted header to email report

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

Bug description:
  Please add the header

Auto-Submitted: auto-generated

  to the emails generated by the unattended-upgrade process. This would
  assist in both the mail filtering for receivers and the correct
  processing for "vacation" auto-responders.

  Further technical details are given in:

   http://tools.ietf.org/html/rfc3834#section-5
   http://tools.ietf.org/html/rfc5230#page-8
   
https://www.iana.org/assignments/auto-submitted-keywords/auto-submitted-keywords.xhtml

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

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

[Touch-packages] [Bug 1789637] Re: Proper support for frontend lock

As the log shows I actually tested with 1.1ubuntu1.18.04.7~16.04.1, the
correct version.

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

Title:
  Proper support for frontend lock

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

Bug description:
  [Impact]

  Apt and dpkg implemented the Frontend Locking API and unattended-
  upgrades needs to adopt it to not leave the packaging system unlocked
  while passing control to python-apt and dpkg to perform package
  installations and removals. Leaving the packaging system unlocked
  caused many crashes of u-u when other tools took the lock and in the
  worse case let other package management tools operate on dpkg's
  database breaking systems.

  The change takes advantage of python-apt's new API and keeps the
  frontend lock during the run of u-u and unlocks only the inner locks
  for committing changes.

  [Test case]

  Run strace unattended-upgrades to upgrade several packages and check
  that lock-frontend is acquired at the beginning and not released until
  the end (not reacquired repeatedly).

  Unfixed u-u's output is like this:
  # strace unattended-upgrade --verbose --dry-run 2>&1 | grep lock
  openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", 
O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
  openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 5
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6
  openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 5
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6
  openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 93
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6
  openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 5
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6
  openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 5
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6
  ...

  Fixed u-u's output is like that:
  # strace   unattended-upgrade --dry-run --verbose 2>&1 | grep lock
  openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", 
O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
  openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 8
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10
  openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 57
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10
  openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 69
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10
  openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 70
  openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10
  ...

  [Regression potential]

  Incorrect lock API usage can make unattended-upgrades to crash, but it
  is unlikely to hang since the lock handling operations are non-
  blocking. Failing to reserve the locks can also cause problems by
  allowing other package management tools to install packages in
  parallel, but this problem existed in the past, too.

  [Additional Info]
  This is part of a wider series of changes for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

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

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

[Touch-packages] [Bug 1789637] Re: Proper support for frontend lock

Tested 1.1ubuntu1.18.04.7~16.04.1:

Previous version:

root@x-uu-1789637-2:~# strace unattended-upgrade --verbose --dry-run 2>&1 | 
grep lock
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
open("/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 45
open("/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4

Previous version with python3-apt supporting frontend lock:

root@x-uu-1789637-2:~# apt install -qq python3-apt
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
Suggested packages:
  python3-apt-dbg python-apt-doc
The following packages will be upgraded:
  python3-apt
1 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.
Need to get 138 kB of archives.
After this operation, 6,144 B of additional disk space will be used.
(Reading database ... 25712 files and directories currently installed.)
Preparing to unpack .../python3-apt_1.1.0~beta1ubuntu0.16.04.3_amd64.deb ...
Unpacking python3-apt (1.1.0~beta1ubuntu0.16.04.3) over 
(1.1.0~beta1ubuntu0.16.04.2) ...
Setting up python3-apt (1.1.0~beta1ubuntu0.16.04.3) ...
root@x-uu-1789637-2:~# strace unattended-upgrade --verbose --dry-run 2>&1 | 
grep lock
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
open("/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 45
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
open("/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 48
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5

Fixed version:

root@x-uu-1789637-2:~# apt install -qq unattended-upgrades
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
Suggested packages:
  bsd-mailx default-mta | mail-transport-agent needrestart
The following packages will be upgraded:
  unattended-upgrades
1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Need to get 40.2 kB of archives.
After this operation, 69.6 kB of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 25712 files and directories currently installed.)
Preparing to unpack .../unattended-upgrades_1.1ubuntu1.18.04.7~16.04.1_all.deb 
...
Unpacking unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) over 
(0.90ubuntu0.10) ...
Processing triggers for systemd (229-4ubuntu21.15) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up unattended-upgrades (:) ...
Installing new version of config file 
/etc/kernel/postinst.d/unattended-upgrades ...
Installing new version of config file 
/etc/pm/sleep.d/10_unattended-upgrades-hibernate ...
root@x-uu-1789637-2:~# strace unattended-upgrade --verbose --dry-run 2>&1 | 
grep lock
open("/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6
open("/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 50
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6

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

Title:
  Proper support for frontend lock

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

Bug description:
  [Impact]

  Apt and dpkg implemented the Frontend Locking API and unattended-
  upgrades needs to adopt it to not leave the packaging system unlocked
  while passing control to python-apt and dpkg to perform package
  installations and removals. Leaving the packaging system unlocked
  caused many crashes of u-u when other tools took the lock and in the
  worse case let other package management tools operate on dpkg's
  database breaking systems.

  The change takes advantage of python-apt's new API and keeps the
  frontend lock during the run of u-u and unlocks only the inner locks
  for committing changes.

  [Test case]

  Run strace unattended-upgrades to upgrade several packages and check
  that lock-frontend is acquired at the beginning and not released until
  the end (not reacquired repeatedly).

  Unfixed u-u's output is like this:
  # strace unattended-upgrade --verbose --dry-run 2>&1 | grep lock
  openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", 
O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
  openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 
0640) = 5
  openat(AT_FDCWD,

[Touch-packages] [Bug 1815036] Re: uri defined for connectivity check does not have IPv6 address

Thank you for your bug report, that's not a network-manager issue but
indeed that's a problem on the Ubuntu infrastructure side which I'm
going to report

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  uri defined for connectivity check does not have IPv6 address

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As per subject. This package defines the file
  /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which
  defines the uri for the connectivity check to be http://connectivity-
  check.ubuntu.com

  This hostname does not resolve to an IPv6 address. Therefore, even if
  the user has fully working IPv6, the connectivity check for IPv6 will
  fail. As a result, the IPv6 default routes will be heavily
  deprioritised (ie: having 2 added to the metric) rendering them
  effectively inoperable absent a deliberate effort to use IPv6-only
  addresses.

  NB: This was discovered by-the-by during reporting of bug #1814262
  upstream at
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448

  It seems to be irrelevant to the main thrust of that bug, which is
  that IPv4 wired routes are not being identified as working correctly.
  In fact, when I switch to network-manager-config-connectivity-debian,
  the hostname defined there *does* have a working IPv6 address, and the
  issue actually being reported in that other bug does not affect the
  IPv6 routes, only the IPv4 ones.

  The bug here probably doesn't need any change made to the package
  itself, but rather to the networking of the actual target URL. It
  needs an IPv6 () DNS record, and for it to function on that
  address.

  I note in passing the debian connectivity check URL resolves to
  several IP addresses - four IPv4 addresses and 3 IPv6 addresses,
  presumably geographically diverse. (It's actually a CNAME to
  static.debian.org) This looks like it would be a more reliable target
  for connectivity checks. The ubuntu URL only resolves to a single IPv4
  address.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager-config-connectivity-ubuntu 1.15.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 12:35:24 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-11 (148 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IpRoute:
   default via 192.168.1.254 dev enp63s0 proto dhcp metric 100 
   default via 192.168.1.254 dev wlp2s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-01-13 (24 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.15.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1814925] Re: Bluetooth mouse stops responding after extended deep sleep

2019-02-07 Thread Jill Manfield

I am told by internal engineering the Qualcom fix below is being tested
for this issue:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=2ddd8f0f33972a96f34722de6165ed88a6231f9d

Can you get me more information about this and when it is being
released?

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

Title:
  Bluetooth mouse stops responding after extended deep sleep

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM iso

  Bluetooth mouse tested with HP X4b BT Last mouse stops responding
  after long extended deep sleep (24-48 hours).

  Bluetooth settings window which  initially reported Bluetooth as
  connected now shows disconnected.  Pushing the button within the
  settings window to reconnect takes me back to off.  Switching back to
  on and off keeps bringing me back to off unless I reboot the device
  and or turn off the mouse via the underneath portion of the BT device.

  Demsg logs shows an extremely large number of "Bluetooth: hci:0 last
  event is not cmd complete (0x0f)"

  Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: bluez 5.48-0ubuntu3.1
  XPS 13 9370 bios 1.6.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:16:07 2019
  InstallationDate: Installed on 2019-01-03 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=9a57d978-48d7-4ef3-9f67-5e6b72107fcf ro mem_sleep_default=deep 
initrdefi /acpi_override quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0H0VG3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 9C:B6:D0:90:A0:16  ACL MTU: 1024:8  SCO MTU: 50:8
    UP RUNNING PSCAN ISCAN
    RX bytes:748157 acl:263 sco:0 events:22281 errors:0
    TX bytes:15577 acl:124 sco:0 commands:1167 errors:0

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

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

[Touch-packages] [Bug 1815036] [NEW] uri defined for connectivity check does not have IPv6 address

2019-02-07 Thread Rachel Greenham

Public bug reported:

As per subject. This package defines the file
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which
defines the uri for the connectivity check to be http://connectivity-
check.ubuntu.com

This hostname does not resolve to an IPv6 address. Therefore, even if
the user has fully working IPv6, the connectivity check for IPv6 will
fail. As a result, the IPv6 default routes will be heavily deprioritised
(ie: having 2 added to the metric) rendering them effectively
inoperable absent a deliberate effort to use IPv6-only addresses.

NB: This was discovered by-the-by during reporting of bug #1814262
upstream at
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448

It seems to be irrelevant to the main thrust of that bug, which is that
IPv4 wired routes are not being identified as working correctly. In
fact, when I switch to network-manager-config-connectivity-debian, the
hostname defined there *does* have a working IPv6 address, and the issue
actually being reported in that other bug does not affect the IPv6
routes, only the IPv4 ones.

The bug here probably doesn't need any change made to the package
itself, but rather to the networking of the actual target URL. It needs
an IPv6 () DNS record, and for it to function on that address.

I note in passing the debian connectivity check URL resolves to several
IP addresses - four IPv4 addresses and 3 IPv6 addresses, presumably
geographically diverse. (It's actually a CNAME to static.debian.org)
This looks like it would be a more reliable target for connectivity
checks. The ubuntu URL only resolves to a single IPv4 address.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: network-manager-config-connectivity-ubuntu 1.15.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
Uname: Linux 4.19.0-12-generic x86_64
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  7 12:35:24 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-09-11 (148 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
IpRoute:
 default via 192.168.1.254 dev enp63s0 proto dhcp metric 100 
 default via 192.168.1.254 dev wlp2s0 proto dhcp metric 20600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 
100 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
PackageArchitecture: all
SourcePackage: network-manager
UpgradeStatus: Upgraded to disco on 2019-01-13 (24 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.15.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug disco

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

Title:
  uri defined for connectivity check does not have IPv6 address

Status in network-manager package in Ubuntu:
  New

Bug description:
  As per subject. This package defines the file
  /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which
  defines the uri for the connectivity check to be http://connectivity-
  check.ubuntu.com

  This hostname does not resolve to an IPv6 address. Therefore, even if
  the user has fully working IPv6, the connectivity check for IPv6 will
  fail. As a result, the IPv6 default routes will be heavily
  deprioritised (ie: having 2 added to the metric) rendering them
  effectively inoperable absent a deliberate effort to use IPv6-only
  addresses.

  NB: This was discovered by-the-by during reporting of bug #1814262
  upstream at
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448

  It seems to be irrelevant to the main thrust of that bug, which is
  that IPv4 wired routes are not being identified as working correctly.
  In fact, when I switch to network-manager-config-connectivity-debian,
  the hostname defined there *does* have a working IPv6 address, and the
  issue actually being reported in that other bug does not affect the
  IPv6 routes, only the IPv4 ones.

  The bug here probably doesn't need any change made to the package
  itself, but rather to the networking of the actual target URL. It
  needs an IPv6 () DNS record, and for it to function on that
  address.

  I note in passing the debian connectivity check URL resolves to
  several IP addresses - four IPv4 addresses and 3 IPv6 addresses,
  presumably geographically diverse. (It's actually a CNAME to
  static.debian.org)

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

2019-02-07 Thread Ubuntu Foundations Team Bug Bot

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

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

** Tags added: patch

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

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

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

[Touch-packages] [Bug 1799111] Re: lots of Classes missing from docs (e.g. QFileInfo)

2019-02-07 Thread Łukasz Zemczak

The pending-sru page reports that there are some kdeconnect (and a few
other) autopkgtest regressions for the qtbase upload. I have re-ran most
of them, but could someone take a look and check why they suddenly fail?

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

Title:
  lots of Classes missing from docs (e.g. QFileInfo)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qttools-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  Confirmed
Status in qtdeclarative-opensource-src source package in Cosmic:
  Confirmed
Status in qttools-opensource-src source package in Cosmic:
  Confirmed
Status in qtbase-opensource-src package in Debian:
  Fix Released

Bug description:
  [Impact]
  The packaged Qt documentation, which can be viewed in browser (qt*-doc-html 
packages) or in Qt Assistant (qt*-doc packages) is missing all documentation 
generated from C++ files. Only the static text is present.

  Qt is split by many modules (qtbase, qtdeclarative, qtwebengine,
  etc.).

  To properly fix this bug, we need changes in qtbase and qttools
  modules. In addition, I will be uploading a no-change rebuild of
  qtdeclarative module to demonstrate that the fixes work.

  If requested, I can also upload no-change rebuilds of some other
  modules to get their -doc packages properly regenerated.

  [Test Case]
  For qtbase5-doc-html:
  1. Install qtbase5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtcore/qobject.html is present.

  For qtdeclarative5-doc-html:
  1. Install qtdeclarative5-doc-html package.
  2. Make sure /usr/share/qt5/doc/qtquick/qquickwidget.html is present.

  [Regression Potential]
  The proposed change in qtbase is affecting only builds of Qt modules 
documentation. So the worst thing it can do is breaking the build of -doc 
packages in other Qt modules. However, as confirmed by qtdeclarative example, 
it makes things only better, not worse.

  The proposed change in qttools can affect more packages. It can result
  in qdoc passing more -isystem flags to clang code analyzer. I am not
  aware of negative consequences of this, but if they happen, these
  consequences will be limited to potential build failures or wrong
  documentation contents.

  [Other Info]
  Description of the fix:

  qdoc is a tool that parses C++ source files and generates
  documentation from them. Recently, qdoc began using clang instead of
  its own C++ parser. Clang needs the C++ standard library to work.
  Starting with llvm-toolchain 1:7~+rc1-1~exp2, the GCC C++ standard
  library is no longer on clang’s default search paths, so we need to
  pass it explicitly as -I flag. The proposed qtbase patch
  (qdoc_default_incdirs.diff) does that.

  That patch fixes documentation build for qtbase, but for other modules
  there is another problem. The Qt headers are installed into
  /usr/include//qt5 directory, but it is also not on Clang
  default search path. qmake passes these directories as -isystem flags,
  but qdoc ignores -isystem by default, unless it is built with
  QDOC_PASS_ISYSTEM defined. So the proposed change in qttools is
  building with this define.

  [Original Description]
  The Qt offline documentation for cosmic is incomplete. In fact there's 
virtually no content what so ever. It would be easier I think to list what 
actually got picked up that what was missed.

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

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

[Touch-packages] [Bug 1814501] Re: package libgssapi-krb5-2:amd64 1.16-2ubuntu0.1 failed to install/upgrade: függőségi hibák - e csomag beállítatlan maradt

2019-02-07 Thread Eduardo dos Santos Barretto

** Changed in: krb5 (Ubuntu)
 Assignee: Eduardo dos Santos Barretto (ebarretto) => (unassigned)

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

Title:
  package libgssapi-krb5-2:amd64 1.16-2ubuntu0.1 failed to
  install/upgrade: függőségi hibák - e csomag beállítatlan maradt

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  I want it to try installation Google Earth Pro but all time
  collapsing.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgssapi-krb5-2:amd64 1.16-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   google-earth-pro-stable:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Feb  4 10:23:29 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  DpkgHistoryLog:
   Start-Date: 2019-02-04  10:23:09
   Commandline: packagekit role='install-files'
   Requested-By: paluch (1001)
   Install: google-earth-pro-stable:amd64 (7.3.2.5495-r0)
  ErrorMessage: függőségi hibák - e csomag beállítatlan maradt
  InstallationDate: Installed on 2016-10-05 (852 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: krb5
  Title: package libgssapi-krb5-2:amd64 1.16-2ubuntu0.1 failed to 
install/upgrade: függőségi hibák - e csomag beállítatlan maradt
  UpgradeStatus: Upgraded to bionic on 2019-01-11 (23 days ago)

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

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

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

2019-02-07 Thread xantares

here is a patch against libseccomp 2.3.1 in bionic (on top of the debian risc 
port patch)

I manually applied changes from libseccomp 2.3.3 that reference the
statx syscalls

for the risc part i used the diff from
https://github.com/seccomp/libseccomp/blob/2a70ad4f3e8ab80e88f0662a760f4ef1d9219205/src
/arch-parisc-syscalls.c

successfully rebuilt the package and tested it on x86_64

please apply for ubuntu bionic

to test it in a docker container you can do:
WORKDIR /tmp
RUN wget -q 
https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c
RUN gcc test-statx.c -o test-statx
RUN touch test-file
RUN ./test-statx test-file


** Patch added: "libsecomp231-statx.patch"
   
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1755250/+attachment/5236693/+files/libsecomp231-statx.patch

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

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

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

[Touch-packages] [Bug 1640180] Re: gnome-todo doesn't load CalDav task list from EDS

2019-02-07 Thread distinct

This is still true for ubuntu 18.10.

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

Title:
  gnome-todo doesn't load CalDav task list from EDS

Status in GNOME To Do:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in gnome-todo package in Ubuntu:
  Triaged

Bug description:
  Since the upgrade to Yakkety Gnome-TODO doesn't show my remote CalDav
  task list that were set through evolution. The list are still
  available in working in Evolution.

  I tried to set them up again but they didn't appear. 
  I tried upgrading to version available in various gnome3-ppa (still 3.20.* 
though) and it didn't help.

  The bug seems to have been handled in Fedora :
  https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1363848
  and https://bodhi.fedoraproject.org/updates/FEDORA-2016-db729be3e1 (I
  found those while searching the web for a solution).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-todo/+bug/1640180/+subscriptions

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

[Touch-packages] [Bug 1814551] Re: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA)

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

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

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

Title:
  Ubuntu 18.10's ibus package breaks password fields in Firefox Beta
  (65, 66 via PPA)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Essentially
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but
  reproducible in Cosmic even with the patched gnome-shell installed via
  APT.

  SYSTEM INFO
  =

  * Ubuntu 18.10 Cosmic with latest updates
  * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20
  * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 
09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  * gnome-shell 3.30.1-2ubuntu1.18.10.2
  * ibus 1.5.19-1ubuntu1
  * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA)

  
  STEPS TO REPRODUCE
  =

  1. Ensure keyboard input method system is 
  1. Download Firefox Beta channel via their official PPA: 
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next
  2. Download and install the 1Password X firefox extentsion: 
https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/
  3. Open the extension window by either pressing the shortcut Ctrl+. or 
clicking the 1Password icon in the Firefox UI
  4. Enter in the password in the input and press enter.

  Expected: The vault unlocks or displays a "this is a wrong password"

  Actual: The UI appears to "refresh" and nothing occurs.

  WORKAROUND/VALIDATION
  =

  Like the original bug, switching the keyboard input method to XIM from
  iBus resolves the issue suggesting to me that the symptoms I am
  experiencing are caused by the root issue previously filed, fixed, and
  deployed.

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

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

[Touch-packages] [Bug 1811580] Re: systemd fails to start sshd at reboot

2019-02-07 Thread Adrian Kaegi

Hi xnox
Thank your for your fast reply!

Indeed, i found the problem with a self-compiled package, which made a file in 
/usr/lib/tmpfiles.d and ran the command "chown nrpe.nrpe /var".
After deleting the affected file out of /usr/lib/tmpfiles.d and made a manual 
"chown root.root /var" everything worked well!

BR Cadirol

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

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got caught by it in the middle of setting up a new server
  yesterday, and it took a whole day to find the source.

  The appropriate fix would be to ensure that systemd can successfully
  'start ssh.service' even when 'UsePrivilegeSeparation yes' is set.
  systemd needs to test that /var/run/sshd/ exists before starting sshd,
  just as the init.d script for sshd does. openssl could also be patched
  so that UsePrivilegeSeparation is no longer enabled by default,
  however that is not going to solve the problem for millions of pre-
  existing config files. Only an update to openssl to force-override
  that flag to 'no' would solve the problem. Thus systemd still needs to
  be responsible for ensuring that it inits sshd properly by ensuring
  that /var/run/sshd/ exists before it sends the 'start' command.

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

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

[Touch-packages] [Bug 1814905] Re: dash exits when receiving wall message

2019-02-07 Thread Imre Gergely

Here's a quick demonstration with Ubuntu 18.10 desktop, fresh install in
a VirtualBox VM, up-to-date

https://youtu.be/-VSj_ZZjv3w (1min screen capture)

with and without strace.
I've also attached a perf trace output. I've started /bin/sh as root like this:

perf trace -o /tmp/dash-perf-trace.txt /bin/sh

Pressed a couple of enters, did an echo, and then a "wall foo" from
another terminal, as normal user.

I'm not saying it's dash's fault, I just didn't know where to open the
ticket.

Please let me know if you need anything else.

Thanks!

** Attachment added: "dash-perf-trace.txt"

https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1814905/+attachment/5236686/+files/dash-perf-trace.txt

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

Title:
dash exits when receiving wall message

Status in dash package in Ubuntu:
Incomplete

Bug description:
When using "/bin/sh" (dash) as a shell for ssh, or just starting
/bin/sh in a terminal, when the shell receives a wall message (from
another user or root), it just quits.

How to reproduce:
- start a terminal (xterm, gnome-terminal, etc), usually starts with bash
- from bash run 'sh' command to open a dash shell
- start another terminal, and run: echo "foo" | wall
- the broadcast message appears on both terminals
- in the first terminal you are thrown back to bash, because dash exits

I've tried this on Ubuntu 14.04, 16.04, 18.04 (64bits) latest updates
and it's happening on all of them. I've also tried with latest dash
from git, compiled on Ubuntu 16.04, same problem, that's why I don't
think it's dash's problem.

Also tried on CentOS 7, there is no problem there.

The problem appears this morning (6 February) after updating to latest
version of 16.04, 18.04. I also have a box with 16.04 but not the
latest updates, and on that box the problem does not happen.

If one uses dash as a login shell, and enters on a remote box with SSH
for example, the connection can be terminated by another user simply
wall'ing a broadcast message (or a system daemon like NUT). This could
be taken as a potential security issue.

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

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

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

2019-02-07 Thread Lukáš Karas

I can confirm that this bug is solved in Ubuntu Cosmic (18.10) with
Docker 18.06.1 and libseccomp 2.3.3.

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed

Bug description:
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

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

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

[Touch-packages] [Bug 1814653] Re: get_python_lib() returns path to python3 instead of python3.6

2019-02-07 Thread vital

The issue is that if `get_python_lib()` is called with `prefix='/usr/local'` 
argument then Ubuntu version returns: 
``` sh
$ /usr/bin/python3 -c "from distutils.sysconfig import 
*;print(get_python_lib(prefix='/usr/local'))"
/usr/local/lib/python3/dist-packages
```

while mainstream Python returns:
```sh
$ python3 -c "from distutils.sysconfig import 
*;print(get_python_lib(prefix='/usr/local'))"
/usr/local/lib/python3.6/site-packages
```

`sys.path` (in both Ubuntu and mainstream Python) doesn't contain 
`/usr/local/lib/python3/dist-packages` path, it contains 
`/usr/local/lib/python3.6/dist-packages` instead, so when `/usr/local` prefix 
is used things don't work:
```
$ PYTHONPATH='' /usr/bin/python3 -c "import sys; print(sys.path)"
['', '/usr/lib/python36.zip', '/usr/lib/python3.6', 
'/usr/lib/python3.6/lib-dynload', 
'/home/vital/.local/lib/python3.6/site-packages', 
'/usr/local/lib/python3.6/dist-packages', '/usr/lib/python3/dist-packages']
```

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

Title:
   get_python_lib() returns path to python3 instead of python3.6

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Python version is Python 3.6.7 (default, Oct 22 2018, 11:32:17)
  Ubuntu 18.04.01

  When I call get_python_lib() function to get the Python lib path to install a 
module it returns '/usr/lib/python3/dist-packages' instead of python3.6 dir:
  python3 -c "from distutils.sysconfig import *;print(get_python_lib())"

  
  This is because the source code '/usr/lib/python3.6/distutils/sysconfig.py' 
has the branch on Ubuntu:

  Code:
  
  if os.name == "posix":
  libpython = os.path.join(prefix,
   "lib", "python" + get_python_version())
  if standard_lib:
  return libpython
  elif (is_default_prefix and
'PYTHONUSERBASE' not in os.environ and
'VIRTUAL_ENV' not in os.environ and
'real_prefix' not in sys.__dict__ and
sys.prefix == sys.base_prefix):
  return os.path.join(prefix, "lib", "python3", "dist-packages")
  

  However, this code does not present in the original cpython code 3.6.7:
  
https://github.com/python/cpython/blob/ca7d2933a388677cc3bbc621913b479452c0f25a/Lib/distutils/sysconfig.py#L109

  Is it the right behavior?

  Why the get_python_lib() result should depend on PYTHONUSERBASE and
  VIRTUAL_ENV and points to python3 instead of python3.6

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.7-1~18.04
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  5 12:41:28 2019
  InstallationDate: Installed on 2018-09-06 (151 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1811225] Re: Mesa 18.2.8 stable release