[Touch-packages] [Bug 1818204] NetDevice.lo.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243317/+files/NetDevice.lo.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] PulseList.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243327/+files/PulseList.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] ProcModules.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243326/+files/ProcModules.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] NetworkManager.conf.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243321/+files/NetworkManager.conf.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] PciNetwork.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243322/+files/PciNetwork.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] nmcli-dev.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243331/+files/nmcli-dev.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] UdevDb.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1818204/+attachment/5243329/+files/UdevDb.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] WifiSyslog.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243330/+files/WifiSyslog.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] RfKill.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1818204/+attachment/5243328/+files/RfKill.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] IpAddr.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1818204/+attachment/5243312/+files/IpAddr.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] NetDevice.enx00e04c704f68.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.enx00e04c704f68.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243316/+files/NetDevice.enx00e04c704f68.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] ProcInterrupts.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243325/+files/ProcInterrupts.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] ProcEnviron.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243324/+files/ProcEnviron.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] ProcCpuinfoMinimal.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243323/+files/ProcCpuinfoMinimal.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] NetDevice.virbr0.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.virbr0.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243318/+files/NetDevice.virbr0.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] NetDevice.virbr0-nic.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.virbr0-nic.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243319/+files/NetDevice.virbr0-nic.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] NetDevice.wlp1s0.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "NetDevice.wlp1s0.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243320/+files/NetDevice.wlp1s0.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] IwConfig.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243313/+files/IwConfig.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] Lspci.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1818204/+attachment/5243314/+files/Lspci.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] Lsusb.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1818204/+attachment/5243315/+files/Lsusb.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] CRDA.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1818204/+attachment/5243309/+files/CRDA.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] CurrentDmesg.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243310/+files/CurrentDmesg.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1818204] Dependencies.txt

2019-03-03 Thread Sami Pietila
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1818204/+attachment/5243311/+files/Dependencies.txt

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

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

2019-03-03 Thread Sami Pietila
apport information

** Tags added: apport-collected

** Description changed:

  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter (rev 31).
  
  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  sami   1315 F pulseaudio
+  /dev/snd/controlC0:  sami   1315 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2019-02-20 (11 days ago)
+ InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ IpRoute:
+  default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 
+  130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100 
+  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
+  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
+ MachineType: LENOVO 81H1
+ NetworkManager.state:
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+ Package: network-manager 1.10.6-2ubuntu1.1
+ PackageArchitecture: amd64
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-15-generic N/A
+  linux-backports-modules-4.18.0-15-generic  N/A
+  linux-firmware 1.173.3
+ Tags:  bionic wayland-session wayland-session
+ Uname: Linux 4.18.0-15-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/17/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 8PCN45WW
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40700 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo ideapad 530S-14ARR
+ dmi.modalias: 
dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR:
+ dmi.product.family: ideapad 530S-14ARR
+ dmi.product.name: 81H1
+ dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR
+ dmi.product.version: Lenovo ideapad 

[Touch-packages] [Bug 1818204] Missing required logs.

2019-03-03 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1818204

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

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

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

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

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

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


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

2019-03-03 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

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

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

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

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

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


[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]

2019-03-03 Thread rubpa
I'm having this issue on my Dell Latitude E6410 on which Ubuntu 14.04
was working fine until I upgraded to 18.04.

$ cat /proc/asound/cards
 0 [MID]: HDA-Intel - HDA Intel MID
  HDA Intel MID at 0xf695 irq 26
$ aplay -l
aplay: device_list:270: no soundcards found...

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

Title:
  No sound card detected by PulseAudio and ALSA, but is visible in lspci
  [Dell XPS 13 9360]

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through
  the troubleshooting steps here:

  https://help.ubuntu.com/community/SoundTroubleshooting

  and have included some output of those diagnostic steps below:

  
  $ sudo aplay -l
  aplay: device_list:270: no soundcards found...

  $ find /lib/modules/`uname -r` | grep snd
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko
  /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko
  ...and lots more

  $ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 131
Memory at dc228000 (64-bit, non-prefetchable) [size=16K]
Memory at dc20 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  Sound settings still only list dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 18:44:06 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-11 (426 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 01KT0M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2019-03-03 Thread Kristijan Žic 
I encounter probably the same bug in 18.04 and in 18.10.

I've opened a separate bug report because it might not be the exact issue:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1818382

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GStreamer:
  Expired
Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Expired
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in clutter-gst-3.0 package in Ubuntu:
  Incomplete
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1818456] [NEW] Horrible video experience with Intel Graphic after new fresh install

2019-03-03 Thread Welington R. Braga
Public bug reported:

Since my new fresh install of Ubuntu 18.04 I can't have a good
experience.

Use a simple gEdit is impossible because the text area is not showed in
a white background but "cloning" everything that were in that screen
position curiously it not happen with Leafpad editor. But occur with
Gnome-claculator.

My LibreOffice can't show their buttons in any toolbar.

I've tried to install the oibaf PPA (sudo add-apt-repository ppa:oibaf
/graphics-drivers) expcting some improve but nothing change. Unhappily.

Some years ago I have this same experience in Ubuntu 16.04 but it was
over (I don't know how) and even after a dist-upgrade to 18.04 it is OK,
but now I had to to new install and the bug is here. Unhappily.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.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
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolb 
ox,decor,grid,move,resize,mousepoll,regex,snap,gno 
mecompat,place,imgpng,vpswitch,animation,wall,work 
arounds,fade,session,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  3 22:17:53 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GconfCompiz:
 /apps/compiz-1/general:
   /apps/compiz-1/general/screen0:
/apps/compiz-1/general/screen0/options:
 active_plugins = [core,bailer,detection,composite,opengl,compiztoolb 
ox,decor,grid,move,resize,mousepoll,regex,snap,gno 
mecompat,place,imgpng,vpswitch,animation,wall,work 
arounds,fade,session,expo,ezoom,unityshell]
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2018-09-01 (183 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. H87M-HD3
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-45-generic 
root=UUID=3c502856-3b66-4815-8747-59e0fce0d335 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-HD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H87M-HD3
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97+git1902261830.d54e54~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1903030730.cb4e3e~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1903030730.cb4e3e~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.1.99+git1902111932.15697e~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1903011933.6afed3~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1901290732.ec2b45~oibaf~b

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

** Attachment added: "Libreoffice Toolbar"
   
https://bugs.launchpad.net/bugs/1818456/+attachment/5243218/+files/Captura%20de%20tela%20de%202019-03-03%2022-28-14.png

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

Title:
  Horrible video experience with Intel Graphic after new fresh install

Status in xorg package in Ubuntu:
  New

Bug description:
  Since my new fresh install of Ubuntu 18.04 I can't have a good
  experience.

  Use a simple gEdit is impossible because the text area is not showed
  in a white background but "cloning" everything that were in that
  screen position curiously it not happen with Leafpad editor. But occur
  with Gnome-claculator.

  My LibreOffice can't show their buttons in any toolbar.

  I've tried to install the oibaf PPA (sudo add-apt-repository ppa:oibaf
  

[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo

2019-03-03 Thread Eric Desrochers
[VERIFICATION XENIAL]

Using the protocol mentioned in the [Test Case] with systemd from
xenial-proposed, version : 229-4ubuntu21.17. I can no longer reproduce
the situation.

# systemctl list-units --all | grep bind-test
  mnt-bind\x2dtest.mount loadedactive mounted   
/mnt/bind-test

- Eric


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

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

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

Title:
  systemd: core: Fix edge case when processing /proc/self/mountinfo

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  kubernetes loaded inactive dead transient mount points grows
  https://github.com/kubernetes/kubernetes/issues/57345

  [Test Case]

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  Expected outcome (w/ the fix) :

  # cd /tmp
  # mkdir -p bind-test/abc
  # mount --bind bind-test bind-test
  # mount -t tmpfs tmpfs bind-test/abc
  # umount bind-test/abc
  # systemctl list-units --all | grep bind-test
  tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test

  [Regression Potential]

  This is a adapted version of 2 upstream fixes as the original upstream
  commit has been made on top on 2 functions mount_setup_new_unit() &
  mount_setup_existing_unit() that not yet exist systemd 229. It is
  easily adaptable because the current function mount_setup_unit() is
  dealing with both of at the moment instead of being individually
  separate in two distinct function.

  It is an adaptation of commits :
  [65d36b495] core: Fix edge case when processing /proc/self/mountinfo
  [03b8cfede] core: make sure to init mount params before calling 
mount_is_extrinsic()

  This patch changes mount_setup_unit() to prevent the just_mounted
  mount setup flag from being overwritten if it is set to true. This
  will allow all mount units created from /proc/self/mountinfo entries
  to be initialised properly.

  Additionally, the patch got the blessing of 'xnox' who looked at it
  and mention it looks fine to him.

  [Pending SRU]

  Note: No autopkgtests has been reported since systemd (21.5) ...
  between 21.5 and now (21.11) everything released has been about
  security fixes :

  systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU
  systemd (229-4ubuntu21.10) xenial-security; urgency=medium
  systemd (229-4ubuntu21.9) xenial-security; urgency=medium
  systemd (229-4ubuntu21.8) xenial-security; urgency=medium
  systemd (229-4ubuntu21.6) xenial-security; urgency=medium
  systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU

  
  Note: I don't know the level of adoption of Netplan in Xenial, but I suspect 
it is low as Netplan replaced ifupdown as the default configuration utility 
starting with Ubuntu 17.10 Artful only AFAIK.

  
  * Regression in autopkgtest for nplan (s390x): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz

  Error:
  modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.4.0-138-generic

  Justification:
  This above seems to be a recurrent failure since a couple of release already. 
This wasn't introduce by this particular SRU.

  I don't think having wifi module is relevant in s390x anyway, so most
  likely the module is not there on purpose for kernel w/ s390x
  architecture.

  * Regression in autopkgtest for nplan (amd64): test log
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz

  Error: (Ran on autopkgtest Ubuntu infra)
  test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could 
not create NMClient object: Cannot invoke method; proxy is for a well-known 
name without an owner and proxy was constructed with the 
G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL

  test_bridge_priority (__main__.TestNetworkManager) ... Error: Could
  not create NMClient object: Cannot invoke method; proxy is for a well-
  known name without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL

  test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create
  NMClient object: Cannot invoke method; proxy is for a well-known name
  without an owner and proxy was constructed with the
  G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL

  

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

2019-03-03 Thread Richard Laager
I was an affected user. I have confirmed that the package from bionic-
proposed works. I do not have any systems installed with Cosmic.

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

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

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

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

Bug description:
  [Impact]

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

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

  [Test Case]

  Start a Bionic or Cosmic VM.

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

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

  Run netplan apply or reboot. Wait ~10s.

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

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

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

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

  [Regression Potential]

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

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

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

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


[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

2019-03-03 Thread Woonjas
Seeing the same error on Dell Latitude e6520 on 18.04.2 LTS, 4.15.0-45
kernel

Not sure if it has any detrimental effects though

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1818448] [NEW] Segfault 0x00007ffff61978cb in QPixmap::size() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5

2019-03-03 Thread themusicgod1
Public bug reported:

start marble-qt
mouse-wheel in to zoom in
left click and drag the map
boom segfault

Thread 1 "marble-qt" received signal SIGSEGV, Segmentation fault.
0x761978cb in QPixmap::size() const () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
(gdb) bt
#0  0x761978cb in QPixmap::size() const () at 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#1  0x778be3d8 in  () at 
/usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28
#2  0x778c02cb in  () at 
/usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28
#3  0x77809a5a in Marble::MarbleMap::hasFeatureAt(QPoint const&) const 
() at /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28
#4  0x77856551 in 
Marble::MarbleDefaultInputHandler::adjustCursorShape(QPoint const&, QPoint 
const&) () at /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28
#5  0x7785793e in 
Marble::MarbleDefaultInputHandler::handleMouseEvent(QMouseEvent*) () at 
/usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.28
#6  0x758d268c in 
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x768da805 in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x768e264f in QApplication::notify(QObject*, QEvent*) () at 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x758d29a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x768e1622 in QApplicationPrivate::sendMouseEvent(QWidget*, 
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7693414b in  () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x769367ba in  () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x768da82c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x768e20f4 in QApplication::notify(QObject*, QEvent*) () at 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x758d29a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7611e523 in 
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
 () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#17 0x7611fff5 in 
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
 ()
at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x760f72eb in 
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
 () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x7fffe2eb91c0 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#20 0x7fffef0ed387 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fffef0ed5c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fffef0ed64c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7592b8ef in 
QEventDispatcherGlib::processEvents(QFlags) () 
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x758d09ea in 
QEventLoop::exec(QFlags) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x758d9a84 in QCoreApplication::exec() () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x555690f7 in  ()
#27 0x74cd7b97 in __libc_start_main (main=
0x55568030, argc=1, argv=0x7fffdf48, init=, 
fini=, rtld_fini=, stack_end=0x7fffdf38)
at ../csu/libc-start.c:310
#28 0x55569f5a in _start ()

thread 2
#0  0x709da9f3 in futex_wait_cancelable (private=, 
expected=0, futex_word=0x73eec114) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
88  ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.
(gdb) bt
#0  0x709da9f3 in futex_wait_cancelable (private=, 
expected=0, futex_word=0x73eec114) at 
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x709da9f3 in __pthread_cond_wait_common (abstime=0x0, 
mutex=0x557b26b0, cond=0x73eec0e8) at pthread_cond_wait.c:502
#2  0x709da9f3 in __pthread_cond_wait (cond=0x73eec0e8, 
mutex=0x557b26b0) at pthread_cond_wait.c:655
#3  0x7537679c in 
std::condition_variable::wait(std::unique_lock&) () at 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7322d0a7 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#5  0x7322d1e9 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#6  0x7537c57f in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x709d46db in start_thread (arg=0x7fffe40ac700) at 
pthread_create.c:463
#8  0x74dd788f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

(gdb) thread 3
[Switching to thread 3 (Thread 0x7fffe00ad700 (LWP 15390))]
#0  0x74dcabf9 in __GI___poll (fds=0x7fffe00acb68, nfds=1, timeout=-1) 
at 

[Touch-packages] [Bug 1760801] Re: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2019-03-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: dbus-python (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in dbus-python package in Ubuntu:
  Confirmed

Bug description:
  this error appeared during Ubuntu startup

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-dbus 1.2.0-3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Mar 26 14:45:49 2018
  DuplicateSignature:
   package:python3-dbus:1.2.0-3
   Setting up python3-apt (1.1.0~beta1ubuntu0.16.04.1) ...
   /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
   dpkg: error processing package python3-apt (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2018-03-07 (26 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: dbus-python
  Title: package python3-dbus 1.2.0-3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2019-03-03 Thread supersasho
Finaly I was able to get rid of the 30s delay.

TL;DR
1. Changed RESUME=UUID=... to RESUME=none in /etc/initramfs-tools/conf.d/resume 
(removing the file didn't help)
2. sudo update-initramfs -u

---
I've got a custom LVM layout.

$ cat /etc/lsb-release 
DISTRIB_ID=neon
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="KDE neon User Edition 5.15"

$ uname -r
4.15.0-45-generic

$ sudo apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.130ubuntu3.6
  Candidate: 0.130ubuntu3.6
...

$ sudo cat /etc/initramfs-tools/conf.d/resume 
RESUME=none

$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic

$

With "RESUME=UUID..." in /etc/initramfs-tools/conf.d/resume:
[3.418544] Btrfs loaded, crc32c=crc32c-intel
[3.487208] BTRFS: device fsid ... devid 1 transid 272021 
/dev/mapper/vg_00-lv_root
[   34.587759] BTRFS info (device dm-0): disk space caching is enabled


With "RESUME=none" in /etc/initramfs-tools/conf.d/resume:
[3.422572] Btrfs loaded, crc32c=crc32c-intel
[3.487216] BTRFS: device fsid ... devid 1 transid 272833 
/dev/mapper/vg_00-lv_root
[3.501201] BTRFS info (device dm-0): disk space caching is enabled

Hope it  helps someone.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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


[Touch-packages] [Bug 1572493] Re: pulseaudio 8.0 drops connections after playing audio in a firejail

2019-03-03 Thread Steve Dodd
I'm seeing this in a slightly different situation .. I'm running an xpra
server which starts its own pulseaudio server; something to do with
running Chrome and attempting to play video randomly results in
everything in /dev/shm getting deleted, which leads the shm errors
reported above.

I made sure to set RemoveIPC=no in /etc/systemd/logind.conf, but systemd
does not seem to be the culprit. I've tried using auditd to see what is
wiping the files, but nothing is showing.

Did anyone ever make any headway with this?

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

Title:
  pulseaudio 8.0 drops connections after playing audio in a firejail

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 15.10 to 16.04 (pulseaudio 6 -> 8), I
  notice that my audio output stops working every few hours.  When this
  happens, if I run pavucontrol, it seems to wait forever trying to
  connect to pulseaudio.  Killing pulseaudio and starting it again fixes
  the problem for a little while.

  I don't think anything fancy is needed to cause a hang; usually, I'm
  just using Chrome.

  This never happened with pulseaudio 6 over hundreds of hours of use.

  I am using the default pulseaudio config files on an HP EliteBook
  8460p, which has this audio sink:

  1 sink(s) available.
* index: 0
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
DYNAMIC_LATENCY
state: IDLE
suspend cause: 
priority: 9959
volume: front-left: 61870 /  94% / -1.50 dB,   front-right: 61870 /  
94% / -1.50 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 38.86 ms
max request: 6 KiB
max rewind: 64 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 371.52 ms
card: 1 
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "92HD81B1X5 Analog"
alsa.id = "92HD81B1X5 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xd452 irq 40"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1c20"
device.product.name = "6 Series/C200 Series Chipset Family High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "IDT 92HD81B1X5"
alsa.components = "HDA:111d7605,103c3588,00100105 
HDA:11c11040,103c3066,00100200"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-lineout: Line Out (priority 9900, latency offset 
0 usec, available: no)
properties:

analog-output-speaker: Speakers (priority 1, latency offset 
0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
active port: 



  # dpkg -l | grep pulse
  ii  libpulse-mainloop-glib0:amd64   1:8.0-0ubuntu3   amd64
PulseAudio client libraries (glib support)
  ii  libpulse0:amd64 1:8.0-0ubuntu3   amd64
PulseAudio client libraries
  ii  libpulse0:i386  1:8.0-0ubuntu3   i386 
PulseAudio client 

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-03-03 Thread Matthias Klose
** Also affects: jxgrabkey (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in afterburner.fx package in Ubuntu:
  New
Status in annotation-indexer package in Ubuntu:
  New
Status in apache-directory-server package in Ubuntu:
  New
Status in aspectj package in Ubuntu:
  New
Status in aspectj-maven-plugin package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in bridge-method-injector package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in ecj package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in elki package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in fontawesomefx package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gluegen2 package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hikaricp package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-core package in Ubuntu:
  New
Status in jackson-databind package in Ubuntu:
  New
Status in jackson-dataformat-xml package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javafxsvg package in Ubuntu:
  New
Status in javamail package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-classfilewriter package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jcommander package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jxgrabkey package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libapache-poi-java package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libcommons-compress-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjavaewah-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libjogl2-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libpdfbox2-java package in Ubuntu:
  New
Status in libpicocontainer-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libsambox-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libsejda-java package in Ubuntu:
  New
Status in libspring-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mavibot package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in 

[Touch-packages] [Bug 1818422] Re: Totem: DBus reports wrong .desktop file name

2019-03-03 Thread Amr Ibrahim
** Package changed: mesa (Ubuntu) => totem (Ubuntu)

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

Title:
  Totem: DBus reports wrong .desktop file name

Status in totem package in Ubuntu:
  New

Bug description:
  
  Totem - MPRIS2 - DBus-interface: 
  My application is asking Totem (video player) various data via (MPRIS2) 
DBus-interface.

  When asking "DesktopEntry", totem return value "totem" (meaning 
totem.desktop).  
  That is probably wrong.

  Ubuntu 19.10 has no "totem.desktop" file.
  $ updatedb
  $ locate totem.desktop

  The right answer would be "org.gnome.Totem". That is 
  /usr/share/applications/org.gnome.Totem.desktop

  Please see:
  
https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:Identity

  Please fix it.

  Kindly
Moma Antero

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

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


[Touch-packages] [Bug 1818422] Re: Totem: DBus reports wrong .desktop file name

2019-03-03 Thread moma
I meant the "totem" package, NOT mesa.

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

Title:
  Totem: DBus reports wrong .desktop file name

Status in mesa package in Ubuntu:
  New

Bug description:
  
  Totem - MPRIS2 - DBus-interface: 
  My application is asking Totem (video player) various data via (MPRIS2) 
DBus-interface.

  When asking "DesktopEntry", totem return value "totem" (meaning 
totem.desktop).  
  That is probably wrong.

  Ubuntu 19.10 has no "totem.desktop" file.
  $ updatedb
  $ locate totem.desktop

  The right answer would be "org.gnome.Totem". That is 
  /usr/share/applications/org.gnome.Totem.desktop

  Please see:
  
https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:Identity

  Please fix it.

  Kindly
Moma Antero

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

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


[Touch-packages] [Bug 1818422] [NEW] Totem: DBus reports wrong .desktop file name

2019-03-03 Thread moma
Public bug reported:


Totem - MPRIS2 - DBus-interface: 
My application is asking Totem (video player) various data via (MPRIS2) 
DBus-interface.

When asking "DesktopEntry", totem return value "totem" (meaning totem.desktop). 
 
That is probably wrong.

Ubuntu 19.10 has no "totem.desktop" file.
$ updatedb
$ locate totem.desktop

The right answer would be "org.gnome.Totem". That is 
/usr/share/applications/org.gnome.Totem.desktop

Please see:
https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:Identity

Please fix it.

Kindly
  Moma Antero

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

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

Title:
  Totem: DBus reports wrong .desktop file name

Status in mesa package in Ubuntu:
  New

Bug description:
  
  Totem - MPRIS2 - DBus-interface: 
  My application is asking Totem (video player) various data via (MPRIS2) 
DBus-interface.

  When asking "DesktopEntry", totem return value "totem" (meaning 
totem.desktop).  
  That is probably wrong.

  Ubuntu 19.10 has no "totem.desktop" file.
  $ updatedb
  $ locate totem.desktop

  The right answer would be "org.gnome.Totem". That is 
  /usr/share/applications/org.gnome.Totem.desktop

  Please see:
  
https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:Identity

  Please fix it.

  Kindly
Moma Antero

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

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


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

2019-03-03 Thread Dave Chiluk
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Cosmic:
  Fix Committed
Status in pulseaudio source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * User is only able to get mono audio from steelseries headsets
  because they provide both a stereo and mono output.  PA selects the
  mono output by default.

   * This should be backported to stable releases because this fix is 
 isolated to code that only applies to the affected headsets.  
 Additionally other gaming headsets may be more easily enabled by adding 
  ATTRS{idVendor}=="", ATTRS{idProduct}=="", 
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
 to /lib/udev/rules.d/90-pulseaudio.rules now.  Such as the Lucidsound 
 LS31 which I own.

   * The upload fixes the bug by conditionally setting a pulseaudio
  profile for the headset based on specific usb vendor and product ids
  in the udev rules.

  [Test Case]

   1. Acquire headset.
   2. Open sound settings, and click test speakers.
   3. Only option available will be mono sound

  [Regression Potential]

   * Risk of regressions should be mitigated to those who own the
  headset.  In which case it is likely that their headset is already not
  working.

  [Other Info]
   
   * All patches originate from upstream pulseaudio, and are documented as
 such including the shas.
   
   * I will be pursuing enabling other similar headsets in the coming weeks.
   * I plan to work with upstream pulseaudio to enable my own headset and to
 also make the headset templates backported here more generic.

  
   Original 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

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


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

2019-03-03 Thread Peter P.
I have the same problem on two machines running Ubuntu 18.04 with a Sony
WH-1000XM2.

-- 
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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

2019-03-03 Thread Till Kamppeter
Thanks Esko for your investigations. I have uploaded and appropriately
patched CUPS package for Bionic now. As soon as it gets approved you
will be asked for testing here. Please do the testing then and give us
feedback whether it solves your problem, so that we can make the fix an
official update for Bionic.

** Description changed:

+ [Impact]
+ 
+ If a print queue is set up with "auth-info-required=negotiate" because
+ the server requires authentication (for example Kerberos) the user is
+ asked for user name and password on every jon, insteaf of the
+ authentication working automatically. This worked correctly in 14.04 and
+ 16.04.
+ 
+ Also setting "AuthType Default" for "/" in cupsd.conf leads to be
+ prompted for a password on commands like "lpatat -a", even for root.
+ Works correctly in Xenial and Cosmic.
+ 
+ [Test Case]
+ 
+ Set up a queue pointing to a Kerberos-authenticated Windows server with
+ "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType
+ Default" for "/" in cupsd.conf. When printing or running other commands
+ accessing your print queue you will get prompted for credentials. With
+ the fix the authentication will get automatic again.
+ 
+ [Regression Potential]
+ 
+ Low, as the fix are simple one-line corrections taken from upstream.
+ 
+ [Original report]
  
  Hi,
  
  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems
  to be acting more like AuthInfoRequired username,password i.e. it
  prompts for a password when printing rather than using the available
  Kerberos credentials.
  
  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:
  
  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o
  printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS
  /hp-officejet_pro_476_576_series-ps.ppd"
  
  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as
  it's blocked by default) and the permissions on this file changed to 700
  (owner root) as per manpage instructions.
  
  When using lp -d printer /tmp/test.txt I get the following response:
  
  Password for myuid on localhost?
  
  Typing my password gets the job accepted to the queue but it does spool
  to the Windows Print Server and in the error_log file I can see
  
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set
  
  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)
  
  Any ideas how to fix this?
  
  Thanks,
  
  Ian.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  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
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
-  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
-  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
+  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

Title:
  [SRU] AuthInfoRequired 

[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

2019-03-03 Thread Till Kamppeter
debdiff of the fix.

** Patch added: "cups_2.2.7-1ubuntu2.3_2.2.7-1ubuntu2.4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+attachment/5243039/+files/cups_2.2.7-1ubuntu2.3_2.2.7-1ubuntu2.4.debdiff

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every jon, insteaf of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  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
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

2019-03-03 Thread Till Kamppeter
** Summary changed:

- AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
+ [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  
  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  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
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1818395] [NEW] Please demote lightdm greeter recommends to suggests

2019-03-03 Thread Sean Davis
Public bug reported:

Please see https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1754872/comments/25 for some background on this bug
report.

I'd like to request that the lightdm greeter Recommends...
unity-greeter | lightdm-greeter (virtual package) | lightdm-kde-greeter

be moved to Suggests. It seems the apt installation order causes unity-
greeter (and other unity components) to be installed along with lightdm-
gtk-greeter when installing the xubuntu-desktop task.

Since each of the lightdm greeters should depend on lightdm, I think
this change helps make greeter installation more explicit and should
prevent the installation of multiple greeters when only one is needed or
requested.

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

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

Title:
  Please demote lightdm greeter recommends to suggests

Status in lightdm package in Ubuntu:
  New

Bug description:
  Please see https://bugs.launchpad.net/ubuntu/+source/indicator-
  datetime/+bug/1754872/comments/25 for some background on this bug
  report.

  I'd like to request that the lightdm greeter Recommends...
  unity-greeter | lightdm-greeter (virtual package) | lightdm-kde-greeter

  be moved to Suggests. It seems the apt installation order causes
  unity-greeter (and other unity components) to be installed along with
  lightdm-gtk-greeter when installing the xubuntu-desktop task.

  Since each of the lightdm greeters should depend on lightdm, I think
  this change helps make greeter installation more explicit and should
  prevent the installation of multiple greeters when only one is needed
  or requested.

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

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


[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

2019-03-03 Thread Steve Roberts
Sorry, my bad, it seems I miss read the first part of the wiki! Now
installed, will report back.

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in resolvconf source package in Trusty:
  Invalid
Status in systemd source package in Trusty:
  Invalid
Status in resolvconf source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in resolvconf source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid
Status in resolvconf source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Invalid
Status in resolvconf source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Invalid

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.

  [test case]

  == upgrade from pre-bionic (e.g. xenial) to bionic or later ==

  1) create a xenial system with ifupdown/resolvconf.  The ifupdown
  config needs to include an upstream name server (either static or
  dynamic).  At this point, once the network is configured and up, the
  resolvconf should have put the upstream name server(s) and search
  domain into the /etc/resolv.conf.  As is usual for pre-systemd
  releases, there should be no local dns resolver in /etc/resolv.conf
  (i.e. 127.0.0.53 should not be included) at this point.

  2) upgrade the system to bionic (alternately it should be possible to install 
bionic, then remove netplan and install/configure ifupdown and resolvconf, but 
I have not specifically tested this).  The upgrade will retain the 
ifupdown/resolvconf configuration, and will not change to 
netplan/systemd-networkd.  After upgrade is finished, the /etc/resolv.conf will 
contain:
a) the upstream name server(s)
b) options edns0
c) the local stub resolver (127.0.0.53)
d) search domain

  the fixed resolvconf will remove (b) and (c), and restore
  /etc/resolv.conf to what it contained in Xenial release, before the
  upgrade to Bionic.

  As mentioned, this case also should cover the situation of a native
  Bionic install, where netplan is removed and ifupdown/resolvconf is
  manually installed.

  == bionic or later install ==

  with a bionic install, ifupdown is not installed, instead netplan
  /systemd-networkd handle networking.  In this case, systemd-networkd
  manages the /etc/resolv.conf, and symlinks it to networkd's stub-
  resolv.conf which always contains only the local stub resolver
  (127.0.0.53) and (recently) options edns0, and local search domain.

  If resolvconf is installed while systemd-networkd is managing the
  network, then currently the resolv.conf contents will remain
  completely unchanged, still pointing to the local stub resolver.

  This resolvconf change will alter that, to revert the /etc/resolv.conf
  to Xenial's contents; specifically, the upstream name server(s) and
  search domain.  It will no longer include the local stub resolver nor
  edns0.

  [regression potential]

  Regressions due to this change would likely be seen in dns query
  failures with other system configurations.

  Additionally, for the case where systemd-networkd is actually managing
  the network, this change will stop sending dns traffic to the local
  stub resolver, and instead send it to the upstream name server(s).
  This will increase outgoing dns traffic (since it's no longer cached
  locally), but will matches the behavior from Xenial.  Additionally,
  resolvconf should not be needed when systemd-networkd is managing the
  network (and thus systemd-resolved is managing dns), and resolvconf
  can simply be uninstalled from the system to move back to normal use
  of the local stub resolver.

  [other info]

  This affects only Bionic and later; in Xenial and earlier, resolvconf
  does not include the 'resolvconf-pull-resolved' service to pull in the
  systemd-resolved stub config, which is what causes this problem.

  This also does not affect Debian, as it does not include the
  'resolvconf-pull-resolved' service either.

  original description:

  --

  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  

[Touch-packages] [Bug 1785272] Re: ufw and gufw out of order

2019-03-03 Thread costales
This is an ufw issue. I'll derivate to that project.

** Project changed: gui-ufw => ufw (Ubuntu)

** Package changed: ufw (Ubuntu) => ufw

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

Title:
  ufw and gufw out of order

Status in ufw:
  New

Bug description:
  Hello,

  the sudo ufw status command gives:

  WARN: / is writable for everyone!
  WARN: / is writable for the group!

  and nothing else in the "flag" page of gufw. the "ufw" activity
  normally appears here!

  with "gufw" can not enable or disable "ufw".
  for that I have to use sudo ufw cds and enable or disable or status ...

  finally the comparison of the screen "gufw" with the result of the
  cdes gives results totally reversed !!!

  after complete désisntallation then reinstallation the result is
  always the same. it is to understand nothing more.

  i have two screenshots that highlight this malfunction but i do not
  know how to attach them to this message ...

  thanks for the help expected.

  greetings.

  Ray.

  then, after

  here is the result of the order: sudo systemctl status ufw.service

  ● ufw.service - Uncomplicated firewall
      Loaded: /lib/systemd/system/ufw.service; enabled; vendor preset: enabled
      Active: active (exited) since Fri 2018-08-03 13:39:12 CEST; 21min ago
     Process: 250 ExecStart = / lib / ufw / ufw-init start quiet (code = 
exited, status = 0 / SUCCESS)
  Main PID: 250 (code = exited, status = 0 / SUCCESS)
      CGroup: /system.slice/ufw.service

  August 03 13:39:12 ac2i-W240EU-W250EUQ-W270EUQ systemd [1]: Started 
Uncomplicated firewall.
  Warning: Journal has been rotated since it was started. Log output is 
incomplete or unavailable.

  also, after

  Re,

  actually but the operation via the gufw interface gives weird results.
  you can see the 2 screens images obtained thanks to the ufw cdes and the gufw 
screen ...
  here is the direct link for access to the shared folder: 
https://app.box.com/s/3q29ca27oebk788xqxlbjy2z4vd6idl6
  why say ufw is useless? faced with these problems I tried to install 
"firestarter" without result ...
  I think a firewall is a necessary evil nowadays. thank you.

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

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


[Touch-packages] [Bug 1785272] [NEW] ufw and gufw out of order

2019-03-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello,

the sudo ufw status command gives:

WARN: / is writable for everyone!
WARN: / is writable for the group!

and nothing else in the "flag" page of gufw. the "ufw" activity normally
appears here!

with "gufw" can not enable or disable "ufw".
for that I have to use sudo ufw cds and enable or disable or status ...

finally the comparison of the screen "gufw" with the result of the cdes
gives results totally reversed !!!

after complete désisntallation then reinstallation the result is always
the same. it is to understand nothing more.

i have two screenshots that highlight this malfunction but i do not know
how to attach them to this message ...

thanks for the help expected.

greetings.

Ray.

then, after

here is the result of the order: sudo systemctl status ufw.service

● ufw.service - Uncomplicated firewall
    Loaded: /lib/systemd/system/ufw.service; enabled; vendor preset: enabled
    Active: active (exited) since Fri 2018-08-03 13:39:12 CEST; 21min ago
   Process: 250 ExecStart = / lib / ufw / ufw-init start quiet (code = exited, 
status = 0 / SUCCESS)
Main PID: 250 (code = exited, status = 0 / SUCCESS)
    CGroup: /system.slice/ufw.service

August 03 13:39:12 ac2i-W240EU-W250EUQ-W270EUQ systemd [1]: Started 
Uncomplicated firewall.
Warning: Journal has been rotated since it was started. Log output is 
incomplete or unavailable.

also, after

Re,

actually but the operation via the gufw interface gives weird results.
you can see the 2 screens images obtained thanks to the ufw cdes and the gufw 
screen ...
here is the direct link for access to the shared folder: 
https://app.box.com/s/3q29ca27oebk788xqxlbjy2z4vd6idl6
why say ufw is useless? faced with these problems I tried to install 
"firestarter" without result ...
I think a firewall is a necessary evil nowadays. thank you.

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

-- 
ufw and gufw out of order
https://bugs.launchpad.net/bugs/1785272
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ufw 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 1818376] Re: run-parts tries to execute scripts in /usr/lib/systemd/system-sleep instead of /lib/systemd/system-sleep

2019-03-03 Thread Nyyr
Sorry, my mistake :-(

** Changed in: debianutils (Ubuntu)
   Status: New => Invalid

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

Title:
  run-parts tries to execute scripts in /usr/lib/systemd/system-sleep
  instead of /lib/systemd/system-sleep

Status in debianutils package in Ubuntu:
  Invalid

Bug description:
  Hello,

  while trying to make suspend to disk work on MacBook Pro 12,1 (early 2015) I 
found that brcmfmac
  module must be unloaded before hibernating. So I put brcmfmac script handling 
that into existing
  /lib/systemd/system-sleep where 2 script where already present (from hdparm 
and unattended-upgrades
  packages). After issuing systemctl hibernate command I found that the script 
was not executed.
  By looking into syslog I found an error:

  run-parts: failed to open directory /usr/lib/systemd/system-sleep: No
  such file or directory

  because /usr/lib/systemd/system-sleep directory indeed does not exist.

  After making an symlink named /usr/lib/systemd/system-sleep pointing
  to /lib/systemd/system-sleep it started to work as expected.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy debianutils
  debianutils:
Instalovaná verze: 4.8.4
Kandidát:  4.8.4
Tabulka verzí:
   *** 4.8.4 500
  500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: debianutils 4.8.4
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Mar  3 00:12:30 2019
  Dependencies:
   gcc-8-base 8.2.0-1ubuntu2~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.2.0-1ubuntu2~18.04
  InstallationDate: Installed on 2019-02-28 (1 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: debianutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1816404] Re: on_ac_power fails if the path contains a whitespace

2019-03-03 Thread Mathew Hodson
** Changed in: powermgmt-base (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  on_ac_power fails if the path contains a whitespace

Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  Codename: bionic
  powermgmt-base: 1.33

  on_ac_power fails if the path contains a whitespace, solution is
  attached as patch.

  before patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  cat: '/sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA': No 
such file or directory
  cat: 'Rev:PAACFS00-002-R003-battery/type': No such file or directory
  + type=
  1

  after patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + type=Battery
  + [ no = yes ]
  + [ -d /proc/acpi/ac_adapter ]
  + [ -r /proc/pmu/info ]
  + [ -r /proc/apm ]
  + exit 255
  255

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

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