[Desktop-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 Desktop
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: LENO

[Desktop-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 Desktop
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: LE

[Desktop-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 Desktop
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: LENOVO

[Desktop-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 Desktop
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: LENOVO
  dmi.

[Desktop-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 Desktop
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.

[Desktop-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 Desktop
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.

[Desktop-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 Desktop
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.vend

[Desktop-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 Desktop
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: LENOVO

[Desktop-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 Desktop
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: LENOVO
  dmi.

[Desktop-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 Desktop
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: LE

[Desktop-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 Desktop
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: LENO

[Desktop-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 Desktop
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.chas

[Desktop-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 Desktop
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.ch

[Desktop-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 Desktop
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.

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

[Desktop-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 Desktop
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: LENOVO
  dmi.chas

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

[Desktop-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 Desktop
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: LENOVO
 

[Desktop-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 Desktop
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: LENOVO
  dmi.ch

[Desktop-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 Desktop
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: LENOVO
  dmi.ch

[Desktop-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 Desktop
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: LENOVO
  dmi.

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

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

[Desktop-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 530S-14ARR

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1815957] Re: SynPS/2 Synaptics TouchPad: Read error 19

2019-03-03 Thread Kai-Heng Feng
Please attach dmesg without those kernel parameters.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1815957

Title:
  SynPS/2 Synaptics TouchPad: Read error 19

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hi

  Ubuntu 18.04 went into standby mode with the mouse plugged in.
  Then I've removed the mouse.

  A few hours later I wanted to continue work (without mouse) and woke up my PC 
from standby mode.
  Unfortunately the touchpad did not work.

  So I put Ubuntu back into standby mode, plugged in a mouse and woke it up 
again.
  Both Touchpad and mouse worked perfectly again.

  Regards,

  Ettore Atalan
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ben7239 F pulseaudio
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built
   tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed
   tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 5986:055c Acer, Inc 
   Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RZ
  Package: xserver-xorg-input-libinput 0.27.1-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash 
acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic ubuntu ubuntu
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.09
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W65_W67RZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Jan 21 20:00:45 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2

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

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


[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1818470] [NEW] Screen locking issue

2019-03-03 Thread rdlong
Public bug reported:

I started installation of new software (Sound Juicer). I went away from my 
computer (before the screen asking for PW to install new software appeared) for 
more than 30 minutes, and the computer suspended.
I touched the keyboard to bring it out of suspend. 
It went into a strange state. The password dialog was visble. When I entered my 
password, it brought up the task bar, but no windows. I could click on tasks, 
see the names of windows if there were multiple ones open (like OpenOffice), 
close tasks, and start them,but nothing would show a window. 
I tried cancel, relogging in as myself, was finally forced to reboot.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-8ubuntu3
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
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  3 21:29:02 2019
InstallationDate: Installed on 2018-06-21 (255 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: Upgraded to bionic on 2018-11-18 (105 days ago)

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1818470

Title:
  Screen locking issue

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  I started installation of new software (Sound Juicer). I went away from my 
computer (before the screen asking for PW to install new software appeared) for 
more than 30 minutes, and the computer suspended.
  I touched the keyboard to bring it out of suspend. 
  It went into a strange state. The password dialog was visble. When I entered 
my password, it brought up the task bar, but no windows. I could click on 
tasks, see the names of windows if there were multiple ones open (like 
OpenOffice), close tasks, and start them,but nothing would show a window. 
  I tried cancel, relogging in as myself, was finally forced to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 21:29:02 2019
  InstallationDate: Installed on 2018-06-21 (255 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to bionic on 2018-11-18 (105 days ago)

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

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


[Desktop-packages] [Bug 1208225] Re: nautilus crashed with SIGABRT in _g_log_abort()

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1208225

Title:
  nautilus crashed with SIGABRT in _g_log_abort()

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  nautilus crashed with SIGABRT in g_assertion_message()

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12-0ubuntu2
  Architecture: amd64
  Date: Sun Aug  4 20:13:35 2013
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'839x550+381+182'"
  InstallationDate: Installed on 2013-08-03 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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


[Desktop-packages] [Bug 1435756] Re: nautilus crashed with signal 5 in _XEventsQueued()

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1435756

Title:
  nautilus crashed with signal 5 in _XEventsQueued()

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Linux kylea-HP-Spectre-XT-Ultrabook-PC 3.16.0-33-generic #44-Ubuntu
  SMP Thu Mar 12 12:19:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  
  Distributor ID:   Ubuntu
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  Codename: vivid

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  Date: Mon Mar 23 18:14:16 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-14 (9 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/bin/nautilus
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to vivid on 2015-03-14 (9 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 1160451] Re: f2 (rename) bug in ubuntu 12.10 unity nautilus

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1160451

Title:
  f2 (rename) bug in ubuntu 12.10 unity nautilus

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  The probelm is the F2 key only works when you open fresh Nautilus,
  i like to work with Split view(f3), but then F2 only works  with certain 
files, not all.
  i am uploading the video. 
  In the view I AM PRESSING F2 after each selection with mouse. You would see 
that files work and DO NOT work under different circumstances.

  
  thank you

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

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


[Desktop-packages] [Bug 1471748] Re: Nautilus crashes while launching

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1471748

Title:
  Nautilus crashes while launching

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  System: Ubuntu 14.10, 15.04
  I wanted to start Nautilus as root thru terminal and I had recieved following 
error messages before crashing:

  # nautilus /

  (nautilus:5982): Gtk-WARNING **: Failed to register client: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (nautilus:5982): GLib-GObject-WARNING **: invalid cast from 
'GtkMessageDialog' to 'NautilusWindow'
  **
  ERROR:nautilus-window.c:2116:nautilus_window_get_slots: assertion failed: 
(NAUTILUS_IS_WINDOW (window))
  Aborted

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

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


[Desktop-packages] [Bug 1085212] Re: Evince and other gnome applications do not have print enabled

2019-03-03 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gedit (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085212

Title:
  Evince and other gnome applications do not have print enabled

Status in evince package in Ubuntu:
  Expired
Status in gedit package in Ubuntu:
  Expired

Bug description:
  Even though I have a printer setup, the print menu is disabled in
  evince.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evince 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 30 16:01:03 2012
  InstallationDate: Installed on 2011-10-03 (424 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: Upgraded to quantal on 2012-09-17 (74 days ago)

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

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


[Desktop-packages] [Bug 1085212] Re: Evince and other gnome applications do not have print enabled

2019-03-03 Thread Launchpad Bug Tracker
[Expired for evince (Ubuntu) because there has been no activity for 60
days.]

** Changed in: evince (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085212

Title:
  Evince and other gnome applications do not have print enabled

Status in evince package in Ubuntu:
  Expired
Status in gedit package in Ubuntu:
  Expired

Bug description:
  Even though I have a printer setup, the print menu is disabled in
  evince.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evince 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 30 16:01:03 2012
  InstallationDate: Installed on 2011-10-03 (424 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: Upgraded to quantal on 2012-09-17 (74 days ago)

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

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


[Desktop-packages] [Bug 1156176] Re: package gedit 3.6.1-0ubuntu1 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2

2019-03-03 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gedit (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1156176

Title:
  package gedit 3.6.1-0ubuntu1 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 2

Status in gedit package in Ubuntu:
  Expired

Bug description:
  je ne sais pas comment traiter cette information :

"Une erreur s'est produite, les détails suivants sont donnés :
  E : gedit : le sous-processus script post-installation installé a 
retrouvé une erreur de sortie d'état 2 "

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: gedit 3.6.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Sun Mar 17 12:17:24 2013
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 2
  InstallationDate: Installed on 2011-10-20 (513 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric" - Build i386 LIVE Binary 
20111013-11:02
  MarkForUpload: True
  SourcePackage: gedit
  Title: package gedit 3.6.1-0ubuntu1 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 2
  UpgradeStatus: Upgraded to quantal on 2013-01-17 (59 days ago)

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

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


[Desktop-packages] [Bug 1571418] Re: wrong folder name when creating new folder with ( . ) dot prefix

2019-03-03 Thread Launchpad Bug Tracker
[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1571418

Title:
  wrong folder name when creating new folder  with ( . ) dot prefix

Status in One Hundred Papercuts:
  Expired
Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Hi. The problem is that when i create a folder with dot ( . ) prefix
  in nautilus , and after pressing Enter button it shows (Untitled
  Folder) instead of the folder name.

  I mean for example i create a folder with name ( .mymovies ) and after i 
press Enter button , the folder name is ( Untitled Folder )
  Until  I  refresh the nautilus page and folder gets hidden as expected.

  you can see that in pictures that i upload with this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.365
  CurrentDesktop: Unity
  Date: Sun Apr 17 20:46:50 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1427739] Re: nautilus crashed with SIGABRT in g_assertion_message()

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1427739

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 16:30:12 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-02-15 (16 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: nautilus -n
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1007600] Re: Thunderbird freezes when Internet is disable.

2019-03-03 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1007600

Title:
  Thunderbird freezes when Internet is disable.

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  Hi,

  I’ve openned Thunderbird since I was on a “free-wifi” connection unset: each 
connection to the Internet were redirected to a page asking to type a 
login/password of the Internet service provider.  Thunderbird was trying to 
connect to each of my account and of course got no correct response.  I guess a 
normal behavior would have been to switch to “offline-mode”, but Thunderbird 
did not really response (it update the screen when I move it, but I could do 
anything with the interface — even make it switch to offline mode!).
  I’ve thus disable the Internet.  Thunderbird just froze.

  I do not know what did happens, but when I killed Thunderbird (after
  Apport collected informations), enable Internet *and* give my
  login/password to the Internet service provider, then start
  Thunderbird, it works well.

  It seems that there are some problem left with such connections.

  Hoping that can help.
  Martin.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: thunderbird 12.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 2130 F pulseaudio
  BuildID: 20120430060637
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf460 irq 48'
     Mixer name : 'Nvidia MCP77/78 HDMI'
     Components : 'HDA:10ec0662,15580806,00100101 
HDA:10de0003,10de0101,0010'
     Controls  : 29
     Simple ctrls  : 14
  Channel: release
  CheckboxSubmission: 01a18e0a74cbde3d34a62f62830ed079
  CheckboxSystem: f134069bba098730d27f59b402920826
  Date: Fri Jun  1 22:25:34 2012
  ExecutablePath: /usr/lib/thunderbird/thunderbird-bin
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Messaging Menu and Unity Launcher integration - 
ID=messagingm...@mozilla.com, Version=0.9.3, minVersion=3.3a1pre, 
maxVersion=12.0a1, Location=app-global, Type=extension, Active=Yes
   EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9, 
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension, 
Active=Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:

  Profiles: Profile0 (Default) - LastVersion=12.0.1/20120430060637 (Running)
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to precise on 2012-05-07 (25 days ago)
  dmi.bios.date: 05/27/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.02.23
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: M740TU(N)/M760TU(N)/W7X0TUN
  dmi.board.vendor: CLEVO Co.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.02.23:bd05/27/2009:svnCLEVOCO.:pnM740TU(N)/M760TU(N)/W7X0TUN:pvrNotApplicable:rvnCLEVOCo.:rnM740TU(N)/M760TU(N)/W7X0TUN:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: M740TU(N)/M760TU(N)/W7X0TUN
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

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

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


[Desktop-packages] [Bug 1490442] Re: nautilus crashes when i change wallpaper

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1490442

Title:
  nautilus crashes when i change wallpaper

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  nautilus crashes when i change a few wallpaper or just one. Nemo is also 
falls.
  Sorry for bad English.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu9.1 [modified: 
usr/share/applications/nautilus-folder-handler.desktop 
usr/share/applications/nautilus-home.desktop 
usr/share/applications/nautilus.desktop 
usr/share/applications/org.gnome.Nautilus.desktop]
  ProcVersionSignature: Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-27-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 31 13:44:45 2015
  InstallationDate: Installed on 2013-05-08 (844 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [deleted]

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

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


[Desktop-packages] [Bug 1034082] Re: Dvdrw/cdrw's won't unmount after problems blanking or ejecting

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1034082

Title:
  Dvdrw/cdrw's won't unmount after problems blanking or ejecting

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Tried blanking a dvdrw, wouldn't read the dvd, had to eject
  forcefully, but the volume still lists in the devices column of
  nautilus and won't allow me to "unmount" even though the drive is
  empty.. nor will it allow me to mount..

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21
  Uname: Linux 3.2.0-27-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  Date: Tue Aug  7 13:23:20 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '1274x747+-227+76'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 235
   org.gnome.nautilus.window-state start-with-status-bar true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2012-07-15 (22 days ago)

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

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


[Desktop-packages] [Bug 1057757] Re: Right Click menu is not visible

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1057757

Title:
  Right Click menu is not visible

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  When I try to right click on the file the drop down is not visible even in 
firefox browser but if I right click and ( to open a new tab) press "T" then 
it's working. But the problem is the right click menu is not visible. It's 
really irritating much, I restarted my system so many times still it's the 
same. I viewed this question 
http://askubuntu.com/questions/193802/cant-right-click-copy-or-move-files-to-desktop
 and did as someone answered that question i.e ( command: gsettings set 
org.gnome.desktop.background show-desktop-icons true ) still it's not working.
  Fortunately when I right click on the desktop the menu is visible, but when I 
right click a file or a link it's not visible

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

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


[Desktop-packages] [Bug 1061478] Re: Clicking on search button after searching on a samba folder returns to home folder instead of samba folder

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1061478

Title:
  Clicking on search button after searching on a samba folder returns to
  home folder instead of samba folder

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  If you do a search on a samba folder in nautilus and press again on
  the search button after the search is completed you go back to the
  home folder instead of the samba folder where you did the search.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Thu Oct  4 11:07:10 2012
  EcryptfsInUse: Yes
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '800x550+0+24'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 175
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to precise on 2011-10-13 (356 days ago)

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

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


[Desktop-packages] [Bug 1409833] Re: errors while opening /var/crash on 14.10

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1409833

Title:
  errors while opening /var/crash on 14.10

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I got these errors while opening /var/crash with a terminal:

  :~$ sudo nautilus /var/crash
  Unable to initialize DBus connection: Impossibile connettersi: Connessione 
rifiutata
  (nautilus:3354): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_export: 
assertion 'G_IS_DBUS_CONNECTION (connection)' failed

  (nautilus:3354): libunity-CRITICAL **: unity-launcher.vala:154: Unable
  to connect to session bus: Impossibile connettersi: Connessione
  rifiutata

  (nautilus:3354): libunity-CRITICAL **: unity-launcher.vala:154: Unable
  to connect to session bus: Impossibile connettersi: Connessione
  rifiutata

  (nautilus:3354): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Impossibile connettersi: Connessione rifiutata

  (nautilus:3354): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: 
Impossibile connettersi: Connessione rifiutata
  --- 
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-10-16 (88 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Package: nautilus 1:3.10.1-0ubuntu15
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Tags:  utopic
  Uname: Linux 3.16.0-29-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-12-21 (22 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1567818] Re: appearance of nautilus is wrong

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1567818

Title:
  appearance of nautilus is wrong

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I used to have a nautilus window with a menu in the title bar. After
  the last update, I got a nautilus window with no menu in the title
  bar, but instead an arrow down button on the top right. Also, the
  characters in all windows are more pixelated than I'm used to. I found
  that I can resolve this by changing the theme to Radiance, log out,
  log in, change the theme back to Ambiance. Then I have better
  characters and the right Nautilus appearance. Every time I reboot my
  computer, I have to do this. see screenshots.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  8 09:59:24 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-12-13 (116 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1013651] Re: Cannot paste into a usb device until every other opening.

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1013651

Title:
  Cannot paste into a usb device until every other opening.

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  After downloading and installing Ubuntu Linux 12.04 LTS, I found that
  I cannot cut and paste a file onto my USB external hard drive until I
  close it and open it for a second time. This happens every other time;
  ie, every second time that I opened my USB external hard drive, I then
  can cut and paste; but, not before.  I expect to cut and paste after
  each time that I open a USB external hard drive.

  OS:
   Ubuntu Linux 12.04 LTS

  Nautilus:
Installed: 1:3.4.2-0ubuntu2
Candidate: 1:3.4.2-0ubuntu2
Version table:
   *** 1:3.4.2-0ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.4.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jun 15 05:48:15 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '887x470+791+551'
   org.gnome.nautilus.window-state sidebar-width 198
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1052766] Re: eSATA does not automount

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1052766

Title:
  eSATA does not automount

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have an eSATA drive that used to automount (entries are in fstab
  file) in 10.04 when connected to AHCI eSATA port.

  In 12.04 Gnome Fallback drive is recognised in dmesg logs when
  connected but partitions no longer automount.

  USB devices automount, but not eSATA.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  CheckboxSubmission: 212f016c580cd6ab8528ceeed43cfd4f
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Wed Sep 19 16:02:58 2012
  GsettingsChanges: org.gnome.nautilus.window-state geometry '1035x784+308+146'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1169307] Re: compare, dropbox, rename: none working

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1169307

Title:
  compare, dropbox, rename: none working

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  nautilus-compare
  nautilus-dropbox and
  mass-rename

  none of the above appear in my Nautilus 3.6 menus.

  I'm using Ubuntu Gnome, Raring 13.04 beta.

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

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


[Desktop-packages] [Bug 1434491] Re: nautilus crashed with SIGSEGV

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1434491

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  this error happened after I have disconnected my usb pendrive

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Mar 20 11:08:53 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-12 (7 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f1d26ebeb43:mov0x30(%rbx),%rdi
   PC (0x7f1d26ebeb43) ok
   source "0x30(%rbx)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: Upgraded to vivid on 2015-03-12 (7 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 995912] Re: File browser window pop up every time when autofs5 mount a file system

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/995912

Title:
  File browser window pop up every time when autofs5 mount a file system

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Package autofs5 is set up to manage some mounts under /data.

  There are NFS4 mounts and also some local Ext4 mounts.

  And every time one of the Ext4 were mounted, a nautilus browser window
  is going to be pop up. This is a new behavior, until Oneirc only
  mounts under /media were recognized.

  This is very annoying, also
  > gconftool-2 --type bool --set 
/apps/nautilus/preferences/media_automount_open false
  did not work for me.

  Your Alex

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Mon May  7 13:46:18 2012
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '949x605+969+0'
   org.gnome.nautilus.window-state sidebar-width 144
   org.gnome.nautilus.window-state start-with-status-bar true
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1571418] Re: wrong folder name when creating new folder with ( . ) dot prefix

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1571418

Title:
  wrong folder name when creating new folder  with ( . ) dot prefix

Status in One Hundred Papercuts:
  Expired
Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Hi. The problem is that when i create a folder with dot ( . ) prefix
  in nautilus , and after pressing Enter button it shows (Untitled
  Folder) instead of the folder name.

  I mean for example i create a folder with name ( .mymovies ) and after i 
press Enter button , the folder name is ( Untitled Folder )
  Until  I  refresh the nautilus page and folder gets hidden as expected.

  you can see that in pictures that i upload with this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.365
  CurrentDesktop: Unity
  Date: Sun Apr 17 20:46:50 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1424204] Re: nautilus crashed with SIGSEGV in magazine_cache_trim()

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1424204

Title:
  nautilus crashed with SIGSEGV in magazine_cache_trim()

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  I have no idea why.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  Uname: Linux 3.18.3-031803-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Feb 21 16:39:22 2015
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2014-10-16 (127 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141016)
  ProcCmdline: nautilus /home/username/Pobrane
  SegvAnalysis:
   Segfault happened at: 0x7f4f43e447ee:mov(%r8),%r9
   PC (0x7f4f43e447ee) ok
   source "(%r8)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r9" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_slice_free1()
  UpgradeStatus: Upgraded to vivid on 2015-01-23 (28 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1462580] Re: package gedit 3.10.4-0ubuntu10 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/gedit/plugins/zeitgeist.plugin', which is also in package

2019-03-03 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gedit (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1462580

Title:
  package gedit 3.10.4-0ubuntu10 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/gedit/plugins/zeitgeist.plugin',
  which is also in package gedit-plugins 3.16.0-0ubuntu1~vivid1

Status in gedit package in Ubuntu:
  Expired

Bug description:
  package gedit 3.10.4-0ubuntu10 failed to install/upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/gedit/plugins/zeitgeist.plugin',
  which is also in package gedit-plugins 3.16.0-0ubuntu1~vivid1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: gedit 3.10.4-0ubuntu10
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Fri Jun  5 23:14:31 2015
  DuplicateSignature: package:gedit:3.10.4-0ubuntu10:trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gedit/plugins/zeitgeist.plugin', which is also in 
package gedit-plugins 3.16.0-0ubuntu1~vivid1
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gedit/plugins/zeitgeist.plugin', which is also in 
package gedit-plugins 3.16.0-0ubuntu1~vivid1
  InstallationDate: Installed on 2014-05-28 (373 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: gedit
  Title: package gedit 3.10.4-0ubuntu10 failed to install/upgrade: trying to 
overwrite '/usr/lib/x86_64-linux-gnu/gedit/plugins/zeitgeist.plugin', which is 
also in package gedit-plugins 3.16.0-0ubuntu1~vivid1
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (43 days ago)

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

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


[Desktop-packages] [Bug 1119311] Re: 13.04 Graphical corruption of icons

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1119311

Title:
  13.04 Graphical corruption of icons

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Some file/folder icons and shortcuts within Files (Nautilus) appear
  corrupted or show the incorrect icon until I "mouse over" them.
  Please see attached image.  In the image, I have blurred some of the
  folder names on purpose; these are not graphical faults.  I have drawn
  red boxes around two areas which should be showing folder icons.  Also
  see the Home shortcut on the left that is corrupted.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.02.07-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
  Uname: Linux 3.8.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Fri Feb  8 11:02:39 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:022e]
  InstallationDate: Installed on 2013-02-05 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130205)
  MachineType: Dell Inc. XPS M1530
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-5-generic 
root=UUID=4dba86b1-346e-462c-97fe-e03c26362d65 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: XPS M1530
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.02.07-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.0-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2

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

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


[Desktop-packages] [Bug 1033569] Re: nautilus crashed with SIGABRT in g_assertion_message()

2019-03-03 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1033569

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Just moving some files from one samba share to another...

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
  Uname: Linux 3.5.0-8-generic x86_64
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  Date: Mon Aug  6 19:20:28 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+344+270'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120805.1)
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: nautilus crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (compiz:1406): GConf-CRITICAL **: gconf_client_add_dir: assertion 
`gconf_valid_key (dirname, NULL)' failed
   (nautilus:1425): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: 
assertion `handler_id > 0' failed
   (nautilus:1425): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: 
assertion `handler_id > 0' failed

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

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


[Desktop-packages] [Bug 1306992] Re: line numbers are cut off

2019-03-03 Thread Launchpad Bug Tracker
[Expired for gedit (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gedit (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1306992

Title:
  line numbers are cut off

Status in gedit package in Ubuntu:
  Expired

Bug description:
  Line numbers are being visually cut off on the left hand side. See
  screenshot.

  I can get it to work again by turning off line numbers, closing gedit,
  reopening it, and then reenabling line numbers.

  However, if I close gedit and reopen it again, line numbers are again
  cut off. Something seems to be going wrong when the line numbers
  preference is enabled at gedit start up.

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

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


[Desktop-packages] [Bug 894387] Re: "Include an attachment" tooltip appears over file chooser window and does not ever disappear

2019-03-03 Thread Launchpad Bug Tracker
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/894387

Title:
  "Include an attachment" tooltip appears over file chooser window and
  does not ever disappear

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  There seems to be a race condition around the tooltip for "Include an
  attachment."  If you click on the Add Attachment button before the
  tooltip appears, but presumably as it's being prepared, the tooltip
  shows over top of the modal file chooser window, and over top of any
  other application.  If the tooltip is already showing when you click
  on Add Attachment, this does not occur.

  This does not appear to be specific to Unity or compiz, as I've run
  metacity --replace and reproduced this same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 7.0.1+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia wl
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: Cirrus Analog [Cirrus Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sian   1562 F pulseaudio
   /dev/snd/pcmC0D0p:   sian   1562 F...m pulseaudio
  BuildID: 20110929181644
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xd348 irq 23'
 Mixer name : 'Nvidia MCP89 HDMI'
 Components : 'HDA:10134206,106b0d00,00100301 
HDA:10de000c,10de0101,00100200'
 Controls  : 29
 Simple ctrls  : 13
  Channel: release
  Date: Thu Nov 24 13:38:49 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  IpRoute:
   default via 10.45.43.1 dev eth1  proto static 
   10.45.43.0/24 dev eth1  proto kernel  scope link  src 10.45.43.80  metric 2 
   169.254.0.0/16 dev eth1  scope link  metric 1000
  Prefs:
   places.database.lastMaintenance - 1321953301
   extensions.lastAppVersion - 7.0.1
   network.cookie.prefsMigrated - true
   places.history.expiration.transient_current_max_pages - 118303
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929181644 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to oneiric on 2011-11-07 (16 days ago)
  dmi.bios.date: 06/01/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP71.88Z.0039.B0B.1006012305
  dmi.board.name: Mac-F222BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F222BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0B.1006012305:bd06/01/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8:
  dmi.product.name: MacBookPro7,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

2019-03-03 Thread Lonnie Lee Best
I just install Ubuntu 18.04 in a virtual machine and updated it. I don't see a 
fix, I see the same disappointment:
https://i.imgur.com/tTanPlv.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1687246

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

Status in Mutter:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"

  After restarting your computer, you should find additional scale
  options in Settings > Devices > Displays.

  If you change your mind and want to get back to supported status, run:

  gsettings reset org.gnome.mutter experimental-features

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

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


[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

2019-03-03 Thread Lonnie Lee Best
Is this really fixed in Ubuntu 18.04? I don't want to waste my time
upgrading again unless fractional scaling truly supported.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1687246

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

Status in Mutter:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

  Workaround
  ==
  You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS 
by running the following command in a terminal and then restarting your 
computer. Note that this is an experimental feature and is not fully supported 
by either Ubuntu or GNOME.

  gsettings set org.gnome.mutter experimental-features "['scale-monitor-
  framebuffer']"

  After restarting your computer, you should find additional scale
  options in Settings > Devices > Displays.

  If you change your mind and want to get back to supported status, run:

  gsettings reset org.gnome.mutter experimental-features

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

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


[Desktop-packages] [Bug 1817335] Re: Freeze when changing the volume with the mouse wheel

2019-03-03 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1817546 ***
https://bugs.launchpad.net/bugs/1817546

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1817335

Title:
  Freeze when changing the volume with the mouse wheel

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  = Problem =
  Since today 2019-02-22 after upgrade:

  * Ubuntu (Gnome) desktop freeze when changing the volume with mouse wheel, no 
keyboard/mouse input possible, hard reboot or restart gdm over ssh required
  * (possibly related?) gnome-shell extensions {system-monitor, SomaFM internet 
radio} not working anymore

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

  apt-cache policy gnome-shell
  gnome-shell:
Installiert:   3.31.90-1ubuntu1
Installationskandidat: 3.31.90-1ubuntu1
Versionstabelle:
   *** 3.31.90-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu disco-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.2-2ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-10-02 (145 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181001)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.31.90-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags: wayland-session disco package-from-proposed third-party-packages
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2018-12-19 (67 days ago)
  UserGroups: adm cdrom davfs2 dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-10-02 (145 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181001)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.31.90-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags: disco package-from-proposed third-party-packages
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2018-12-19 (67 days ago)
  UserGroups: adm cdrom davfs2 dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-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 Desktop
Packages, which is subscribed to clutter-gst-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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1818315] Re: Can't install applications: "E: could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)"

2019-03-03 Thread Qasim Ali
Eventually, I got an upgrade notification (it listed a bunch of packages
which were scheduled to be updated). I assume whatever process was doing
silent updates in the background grabbed the lock, and once I closed the
dialog software centre was able to install packages.

Some sort of communication between that background upgrade system and
gnome-software would probably help alleviate this sort of confusion.

Thanks,
Qasim

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1818315

Title:
  Can't install applications: "E: could not get lock /var/lib/dpkg/lock-
  frontend - open (11: Resource temporarily unavailable)"

Status in gnome-software package in Ubuntu:
  New

Bug description:
  1. Start Software Center. 
  2. Select an application to install
  3. Click install

  Expected: application installs
  Actual: error message "E: could not get lock /var/lib/dpkg/lock-frontend - 
open (11: Resource temporarily unavailable)" (see attached screenshot)

  Solutions attempted:

  1. Closing and re-opening software center
  2. Checking 'updates' tab in software center ('Software is up to date')

  ---

  Version information:

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

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.8
Version table:
   *** 3.28.1-0ubuntu4.18.04.8 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 20:06:51 2019
  InstallationDate: Installed on 2019-01-20 (40 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-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 Desktop
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
  /graphics-driv

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-03-03 Thread Fink Nottle
@Alberto, with prime-select intel as well as with bbswitch off, powertop
shows the nvidia tunable as "good". Still, the battery's discharge rate
on idle remains pretty high (around 20W) on prime-select intel. With
bbswitch off, it drops to 13W or thereabouts. Do you need any more
information ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

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

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


[Desktop-packages] [Bug 1818454] [NEW] Xorg Segmentation Fault - Lightdm Error with i3-8100T 16.04-hwe

2019-03-03 Thread moe613
Public bug reported:

Issues with latest Coffee lake i3-8100T

Unable to start Lightdm on Ubuntu 16.04 with HWE kernel
4.15.0-45-generic and i915.alpha_support=1

When starting lightdm, Xorg throws a segmentation fault:

X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-128-generic x86_64 Ubuntu
Current Operating System: Linux coincloud221 4.15.0-45-generic 
#48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=bcc6c4a2-773a-4430-bf99-addfe22f344c ro quiet splash 
i915.alpha_support=1 vt.handoff=7
Build Date: 10 August 2018  09:33:05AM
xorg-server 2:1.18.4-0ubuntu0.8 (For technical support please see 
http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar  3 18:55:49 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a9cde916ce]
(EE) 1: /usr/lib/xorg/Xorg (0x55a9cdcdf000+0x1b6a69) [0x55a9cde95a69]
(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb6cf863000+0x354b0) 
[0x7fb6cf8984b0]
(EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fb6cba24000+0x75dad) 
[0x7fb6cba99dad]
(EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fb6cba24000+0x40d4c) 
[0x7fb6cba64d4c]
(EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fb6cba24000+0x42cc1) 
[0x7fb6cba66cc1]
(EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fb6cba24000+0x46179) 
[0x7fb6cba6a179]
(EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fb6cba24000+0x4968e) 
[0x7fb6cba6d68e]
(EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fb6cba24000+0x3a13f) 
[0x7fb6cba5e13f]
(EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fb6cba24000+0x3a342) 
[0x7fb6cba5e342]
(EE) 10: /usr/lib/xorg/Xorg (0x55a9cdcdf000+0x13d341) [0x55a9cde1c341]
(EE) 11: /usr/lib/xorg/Xorg (0x55a9cdcdf000+0x4fd47) [0x55a9cdd2ed47]
(EE) 12: /usr/lib/xorg/Xorg (0x55a9cdcdf000+0x53d9f) [0x55a9cdd32d9f]
(EE) 13: /usr/lib/xorg/Xorg (0x55a9cdcdf000+0x57e13) [0x55a9cdd36e13]
(EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7fb6cf883830]
(EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x55a9cdd21069]
(EE)
(EE) Segmentation fault at address 0x7c
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
(EE)
(II) AIGLX: Suspending AIGLX clients for VT switch
(EE) Server terminated with error (1). Closing log file.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1818454

Title:
  Xorg Segmentation Fault - Lightdm Error with i3-8100T 16.04-hwe

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Issues with latest Coffee lake i3-8100T

  Unable to start Lightdm on Ubuntu 16.04 with HWE kernel
  4.15.0-45-generic and i915.alpha_support=1

  When starting lightdm, Xorg throws a segmentation fault:

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-128-generic x86_64 Ubuntu
  Current Operating System: Linux coincloud221 4.15.0-45-generic 
#48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=bcc6c4a2-773a-4430-bf99-addfe22f344c ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  Build Date: 10 August 2018  09:33:05AM
  xorg-server 2:1.18.4-0ubuntu0.8 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar  3 18:55:49 2019
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a9cde916ce]
  (EE) 1: /usr/lib/xorg/Xorg (0x55a9cdcdf000+0x1b6a69) [0x55a9cde95a69]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb6cf863000+0x354b0) 
[0x7fb6cf8984b0]
  (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.s

[Desktop-packages] [Bug 1818434] Re: Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1817223 ***
https://bugs.launchpad.net/bugs/1817223

I can reproduce this issue with gnome-software 3.31 but I can't
reproduce this bug with gnome-software 3.30.

I believe you'll find that this bug will be fixed when bug 1817223 is
fixed. :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus

2019-03-03 Thread Rachel Greenham
Bug only affects X11 sessions.

I had a random urge to try out Wayland again. This issue does not arise
in Wayland. Apps that were affected under X11 are taking input focus
quite happily when launched from shell in Wayland.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1817924

Title:
  apps launched from gnome shell do not get input focus

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Observed on upgrading to disco-proposed today...

  When launching an app from the dock or from the applications grid (so
  i believe it's a gnome-shell thing rather than a dock thing), the app
  opens, but does not get the input focus. You have to either click in
  the window, or clicking again on the icon of the running app in the
  dock works, to give it focus. An extra step my muscle memory isn't
  prepared for!

  It seems like the sort of thing that might be an option rather than a
  bug, but if so, changing this behaviour back to its previous default
  is not at all obvious (I haven't found a way). So guessing it is a
  bug. NB: After launching an app this way, *no* window has focus. It is
  lost by the app that had it before, but not given to the newly started
  app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 15:53:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (169 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago)

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

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


[Desktop-packages] [Bug 1801757] Re: all app indicators disappear

2019-03-03 Thread Xavier Guillot
I don't know if it is the same bug, but I have a similar problem since
approx. 1 week in Dingo : Dropbox, Radio-tray NG, gEncFS Manager
indicators are no more visible in the top bar, programs are still
running.

Those from Gnome Shell extensions are still there.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1801757

Title:
  all app indicators disappear

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  Occasionally all of my app indicators just disappear. Right now, for
  example the only icons in my top bar are the wifi icon, the volume
  icon, and the battery charge icon. Everything else is gone. The
  applications associated with the missing indicators, e.g., Dropbox,
  Cloud Station Drive, Pritunl, Shutter, are still running, but their
  app indicators are no longer there.

  The only way I've found to get them back is to log out and log back
  in.

  I have no idea what provokes this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  5 11:37:47 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818451] [NEW] I can not watch 4k .webm video in the Firefox

2019-03-03 Thread Artyom Pozharov
Public bug reported:

Ubuntu 19.04 (alpha). Firefox 65.0.1

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 65.0.1+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  artyom 1132 F pulseaudio
BuildID: 20190214235031
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  4 00:05:35 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2019-03-02 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
IpRoute:
 default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.100 metric 600
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=65.0.1/20190214235031 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.40
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 832E
dmi.board.vendor: HP
dmi.board.version: 26.34
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd05/17/2018:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.34:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP 200
dmi.product.name: HP 250 G6 Notebook PC
dmi.product.sku: 3DN65ES#ACB
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1818451

Title:
  I can not watch 4k .webm video in the Firefox

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04 (alpha). Firefox 65.0.1

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 65.0.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  artyom 1132 F pulseaudio
  BuildID: 20190214235031
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  4 00:05:35 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2019-03-02 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.100 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=65.0.1/20190214235031 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832E
  dmi.board.vendor: HP
  dmi.board.version: 26.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd05/17/2018:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.34:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.sku: 3DN65ES#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

2019-03-03 Thread Michael Grivas
Anonymized, gzipped and attached.

** Attachment added: "gnome-crash.journal.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812527/+attachment/5243149/+files/gnome-crash.journal.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1812527

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in gjs package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818434] Re: Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Edson José dos Santos
*** This bug is a duplicate of bug 1817223 ***
https://bugs.launchpad.net/bugs/1817223

Hello Jeremy Bicha

It is not a duplicate, because this problem is specific in the Ubuntu
settings and not in Ubuntu Software.

Just when we click on "Open in Software" and it opens Ubuntu Software,
but no program opens.

They are different but related applications.

Thank you


*
Olá Jeremy Bicha

Não é uma duplicata, pois este problema é em especifico nas
configurações do Ubuntu e não no Ubuntu Software.

Apenas quando clicamos no "Open in Software" e que se abre o Ubuntu
Software, mas nenhum programa abre.

São aplicativos distintos, mas relacionados.

Obrigado

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818434] Re: Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1817223 ***
https://bugs.launchpad.net/bugs/1817223

I think this is a duplicate of bug 1817223 so I'm marking it as a
duplicate.

If you use gnome-software 3.30.6 instead of 3.31 in disco-proposed, you
shouldn't have this bug.

** This bug has been marked a duplicate of bug 1817223
   [disco-proposed] The list of applications in Ubuntu Software is empty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1816205] Re: When using the Gedit icons they disappear from the desktop

2019-03-03 Thread Edson José dos Santos
Recorded by cell phone got a little better

See the icons disappearing and appearing from the desktop when you click
Save in Gedit.

*
Gravado pelo celular ficou um pouco melhor

Vejam os ícones sumindo e aparecendo ao clicar em salvar no Gedit

** Attachment added: "WhatsApp Video 2019-03-03 at 16.41.44.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+attachment/5243137/+files/WhatsApp%20Video%202019-03-03%20at%2016.41.44.mp4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
https://bugs.launchpad.net/bugs/1816205

Title:
  When using the Gedit icons they disappear from the desktop

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Incomplete

Bug description:
  Hello guys

  When you open Gedit and edit any text or not, and click save, the
  desktop icons disappear, disappear, and move from side to side. After
  you click save the icons reappear again.

  The following images are attached:

  *

  Olá Pessoal

  Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em
  salvar, os ícones da área de trabalho desaparecem, somem e se movem de
  um lado para o outro. Após clicar em salvar os ícones reaparecem
  novamente.

  Segue imagens em anexo:

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.31.90-1build1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 15 21:46:27 2019
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818440] Re: icon of kde system tray didn't named, just say frame

2019-03-03 Thread paulwoisard
** Summary changed:

- icon of kde system tray is not named, just say frame
+ icon of kde system tray didn't named, just say frame

** Summary changed:

- icon of kde system tray didn't named, just say frame
+ icon of kde system tray didn't name, just say frame

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-orca in Ubuntu.
https://bugs.launchpad.net/bugs/1818440

Title:
  icon of kde system tray didn't name, just say frame

Status in gnome-orca package in Ubuntu:
  New

Bug description:
  I would like use Orca in kubuntu 18.10, and when pass the cursor on
  systray of my kubuntu, icon are name frame and not there real name

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

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


[Desktop-packages] [Bug 1816205] Re: When using the Gedit icons they disappear from the desktop

2019-03-03 Thread Edson José dos Santos
Hello guys

Attaching small video showing that when you click save in gedit, the
icons on the desktop disappear and when you click save again the icons
reappear.

Sorry for the bad quality of the video, but the to see the icons
disappear and after they return to the desktop.


*
Olá Pessoal

Anexando pequeno vídeo mostrando que ao clicar em salvar no gedit, os
ícones na área de trabalho desaparecem e ao clicar em salvar novamente
os ícones reaparecem.

Perdão pela má qualidade do vídeo, mas da para ver os ícones sumirem e
após retornarem a área de trabalho.


** Attachment added: "2019-03-03-162955.webm"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+attachment/5243125/+files/2019-03-03-162955.webm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
https://bugs.launchpad.net/bugs/1816205

Title:
  When using the Gedit icons they disappear from the desktop

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Incomplete

Bug description:
  Hello guys

  When you open Gedit and edit any text or not, and click save, the
  desktop icons disappear, disappear, and move from side to side. After
  you click save the icons reappear again.

  The following images are attached:

  *

  Olá Pessoal

  Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em
  salvar, os ícones da área de trabalho desaparecem, somem e se movem de
  um lado para o outro. Após clicar em salvar os ícones reaparecem
  novamente.

  Segue imagens em anexo:

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gedit 3.31.90-1build1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 15 21:46:27 2019
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2019-02-11 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818440] [NEW] icon of kde system tray is not named, just say frame

2019-03-03 Thread paulwoisard
Public bug reported:

I would like use Orca in kubuntu 18.10, and when pass the cursor on
systray of my kubuntu, icon are name frame and not there real name

** Affects: gnome-orca (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-orca in Ubuntu.
https://bugs.launchpad.net/bugs/1818440

Title:
  icon of kde system tray is not named, just say frame

Status in gnome-orca package in Ubuntu:
  New

Bug description:
  I would like use Orca in kubuntu 18.10, and when pass the cursor on
  systray of my kubuntu, icon are name frame and not there real name

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

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


[Desktop-packages] [Bug 1818439] [NEW] Notifications from Kubuntu 18.10 aren't reading

2019-03-03 Thread paulwoisard
Public bug reported:

I would like create a version of Kubuntu 18.10 for visual deficiant.

And orca don't read notifications on kde system.

I use pico voice.

** Affects: gnome-orca (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-orca in Ubuntu.
https://bugs.launchpad.net/bugs/1818439

Title:
  Notifications from Kubuntu 18.10 aren't reading

Status in gnome-orca package in Ubuntu:
  New

Bug description:
  I would like create a version of Kubuntu 18.10 for visual deficiant.

  And orca don't read notifications on kde system.

  I use pico voice.

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

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


[Desktop-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 Desktop
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 libraries
  ii  l

[Desktop-packages] [Bug 1818434] Re: Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Edson José dos Santos
** Attachment added: "Captura de tela de 2019-03-03 16-02-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1818434/+attachment/5243107/+files/Captura%20de%20tela%20de%202019-03-03%2016-02-42.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818434] Re: Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Edson José dos Santos
** Attachment added: "Captura de tela de 2019-03-03 16-03-12.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1818434/+attachment/5243109/+files/Captura%20de%20tela%20de%202019-03-03%2016-03-12.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818434] Re: Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Edson José dos Santos
** Attachment added: "Captura de tela de 2019-03-03 16-02-28.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1818434/+attachment/5243106/+files/Captura%20de%20tela%20de%202019-03-03%2016-02-28.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818434] Re: Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Edson José dos Santos
** Attachment added: "Captura de tela de 2019-03-03 16-02-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1818434/+attachment/5243108/+files/Captura%20de%20tela%20de%202019-03-03%2016-02-58.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818434] [NEW] Applications in gnome-control-center by clicking on "Open in Software" do not open

2019-03-03 Thread Edson José dos Santos
Public bug reported:

Hello guys

No application next door opens in gnome-control-center by clicking "Open
in Software" on Ubuntu Disk 19.04.

The only thing that appears is the screen of Ubuntu Frozen Software, see
attachments.



Olá Pessoal

Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
"Open in Software" no Ubuntu Disco 19.04.

A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
anexos.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.31.90-1ubuntu3
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  3 16:05:16 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-02-11 (19 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1818434

Title:
  Applications in gnome-control-center by clicking on "Open in Software"
  do not open

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hello guys

  No application next door opens in gnome-control-center by clicking
  "Open in Software" on Ubuntu Disk 19.04.

  The only thing that appears is the screen of Ubuntu Frozen Software,
  see attachments.

  

  Olá Pessoal

  Nenhum aplicativo ao lado abre em gnome-control-center ao clicarmos em
  "Open in Software" no Ubuntu Disco 19.04.

  A unica coisa que aparece é a tela do Ubuntu Software congelada, vide
  anexos.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.31.90-1ubuntu3
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  3 16:05:16 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-02-11 (19 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1771396] Re: Pasted Twitter links are invisble.

2019-03-03 Thread Paul White
** Changed in: firefox (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1771396

Title:
  Pasted Twitter links are invisble.

Status in firefox package in Ubuntu:
  New

Bug description:
  If I:

  1. point my browser to twitter.com and select a random tweet.
  2. And then from the Drop Down menu, select: "Copy Link to Tweet."
  3. And then paste that link into a gmail composition

  Then the link will not show up, although it is there.
  It's almost as if it is pasted as white text on white background?
  With the difference that even when selecting it, it still doesn't show.

  The only way to make it show up, is change your gmail composition mode to 
'Plain text mode.'
  Once you do that, you see that the link is actually there.

  
  I expected, instead, to have the link visible after pasting it into gmail.

  Note: same issue happens if I use Chromium browser instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 60.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bram   1345 F pulseaudio
   /dev/snd/controlC0:  bram   1345 F pulseaudio
  BuildID: 20180509234620
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 15 10:27:22 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2018-04-29 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IpRoute:
   default via 10.0.1.1 dev enp5s1 proto dhcp metric 100 
   10.0.1.0/24 dev enp5s1 proto kernel scope link src 10.0.1.78 metric 100 
   169.254.0.0/16 dev enp5s1 scope link metric 1000
  IwConfig:
   enp5s1no wireless extensions.
   
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MostRecentCrashID: bp-64ea59d4-fe25-4952-b630-d4b561180214
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=60.0/20180509234620 (In use)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2108
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2108:bd06/02/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Desktop-packages] [Bug 1791307] Re: [snap] GTK theme doesn't match the host system

2019-03-03 Thread igetin
Some system themes don’t get styled at all on the snap version. In the
attachment there’s a comparison of the Adapta theme on the deb & snap
versions of Chromium 72.0.3626.119, running on Xubuntu 18.04.

** Attachment added: "chromium_gtk_theme_deb_vs_snap.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1791307/+attachment/5243092/+files/chromium_gtk_theme_deb_vs_snap.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1791307

Title:
  [snap] GTK theme doesn't match the host system

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  The GTK theme of the chrome and file open/save dialogs doesn't match
  the theme on the host system.

  See attached screenshots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1791307/+subscriptions

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


[Desktop-packages] [Bug 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt

2019-03-03 Thread Mario Trangoni
** Bug watch added: Red Hat Bugzilla #1241939
   https://bugzilla.redhat.com/show_bug.cgi?id=1241939

** Also affects: libxfont (Nexenta Operating System) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1241939
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxfont in Ubuntu.
https://bugs.launchpad.net/bugs/1818428

Title:
  bdftopcf: bdf input, xtfont4.bdf, corrupt

Status in libxfont package in Ubuntu:
  New
Status in libxfont package in Nexenta Operating System:
  Unknown

Bug description:
  Compiling the xorg Test Suite called XTS
  (https://github.com/freedesktop/xorg-test-xts) on TravisCI (https
  ://travis-ci.org/mjtrangoni/nx-libs/jobs/501145999), I am running on
  this Bug,

  -
  /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf
  /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf
  /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf
  /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf
  /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf
  BDF Error on line 32: character 'ascii001' has out of range width, -8
  /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt
  Makefile:767: recipe for target 'xtfont4.pcf' failed
  ---

  Which seems to be fixed upstream,

  See RedHat Bugzilla 1241939
  (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream
  fix here (https://lists.x.org/archives/xorg-
  devel/2015-July/046914.html)

  I hope, I can get this fixed/backported soon on Ubuntu Xenial.

  Operating System Details:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  Codename: xenial

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

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


[Desktop-packages] [Bug 1818428] [NEW] bdftopcf: bdf input, xtfont4.bdf, corrupt

2019-03-03 Thread Mario Trangoni
Public bug reported:

Compiling the xorg Test Suite called XTS (https://github.com/freedesktop
/xorg-test-xts) on TravisCI (https://travis-ci.org/mjtrangoni/nx-
libs/jobs/501145999), I am running on this Bug,

-
/usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf
/usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf
/usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf
/usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf
/usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf
BDF Error on line 32: character 'ascii001' has out of range width, -8
/usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt
Makefile:767: recipe for target 'xtfont4.pcf' failed
---

Which seems to be fixed upstream,

See RedHat Bugzilla 1241939
(https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream
fix here (https://lists.x.org/archives/xorg-devel/2015-July/046914.html)

I hope, I can get this fixed/backported soon on Ubuntu Xenial.

Operating System Details:
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename:   xenial

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxfont in Ubuntu.
https://bugs.launchpad.net/bugs/1818428

Title:
  bdftopcf: bdf input, xtfont4.bdf, corrupt

Status in libxfont package in Ubuntu:
  New

Bug description:
  Compiling the xorg Test Suite called XTS
  (https://github.com/freedesktop/xorg-test-xts) on TravisCI (https
  ://travis-ci.org/mjtrangoni/nx-libs/jobs/501145999), I am running on
  this Bug,

  -
  /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf
  /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf
  /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf
  /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf
  /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf
  BDF Error on line 32: character 'ascii001' has out of range width, -8
  /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt
  Makefile:767: recipe for target 'xtfont4.pcf' failed
  ---

  Which seems to be fixed upstream,

  See RedHat Bugzilla 1241939
  (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream
  fix here (https://lists.x.org/archives/xorg-
  devel/2015-July/046914.html)

  I hope, I can get this fixed/backported soon on Ubuntu Xenial.

  Operating System Details:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  Codename: xenial

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

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


[Desktop-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 Desktop
Packages, which is subscribed to libreoffice-l10n 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 obj

[Desktop-packages] [Bug 1818427] [NEW] Problem changing video resolution

2019-03-03 Thread Simon Rodan
Public bug reported:

Actions:
Open Cheese
>From preferences change video resolution
Select video as recording mode (either using the button or from the menu)

Expected behavior:
Video resolution changes and new aspect ratio image is shown in Cheese monitor.

Observed behavior: 
Cheese monitor is black with message "There was an error playing the video from 
the webcam"
The webcam is not activated
All modes in menu are greyed.
Modes cannot be selected until cheese is closed  


Workaround #1
Set both photo and video modes to the desired video resolution - both video and 
photo resolution must be the same. 
Quit Cheese
Reopen Cheese
New video resolution is selected

Workaround #2
Select video mode
Make a video recording
Now the video resolution can be changed independently of the photo resolution
NOTE that a recording must be made at the selected resolution every time before 
it can be changed.

Cheese version 3.10.2
Webcam is Logitech C920 HD pro
Linux Mint

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cheese 3.10.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-151.201-generic 3.13.11-ckt39
Uname: Linux 3.13.0-151-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
Date: Sun Mar  3 09:16:18 2019
ExecutablePath: /usr/bin/cheese
InstallationDate: Installed on 2018-01-03 (423 days ago)
InstallationMedia: Linux Mint 17.1 "Rebecca" - Release amd64 20141126
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cheese
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug rebecca third-party-packages

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1818427

Title:
  Problem changing video resolution

Status in cheese package in Ubuntu:
  New

Bug description:
  Actions:
  Open Cheese
  From preferences change video resolution
  Select video as recording mode (either using the button or from the menu)

  Expected behavior:
  Video resolution changes and new aspect ratio image is shown in Cheese 
monitor.

  Observed behavior: 
  Cheese monitor is black with message "There was an error playing the video 
from the webcam"
  The webcam is not activated
  All modes in menu are greyed.
  Modes cannot be selected until cheese is closed  

  
  Workaround #1
  Set both photo and video modes to the desired video resolution - both video 
and photo resolution must be the same. 
  Quit Cheese
  Reopen Cheese
  New video resolution is selected

  Workaround #2
  Select video mode
  Make a video recording
  Now the video resolution can be changed independently of the photo resolution
  NOTE that a recording must be made at the selected resolution every time 
before it can be changed.

  Cheese version 3.10.2
  Webcam is Logitech C920 HD pro
  Linux Mint

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cheese 3.10.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-151.201-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-151-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  Date: Sun Mar  3 09:16:18 2019
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2018-01-03 (423 days ago)
  InstallationMedia: Linux Mint 17.1 "Rebecca" - Release amd64 20141126
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1818371] Re: Simple Scan images are too dark at resolutions > 75ppi.

2019-03-03 Thread William T. Lowther
Please disregard my first bug description in my post #1.  Apologies for
this confusion.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1818371

Title:
  Simple Scan images are too dark at resolutions > 75ppi.

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.2
  Canon Pixma TS6220
  These issues are identical to an earlier bug (#1818186) that I reported 
regarding the operation of Xsane.

  1) I am able to move the dashed lines to frame the print to be scanned, but 
the output always contains the images of what ever is on the platen on a "full 
size" white background.
  2) I have selected “inches” as the unit of measurement, but the preview 
window has “px” in the upper left corner, and the dimensions in the windows at 
the bottom of the main menu are in pixels. These dimensions do not change as I 
adjust the frame of the photo to be scanned and always read 2480*3507*24 
(24.9MB).
  3) There are no length markings along the side or top of the preview window.
  4) In Advanced Options, the UOM displays “px”. The sliders change as I adjust 
the frame, but for a 4” x 6” photo in the upper left corner, the lower right 
corner is shown to be .00235x, .00154y.
  5) The scanned image of the photos is very dark/saturated – beyond my ability 
to correct.
  6) Max scan resolution in the main menu is only 300, whereas it is 1200 with 
the HP scanner.
  If I can be of any assistance in “testing”, please let me know.
  Kind regards,
  Bill

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Mar  1 20:59:54 2019
  InstallationDate: Installed on 2018-08-04 (210 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Acer Aspire XC-603
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-B4
  dmi.board.name: Aspire XC-603
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire XC-603
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1818371/+subscriptions

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


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

2019-03-03 Thread Amr Ibrahim
In the future, please run (Alt+F2) 'ubuntu-bug package-name' to file bugs in 
Ubuntu. It's easier than selecting the package manually and it collects all 
needed info automatically.
Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-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 Desktop
Packages, which is subscribed to totem 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

2019-03-03 Thread spike speigel
~$ inxi -G
Graphics:  Device-1: NVIDIA GP104 [GeForce GTX 1070] driver: nvidia v: 415.27 
   Display: x11 server: X.Org 1.20.3 driver: nvidia resolution: 
2560x1440~60Hz 
   OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 415.27

~$ xrandr --query
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 600mm x 340mm
   3840x2160 30.00 +  29.9725.0023.98  
   2560x1440 59.95* 
   1920x1080 60.0059.9429.9760.00  
   1600x900  60.00  
   1280x1024 60.02  
   1280x800  59.81  
   1280x720  60.0059.94  
   1152x864  60.00  
   1024x768  60.00  
   800x600   60.32  
   720x480   59.94  
   640x480   59.9459.93  
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1760068

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions

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


[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

2019-03-03 Thread spike speigel
In my instance (Xubuntu 18.10 with nvidia 415 from the graphics drivers
PPA) I was able to fix the lock screen resolution by using the
following:

Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/xorg"
ModulePath "/usr/lib/xorg/modules"
EndSection

My system has /usr/lib/nvidia, but no xorg directory located there.
Likewise, no nvidia/xorg directory path under /usr/lib/x86_64-linux-gnu.
There was only xorg as listed above with my corresponding nvidia
modules.

This workaround does not fix the TTY screen resolution or the Xubuntu
boot/loading spash.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1760068

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions

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


[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

2019-03-03 Thread spike speigel
Same issue with Xubuntu 18.10 Cosmic and nvidia-driver-415.  As
mentioned above it is not only the lock screen, but the boot splash
screens as well.

** Tags added: cosmic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1760068

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions

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


[Desktop-packages] [Bug 1815957] Re: SynPS/2 Synaptics TouchPad: Read error 19

2019-03-03 Thread Ettore Atalan
Removing "acpi_os_name=Linux acpi_osi=" from /etc/default/grub doesn't
fix this problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1815957

Title:
  SynPS/2 Synaptics TouchPad: Read error 19

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hi

  Ubuntu 18.04 went into standby mode with the mouse plugged in.
  Then I've removed the mouse.

  A few hours later I wanted to continue work (without mouse) and woke up my PC 
from standby mode.
  Unfortunately the touchpad did not work.

  So I put Ubuntu back into standby mode, plugged in a mouse and woke it up 
again.
  Both Touchpad and mouse worked perfectly again.

  Regards,

  Ettore Atalan
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ben7239 F pulseaudio
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2018-07-29 21:59:28,715 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-wmi, 1.5.1, 3.13.0-24-generic, x86_64: built
   tuxedo-wmi, 1.5.1, 4.15.0-44-generic, x86_64: installed
   tuxedo-wmi, 1.5.1, 4.15.0-45-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6507]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 5986:055c Acer, Inc 
   Bus 001 Device 002: ID 046d:c245 Logitech, Inc. G400 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook W65_W67RZ
  Package: xserver-xorg-input-libinput 0.27.1-1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=462560f8-ccdb-4115-a3c9-46fce6a630d2 ro rw quiet splash 
acpi_os_name=Linux acpi_osi= acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic ubuntu ubuntu
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-29 (204 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.09
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.09:bd05/27/2016:svnNotebook:pnW65_W67RZ:pvrNotApplicable:rvnNotebook:rnW65_W67RZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W65_W67RZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Jan 21 20:00:45 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2

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

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


  1   2   >