date:20200516

You have been subscribed to a public bug:

Hello everybody,

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

Description:Ubuntu 20.04 LTS
Release:20.04

I have a Dell N4050 Notebook I installed 20.04 LTS. When we choose user
name on the login screen then we tap the touchpad to open the password
box does not open, there is no response to this action.

I also noticed that others login screen icons do not respond to the
touchpad, it needs press a touchpad button instead a tap touchpad
action.

3) What you expected to happen:

I expected when tapped twice on touchpad with the mouse cursor on user
name it opens the password text box.

Same for the icons in the same log in screen.

4) What happened instead

When we tap de touchpad nothings happen.

I hope you understand my broken english.

Thanks

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
ivos de pacote:
 100 /var/lib/dpkg/status
 release a=now
 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages
 release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=i386
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages
 release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=amd64
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages
 release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=restricted,b=amd64
 origin security.ubuntu.com
 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages
 release v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=main,b=i386

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


** Tags: bot-comment functionality
-- 
GNOME Login- Screen / Lock-Screen
https://bugs.launchpad.net/bugs/1876614
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
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 1876614] Re: GNOME Login- Screen / Lock-Screen

2020-05-16 Thread Paul White

** Package changed: ubuntu => gnome-shell (Ubuntu)

** Tags added: focal

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

Title:
  GNOME Login- Screen / Lock-Screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello everybody,

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  I have a Dell N4050 Notebook I installed 20.04 LTS. When we choose
  user name on the login screen then we tap the touchpad to open the
  password box does not open, there is no response to this action.

  I also noticed that others login screen icons do not respond to the
  touchpad, it needs press a touchpad button instead a tap touchpad
  action.

  3) What you expected to happen:

  I expected when tapped twice on touchpad with the mouse cursor on user
  name it opens the password text box.

  Same for the icons in the same log in screen.

  4) What happened instead

  When we tap de touchpad nothings happen.

  I hope you understand my broken english.

  Thanks

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ivos de pacote:
   100 /var/lib/dpkg/status
   release a=now
   500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages
   release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=i386
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages
   release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=amd64
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 
Packages
   release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=restricted,b=amd64
   origin security.ubuntu.com
   500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages
   release v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=main,b=i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876614/+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 1876467] Re: Network Manager Applet Icon error on VPN Connection

2020-05-16 Thread MasterEvil

may 15 00:49:55 notrebook NetworkManager[2323]:   [1589492995.4051] 
audit: op="connection-activate" uuid="9b8acdef-2037-441c-afbc-b4c20774bbbf" 
name="Test Connection" pid=3941 uid=1000 result="success"
may 15 00:49:55 notrebook NetworkManager[2323]:   [1589492995.4233] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",0]: Started the VPN service, PID 8223
may 15 00:49:55 notrebook NetworkManager[2323]:   [1589492995.4313] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",0]: Saw the service appear; activating connection
may 15 00:49:55 notrebook NetworkManager[2323]:   [1589492995.5024] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",0]: VPN plugin: state changed: starting (3)
may 15 00:49:55 notrebook NetworkManager[2323]:   [1589492995.5024] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",0]: VPN connection: (ConnectInteractive) reply received
may 15 00:49:55 notrebook nm-openvpn[8237]: OpenVPN 2.4.7 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep  
5 2019
may 15 00:49:55 notrebook nm-openvpn[8237]: library versions: OpenSSL 1.1.1f  
31 Mar 2020, LZO 2.10
may 15 00:49:55 notrebook nm-openvpn[8237]: WARNING: --ns-cert-type is 
DEPRECATED.  Use --remote-cert-tls instead.
may 15 00:49:55 notrebook nm-openvpn[8237]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
may 15 00:49:55 notrebook nm-openvpn[8237]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]X.X.X.X:1194
may 15 00:49:55 notrebook nm-openvpn[8237]: UDP link local: (not bound)
may 15 00:49:55 notrebook nm-openvpn[8237]: UDP link remote: 
[AF_INET]X.X.X.X:1194
may 15 00:49:55 notrebook nm-openvpn[8237]: NOTE: chroot will be delayed 
because of --client, --pull, or --up-delay
may 15 00:49:55 notrebook nm-openvpn[8237]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
may 15 00:49:55 notrebook nm-openvpn[8237]: [OpenVPN Server] Peer Connection 
Initiated with [AF_INET]X.X.X.X:1194
may 15 00:49:57 notrebook nm-openvpn[8237]: Options error: Unrecognized option 
or missing or extra parameter(s) in [PUSH-OPTIONS]:4: dhcp-pre-release (2.4.7)
may 15 00:49:57 notrebook nm-openvpn[8237]: Options error: Unrecognized option 
or missing or extra parameter(s) in [PUSH-OPTIONS]:5: dhcp-renew (2.4.7)
may 15 00:49:57 notrebook nm-openvpn[8237]: Options error: Unrecognized option 
or missing or extra parameter(s) in [PUSH-OPTIONS]:6: dhcp-release (2.4.7)
may 15 00:49:57 notrebook nm-openvpn[8237]: Options error: Unrecognized option 
or missing or extra parameter(s) in [PUSH-OPTIONS]:18: register-dns (2.4.7)
may 15 00:49:57 notrebook nm-openvpn[8237]: Options error: Unrecognized option 
or missing or extra parameter(s) in [PUSH-OPTIONS]:19: block-ipv6 (2.4.7)
may 15 00:49:57 notrebook nm-openvpn[8237]: TUN/TAP device tun0 opened
may 15 00:49:57 notrebook nm-openvpn[8237]: 
/usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 8223 
--bus-name org.freedesktop.NetworkManager.openvpn.Connection_2 --tun -- tun0 
1500 1553 Z.Z.Z.Z 255.255.240.0 init
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1641] 
manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/5)
may 15 00:49:57 notrebook systemd-udevd[8225]: ethtool: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1842] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",0]: VPN connection: (IP Config Get) reply received.
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1852] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",5:(tun0)]: VPN connection: (IP4 Config Get) reply received
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1857] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",5:(tun0)]: Data: VPN Gateway: X.X.X.X
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1857] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",5:(tun0)]: Data: Tunnel Device: "tun0"
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1857] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",5:(tun0)]: Data: IPv4 configuration:
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1858] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",5:(tun0)]: Data:   Internal Gateway: Z.Z.Z.Z
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.1858] 
vpn-connection[0x562c6c4ea160,9b8acdef-2037-441c-afbc-b4c20774bbbf,"Test 
Connection",5:(tun0)]: Data:   Internal Address: Z.Z.Z.Z
may 15 00:49:57 notrebook NetworkManager[2323]:   [1589492997.18

[Desktop-packages] [Bug 1877711] Re: Libreoffice snap can read but not save files over SSH

2020-05-16 Thread Sami Pietila

If I try to install libreoffice deb version from the software center, I
get a message saying it is not supported. Please see the attached
screenshot.

** Attachment added: "not-supported.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+attachment/5372556/+files/not-supported.png

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

Title:
  Libreoffice snap can read but not save files over SSH

Status in libreoffice package in Ubuntu:
  New

Bug description:
  With Ubuntu 20.04 libreoffice can not anymore save files over SSH
  share.

  When trying to save, it says: Error saving the document. General
  Error. General input/output error.

  In addition, starting from Ubuntu 20.04 libreoffice has become very
  slow to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877711/+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 1879039] [NEW] Xorg crash

You have been subscribed to a public bug:

After Firefox crushes couldnt open any browser, no Firefox nor Chromium
and I had to restart the OS. Ubuntu 19.10 is a guest OS on Parallels 15

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
Uname: Linux 5.3.0-53-generic x86_64
NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: X-Cinnamon
Date: Sat May 16 12:17:36 2020
DistUpgraded: 2020-05-09 07:53:36,319 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 parallels-tools, 15.1.4.47270, 4.15.0-100-generic, x86_64: installed
 parallels-tools, 15.1.4.47270, 5.3.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 [VGA 
controller])
   Subsystem: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:0400]
InstallationDate: Installed on 2018-08-10 (644 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Parallels Software International Inc. Parallels Virtual Platform
MonitorsUser.xml: Virtual1unknownunknownunknown144090059.988003001yes
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=b214da3c-eaae-4adf-bfcc-c64b050618e8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to eoan on 2020-05-09 (7 days ago)
dmi.bios.date: 04/13/2020
dmi.bios.vendor: Parallels Software International Inc.
dmi.bios.version: 15.1.4 (47270)
dmi.board.name: Parallels Virtual Platform
dmi.board.vendor: Parallels Software International Inc.
dmi.board.version: None
dmi.chassis.type: 9
dmi.chassis.vendor: Parallels Software International Inc.
dmi.modalias: 
dmi:bvnParallelsSoftwareInternationalInc.:bvr15.1.4(47270):bd04/13/2020:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct9:cvr:
dmi.product.family: Parallels VM
dmi.product.name: Parallels Virtual Platform
dmi.product.sku: Undefined
dmi.product.version: None
dmi.sys.vendor: Parallels Software International Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash eoan ubuntu
-- 
Xorg crash
https://bugs.launchpad.net/bugs/1879039
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
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 1874578] Re: [wayland] dock has very long load time

2020-05-16 Thread Joerg Baeuerle

I also have the problem, that icons in the dock have a delay of 25
seconds between program start and dock update.

This is a fresh install of 20.04 LTS on a clean laptop with a wiped hard
disk.

schorsch@jbook:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal

schorsch@jbook:~$ uname -a
Linux jbook 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux

The only thing I did after the new installation was installing the dash-
to-panel Gnome extension. Once, I deactivated that extension and the
Ubuntu Dock showed again, I noticed the delay. However, I cannot say for
sure if the delay has been there from the beginning.

I completely removed the dash-to-panel extension using apt, but the
Ubuntu Dock delay is still there.

Also, the 'gsettings set org.gnome.shell.extensions.dash-to-dock show-
mounts false' thing did NOT work in my case. The dock still has the
delay.

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

Title:
[wayland] dock has very long load time

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
Confirmed

Bug description:
I just upgraded from Ubuntu 18.04 to 20.04.

When I boot my system I have to wait at least 10 to 15 seconds for the
application icons to load on dock. Meanwhile everything else seems to
be working properly. I didn't experience this behavior in Ubuntu
18.04.

Also the dock doesn't trigger when I move my cursor to the left of the
screen. (I have set the docker to Auto-Hide mode and it's position is on the
left of my screen).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2016-08-03 (1359 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Tags: focal third-party-packages wayland-session
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
_MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874578/+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 1879039] Re: Xorg crash

2020-05-16 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  After Firefox crushes couldnt open any browser, no Firefox nor
  Chromium and I had to restart the OS. Ubuntu 19.10 is a guest OS on
  Parallels 15

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_vid prl_tg
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat May 16 12:17:36 2020
  DistUpgraded: 2020-05-09 07:53:36,319 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   parallels-tools, 15.1.4.47270, 4.15.0-100-generic, x86_64: installed
   parallels-tools, 15.1.4.47270, 5.3.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 
[VGA controller])
 Subsystem: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:0400]
  InstallationDate: Installed on 2018-08-10 (644 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Parallels Software International Inc. Parallels Virtual Platform
  MonitorsUser.xml: Virtual1unknownunknownunknown144090059.988003001yes
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=b214da3c-eaae-4adf-bfcc-c64b050618e8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2020-05-09 (7 days ago)
  dmi.bios.date: 04/13/2020
  dmi.bios.vendor: Parallels Software International Inc.
  dmi.bios.version: 15.1.4 (47270)
  dmi.board.name: Parallels Virtual Platform
  dmi.board.vendor: Parallels Software International Inc.
  dmi.board.version: None
  dmi.chassis.type: 9
  dmi.chassis.vendor: Parallels Software International Inc.
  dmi.modalias: 
dmi:bvnParallelsSoftwareInternationalInc.:bvr15.1.4(47270):bd04/13/2020:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct9:cvr:
  dmi.product.family: Parallels VM
  dmi.product.name: Parallels Virtual Platform
  dmi.product.sku: Undefined
  dmi.product.version: None
  dmi.sys.vendor: Parallels Software International Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879039/+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 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

The cold boot did not work. I have entered the grub menu, edited the command 
line parameters and added the parameters that you have provided and continued 
to boot. Opened terminal ran "sudo btmon -w coldboot.journal" and opened a new 
tab and ran "sudo modprobe btusb". The bluetooth is not up.
 
Output of "systemctl status bluetooth",
● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
 Active: inactive (dead)
   Docs: man:bluetoothd(8)

May 16 08:19:22 systemd[1]: Condition check resulted in Bluetooth s>

Attaching cold boot btsnoop

** Attachment added: "coldboot.btsnoop"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5372558/+files/coldboot.btsnoop

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.ve

[Desktop-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Hi vicamo,

If i do "systemctl status bluetooth", it shows that bluetooth is active
but if i do "bluetoothctl" and pass the command "power on", the output
says "No default controller available".


** Attachment added: "bt.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5372557/+files/bt.png

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.23
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df1xxx
  dmi.product.sku: 7UT64UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug g

[Desktop-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

** Attachment added: "coldboot.journal"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5372559/+files/coldboot.journal

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.23
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df1xxx
  dmi.product.sku: 7UT64UA#ABA
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

The warmboot did not work either.

** Attachment added: "warmboot.btsnoop"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5372560/+files/warmboot.btsnoop

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.23
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df1xxx
  dmi.product.sku: 7UT64UA#ABA
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
P

[Desktop-packages] [Bug 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.

** Attachment added: "warmboot.journal"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+attachment/5372561/+files/warmboot.journal

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

Title:
  HP-Spectre 2019 Intel wireless driver is detected incorrectly.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Output of lsb_release -rd,
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Issue:
  I have Intel AX-201 for wireless but when i do "lspci -k", the driver is 
detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows 
that the wireless driver detected is "Intel AX-201".

  Output of lspci -k,
  00:14.3 Network controller: Intel Corporation Wireless-AC 9462
   Subsystem: Intel Corporation Wireless-AC 9462
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  Output of journalctl -k | grep iwlwifi,
  May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002)
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
  May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 43.2.23.17
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0
  May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 
48.4fa0041f.0 op_mode iwlmvm
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 
160MHz, REV=0x354
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for 
firmware monitor.
  May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 
7c:b2:7d:d0:d5:95
  May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0
  May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination 
EXTERNAL_DRAM
  May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - 
re-configuring

  In the additional drivers module, it shows that module Intel-9462 no
  longer works. My bluetooth is also not detected and doesn't work.

  I came across this but no else responded yet. So decided to report a bug here.
  
https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems

  Please let me know if any more information is required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srikar 1447 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-03 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP Spectre x360 Convertible 15-df1xxx
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.23
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df1xxx
  dmi.product.sku: 7UT64UA#ABA
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1879053] [NEW] Fractional Upscaling is descaling Certain Apps

2020-05-16 Thread Tobi M.

Public bug reported:

1) Description: Ubuntu 20.04 LTS
Release:20.04
2) wine-development:
  Installed: 5.5-3ubuntu1
  Candidate: 5.5-3ubuntu1
Same goes for wine stable 5.0.
Other Packages foxit 2.4.4.xx, Notepad v7.8.6

3) I'm using a relatively small QHD Display. The Fractional Scaling
Feature is really something I've looked forward to and I'm super
grateful that it has been implemented. With my setup my life gets easier
when having a little zoom but still have a good amount of pixels and
nice sharpness on my workspace :D

4) With some apps the fractional scaling has an opposite effect. For
example wine apps and foxit reader appear tiny with fractional scaling
turned on (I'm using 125%) and the apps shrink compared to 100%.

Is this the right place to report the bug or do i need to make a
bugreport for every specific app?

Kind regards,
Tobi

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

** Description changed:

  1) Description:   Ubuntu 20.04 LTS
  Release:  20.04
  2) wine-development:
-   Installed: 5.5-3ubuntu1
-   Candidate: 5.5-3ubuntu1
+   Installed: 5.5-3ubuntu1
+   Candidate: 5.5-3ubuntu1
  Same goes for wine stable 5.0.
  Other Packages foxit 2.4.4.xx, Notepad v7.8.6
  
  3) I'm using a relatively small QHD Display. The Fractional Scaling
  Feature is really something I've looked forward to and I'm super
  grateful that it has been implemented. With my setup my life gets easier
  when having a little zoom but still have a good amount of pixels and
  nice sharpness on my workspace :D
  
  4) With some apps the fractional scaling has an opposite effect. For
- example the apps named above appear tiny with fractional scaling turned
- on (I'm using 125%) and the apps shrink compared to 100%.
+ example wine apps and foxit reader appear tiny with fractional scaling
+ turned on (I'm using 125%) and the apps shrink compared to 100%.
  
  Is this the right place to report the bug or do i need to make a
  bugreport for every specific app?
  
  Kind regards,
  Tobi

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

Title:
  Fractional Upscaling is descaling Certain Apps

Status in mutter package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 20.04 LTS
  Release:  20.04
  2) wine-development:
    Installed: 5.5-3ubuntu1
    Candidate: 5.5-3ubuntu1
  Same goes for wine stable 5.0.
  Other Packages foxit 2.4.4.xx, Notepad v7.8.6

  3) I'm using a relatively small QHD Display. The Fractional Scaling
  Feature is really something I've looked forward to and I'm super
  grateful that it has been implemented. With my setup my life gets
  easier when having a little zoom but still have a good amount of
  pixels and nice sharpness on my workspace :D

  4) With some apps the fractional scaling has an opposite effect. For
  example wine apps and foxit reader appear tiny with fractional scaling
  turned on (I'm using 125%) and the apps shrink compared to 100%.

  Is this the right place to report the bug or do i need to make a
  bugreport for every specific app?

  Kind regards,
  Tobi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1879053/+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 1879054] [NEW] No sound after 20.04 update

2020-05-16 Thread Sebastian "Nait" Kacprzak

Public bug reported:

After update from 18.04 to 20.04 sound stopped working.
KDE does not display Xonar sound card at all.

$ aplay /usr/share/sounds/alsa/Front_Center.wav
does not make any sound

Alsamixer displays Xonar set at full volume but changing anything there
does not seem to have any effect.

Moving/deleting the pulse config (  ~/.config/pulse/ ) and restarting
machine did not have any effect.


Running:
$ sudo alsa force-reload
fixes the issue (until restart sound is back, and is displayed properly in KDE)


(data arecord and cards display same data before and after restart)
$ arecord -l
 Lista CAPTURE urządzeń 
karta 0: DX [Xonar DX], urządzenie 0: Multichannel [Multichannel]
  Urządzenia podrzędne: 1/1
  Urządzenie podrzędne #0: subdevice #0
karta 0: DX [Xonar DX], urządzenie 1: Digital [Digital]
  Urządzenia podrzędne: 1/1
  Urządzenie podrzędne #0: subdevice #0

$  cat /proc/asound/cards
 0 [DX ]: AV200 - Xonar DX
  Asus Virtuoso 100 at 0xd000, irq 31
 1 [HDMI   ]: HDA-Intel - HDA ATI HDMI
  HDA ATI HDMI at 0xfe96 irq 67

$ lspci | grep -i audio
21:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD 
Audio]
23:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

(build in motherboard soundcard is disabled in BIOS)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nait   5242 F pulseaudio
 /dev/snd/controlC1:  nait   5242 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sat May 16 14:54:07 2020
InstallationDate: Installed on 2018-11-11 (552 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-05-01 (14 days ago)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.J0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 TOMAHAWK (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd09/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal

** Description changed:

  After update from 18.04 to 20.04 sound stopped working.
  KDE does not display Xonar sound card at all.
  
  Alsamixer displays Xonar set at full volume but changing anything there
  does not seem to have any effect.
  
  Running: 
  $ sudo alsa force-reload
  fixes the issue (until restart sound is back, and is displayed properly in 
KDE)
  
- (data after restart)
+ (data arecord and cards display same data before and after restart)
  $ arecord -l
   Lista CAPTURE urządzeń 
  karta 0: DX [Xonar DX], urządzenie 0: Multichannel [Multichannel]
Urządzenia podrzędne: 1/1
Urządzenie podrzędne #0: subdevice #0
  karta 0: DX [Xonar DX], urządzenie 1: Digital [Digital]
Urządzenia podrzędne: 1/1
Urządzenie podrzędne #0: subdevice #0
  
  $  cat /proc/asound/cards 
   0 [DX ]: AV200 - Xonar DX
Asus Virtuoso 100 at 0xd000, irq 31
   1 [HDMI   ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfe96 irq 67
  
  (build in motherboard soundcard is disabled in BIOS)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nait   5242 F pulseaudio
   /dev/snd/controlC1:  nait   5242 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May 16 14:54:07 2020
  InstallationDate: Installed on 2018-11-11 (552 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-01 (14 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.J0
  dmi.board.asset.tag: To be filled by O.E.M.

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-05-16 Thread Ananya Nayan Borah

I am facing the same problem.

Nvidia Geforce 940MX/Driver Version: 440.64  .

I tried xrandr scaling but it just throws part of the  desktop out of
the screen. I have a setup of 2 monitors one with 1920x1080 and one with
1366x768. It would be great if we can have fractional scaling seperately
for seperate monitors because on my laptop its really small and its huge
on the monitor. I tried the workaround provided by @Kristo  it works to
an extent but doesn't really solve everything; still its better to have
something than nothing. I am new to ubuntu, could someone help me if
there is any way to manipulate icon size seperately for different
monitors?

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1876518] Re: Gtk.Clipboard set_text() not working

2020-05-16 Thread bitinerant

This has been reported upstream:
(https://gitlab.gnome.org/GNOME/pygobject/-/issues/405

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

Title:
  Gtk.Clipboard set_text() not working

Status in pygobject:
  Unknown
Status in pygobject package in Ubuntu:
  Incomplete

Bug description:
  Writing to Gtk.Clipboard doesn't work (reading works).

  Example code:

  #!/usr/bin/python3
  import gi
  gi.require_version('Gtk', '3.0')
  from gi.repository import Gtk, Gdk
  clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
  clipboard.set_text("Does a text of all texts contain itself?", -1)
  clipboard.store()

  Ubuntu 20.04 with Gtk 3.36.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1876518/+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 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.

2020-05-16 Thread WXYZ

I have the same exact issue on 20.04 LTS. I'm using a Radeon RX 570 GPU.
Kernel 5.4.0-29-generic

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

Title:
  No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic
  behaviour when user logged in.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to 
reproduce:
  - boot Ubuntu
  - Press Ctrl+Alt+F2 (or F3 or...)

  Expected behaviour: virtual console should appear with login prompt.
  Actual behaviour: nothing happens.

  When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3...
  However, hitting first Ctrl+Alt+F1 and, subsequently, hitting
  Ctrl+Alt+F3 does not show tty3, and remains at the graphical login
  screen but keyboard and mouse are unresponsive until either
  Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal
  the ubuntu session is running at.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 10:11:26 2018
  InstallationDate: Installed on 2014-05-05 (1418 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2020-05-16 Thread Anton Alexandrenok

@osomon If bionic provides only libva-driver-abi-1.1, maybe its time to
move chromium snap to core20?

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Beta Chromium 80 Snap with vaapi enabled :

  https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from-
  source-enable-
  vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap

  Install it with --devmode

  
  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues

2020-05-16 Thread Michael Johnson

It looks several others have been having problems with hplip in 20.04

Answer 690278 is similar.
As I already noted Answer 690720 is also similar.

I have attempted to purge all references to hplip and re-install the
packages included in 20.04 (which install 3.20.3) but that does not seem
to change the results shown above.

I'm noticing in the logs error reports
"
Printer Backend /usr/lib/cups/backend/hp does not exist!15 May 2020 10:52:34 AM 
PDT -
"

For my specific issue will see if I can obtain these files from another
system I have as it looks like many people use the hp installer to
repair/replace these missing files (but as noted above the HP installer
even version 3.20.5) is not currently passing checks in Ubuntu 20.04

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

Title:
  Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip
  issues

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  Hi,
   
  I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04,
  Spent some time troubleshooting with the default (previously current) drivers 
hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially 
due to missing dependencies. Errors about missing pyqt4 dependencies among 
others.

  When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found
  but fails to print.

  Just noticed similar bug filed, 690720 , and saw note that new hplip
  ver. 3.20.5 was just released and supports Ubuntu 20.04

  When trying to install new package hplip ver. 3.20.5 with the .run
  script provided by HP I am unable to complete installatoin as it
  reports unmet dependency of pyqt5 , even though package python3-pyqt5
  is installed on system.

  https://developers.hp.com/hp-linux-imaging-and-printing/gethplip

  Maybe the repo just needs to be updated with a newer build (3.20.5) to
  install on my system, or is there something that can be done in the
  meantime.

  Below hp-check -t when using the repo hplip ver. 3.20.3 ,

  ==
  Saving output in log file: /root/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.20.3)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies are installed to successfully compile
  HPLIP.

 
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
has the proper dependencies installed to
  successfully run. 

 
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time dependencies).   
  

  Check types:  

 
  a. EXTERNALDEP - External Dependencies

 
  b. GENERALDEP - General Dependencies (required both at compile and run time)  

 
  c. COMPILEDEP - Compile time Dependencies 

 
  d. [All are run-time checks]  

 
  PYEXT SCANCONF QUEUES PERMISSION  

 

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible de

[Desktop-packages] [Bug 1876467] Re: Network Manager Applet Icon error on VPN Connection

2020-05-16 Thread Morpheus

Same here. No icon when connecting to a strongswan VPN.

journalctl -b 0 shows this entry everytime I connect to the VPN (with
different time stamp and different number in brackets each time);

May 16 16:17:15 harvey mate-indicator-[36267]: Could not load a pixbuf
from icon theme.

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

Title:
  Network Manager Applet Icon error on VPN Connection

Status in Ubuntu MATE:
  New
Status in network-manager-applet package in Ubuntu:
  Incomplete

Bug description:
  The Network icon in the top panel doesn't change to the icon with a
  lock when a Palo Alto VPN Network is conected.

  In ubuntu Mate 16 and 18 the default behavior was to change the icon
  adding a small size lock.

  In Ubuntu Mate 20, in Traditional Desktop, seems something is missing.
  When connecting to the VPN, icon changes to a black screen with a
  forbidden icon (see attachment).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1876467/+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 1879071] [NEW] Second dead mouse cursor with fractionnal display

2020-05-16 Thread BLASCO

Public bug reported:

While using fractionnal display to adapt the desktop to my 4K display (150%), a 
second dead small mouse cursor with the orginal size (100%) is still there. 
This bug was reported by many users.
Thanks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 17:26:57 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-12 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Second dead mouse cursor with fractionnal display

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  While using fractionnal display to adapt the desktop to my 4K display (150%), 
a second dead small mouse cursor with the orginal size (100%) is still there. 
This bug was reported by many users.
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 17:26:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-12 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/+bug/1879071/+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 1879075] [NEW] Bluetooth sound card not detected.

2020-05-16 Thread chris gibbons

Public bug reported:

not connecting to my Bluetooth headphones. same problem on my desktop
computor. all worked ok with 18.04 .sometimes it will connect but after
a few seconds it will disconnect, if i remove the device, and then add
it, i can get it to connect, but YouTube video stalls with no sound, if
i disconnect the headphones, the video plays.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  chris  1501 F pulseaudio
 /dev/snd/controlC0:  chris  1501 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 17:06:19 2020
InstallationDate: Installed on 2020-05-04 (12 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Grumpy_PK
dmi.board.vendor: PK
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-43
dmi.product.sku: 
dmi.product.version: V1.06
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Description changed:

  not connecting to my Bluetooth headphones. same problem on my desktop
- computor. all worked ok with 18.04 sometimes it will connect but after a
- few seconds it will disconnect, if i remove the device, and the add it,
- i can get it to connect, but YouTube video stalls with no sound, if i
- disconnect the headphones, the video plays.
+ computor. all worked ok with 18.04 .sometimes it will connect but after
+ a few seconds it will disconnect, if i remove the device, and then add
+ it, i can get it to connect, but YouTube video stalls with no sound, if
+ i disconnect the headphones, the video plays.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  chris  1501 F pulseaudio
-  /dev/snd/controlC0:  chris  1501 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  chris  1501 F pulseaudio
+  /dev/snd/controlC0:  chris  1501 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 17:06:19 2020
  InstallationDate: Installed on 2020-05-04 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Grumpy_PK
  dmi.board.vendor: PK
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-43
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

Title:
  Bluetooth sound card not detected.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  not connecting to my Bluetooth headphones. same problem on my desktop
  computor. all worked ok with 18.04 .sometimes it will connect but
  after a few seconds it will disconnect, if i remove the device, and
  then add it, i can get it to connect, but YouTube video stalls with no
  sound, if i disconnect the headphones, the video plays.

  ProblemType: Bug
  DistroRelease: U

[Desktop-packages] [Bug 1879076] [NEW] Xorg freeze

2020-05-16 Thread Alex U

Public bug reported:

When in both Firefox and Opera hardware acceleration is on and browser
is running it will trigger freeze with X.OrgX driver on.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 12:17:35 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
GraphicsCard:
 NVIDIA Corporation G84GLM [Quadro FX 1600M] [10de:040d] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell G84GLM [Quadro FX 1600M] [1028:019b]
InstallationDate: Installed on 2020-04-08 (38 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. Precision M6300
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=57f985ce-6982-47e4-8428-74d41764c9ce ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0JM680
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd06/05/2013:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn0JM680:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M6300
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When in both Firefox and Opera hardware acceleration is on and browser
  is running it will trigger freeze with X.OrgX driver on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 12:17:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 1600M] [10de:040d] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G84GLM [Quadro FX 1600M] [1028:019b]
  InstallationDate: Installed on 2020-04-08 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Precision M6300
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=57f985ce-6982-47e4-8428-74d41764c9ce ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus:

[Desktop-packages] [Bug 1860330] Re: After upgrading from Eoan to Focal, I receive the error: "A newer version of Thunderbird may have made changes to your profile which are no longer compatible with

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

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

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

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

Title:
  After upgrading from Eoan to Focal, I receive the error: "A newer
  version of Thunderbird may have made changes to your profile which are
  no longer compatible with this older version. Use this profile only
  with that newer version, or create a new profile for this installation
  of Thunderbird. Creating a new profile requires setting up your
  accounts, calendars and add-ons again."

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  I've only ever used the default Thunderbird that came packaged with
  Ubuntu. After upgrading from Eoan to Focal I receive the following
  popup error dialog:

  "A newer version of Thunderbird may have made changes to your profile
  which are no longer compatible with this older version. Use this
  profile only with that newer version, or create a new profile for this
  installation of Thunderbird. Creating a new profile requires setting
  up your accounts, calendars and add-ons again."

  The only options are "Create New Profile" and "Quit" with no option to
  continue using my old profile.

  I tried running thunderbird -ProfileManager to force my current
  default profile but it continued to give me the same error.

  I'm assuming this is a bug as it's a major inconvenience to have to
  reconfigure Thunderbird from scratch after an upgrade.

  Terminal shows:

  JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error:
  Can't find profile directory.

  And after clicking Quit:

  JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694:
  Error: Phase "xpcom-will-shutdown" is finished, it is too late to
  register completion condition "UserInteractionTimer 1 for document
  7f645eb33000"

  See attached screenshot: focal-thunderbird-profile-bug.png

  Thanks, Sean.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: thunderbird 1:68.4.1+build1-0ubuntu1
  ProcVersionSignature: User Name 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2592 F pulseaudio
  BuildID: 20200110122930
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 20 14:43:03 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-06 (593 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "68.4.1" (prefs.js)
   security.sandbox.plugin.tempDirSuffix: 
"18138464-d6cb-4282-a9d4-88ab6acfec88" (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=68.4.1/20200110122930
   Profile0 (Default) - LastVersion=68.4.1/20200110143530 (Out of date)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to focal on 2020-01-20 (0 days ago)
  dmi.bios.date: 09/05/2018
  dmi.bios.vendor: System76
  dmi.bios.version: 1.05.12-0
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnSystem76:bvr1.05.12-0:bd09/05/2018:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Ga

[Desktop-packages] [Bug 1772683] Re: [snap] Cannot sign a document, gpg keys are not listed

2020-05-16 Thread Sebastian Jentschke

Works in DEB-version, doesn't work in snap (LO 6.4.3.2, Ubuntu 18.04).

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

Title:
  [snap] Cannot sign a document, gpg keys are not listed

Status in LibreOffice:
  Won't Fix
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  (initially reported on the forum: https://forum.snapcraft.io/t
  /libreoffice-snap-missing-features-and-known-bugs/3920/10)

  Libreoffice 6.0.4.2 (64, candidate channel).

  Steps to reproduce:
   1) snap run libreoffice.writer
   2) write something, then save the document (anywhere) on disk
   3) Open the File menu, then Digital Signatures > Digital Signatures…
   4) in the dialog, click "Sign Document…"

  Expected result: your GPG keys are listed

  Current result: no keys are listed

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772683/+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 1879078] [NEW] copy and paste not working properly

2020-05-16 Thread Tim Passingham

Public bug reported:

In 20.04 cut/copy and paste does not work reliably in Writer.

This has been reported in bugzilla, but seems to only affect ubuntu
20.04.

See https://bugs.documentfoundation.org/show_bug.cgi?id=133029

One report included a video.

My report there said:

I copy and paste, and get the previous copy, not the latest one.
Sometimes the last line gets duplicated in a very peculiar way, such
that if I edit it the duplicate gets edited as well. It is very strange.


I'm using Version: 6.4.3.2
Build ID: 1:6.4.3-0ubuntu0.20.04.1
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded

And have also tried the pre-release of 6.4.4.

This is using the ubuntu ppa versions.  It's really quite a serious
problem for anyone using Writer (and maybe other modules).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 18:00:17 2020
InstallationDate: Installed on 2018-05-24 (722 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  copy and paste not working properly

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In 20.04 cut/copy and paste does not work reliably in Writer.

  This has been reported in bugzilla, but seems to only affect ubuntu
  20.04.

  See https://bugs.documentfoundation.org/show_bug.cgi?id=133029

  One report included a video.

  My report there said:

  I copy and paste, and get the previous copy, not the latest one.
  Sometimes the last line gets duplicated in a very peculiar way, such
  that if I edit it the duplicate gets edited as well. It is very
  strange.

  
  I'm using Version: 6.4.3.2
  Build ID: 1:6.4.3-0ubuntu0.20.04.1
  CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

  And have also tried the pre-release of 6.4.4.

  This is using the ubuntu ppa versions.  It's really quite a serious
  problem for anyone using Writer (and maybe other modules).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 18:00:17 2020
  InstallationDate: Installed on 2018-05-24 (722 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1879078/+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 1844453]

2020-05-16 Thread Vermelhusco1904

Here's the relevant pages from Microsoft to address this for connecting
to One Drive via OAuth 2.0:

https://docs.microsoft.com/en-us/azure/active-directory/develop/access-
tokens

https://docs.microsoft.com/en-us/azure/active-
directory/develop/v2-oauth2-auth-code-flow

https://docs.microsoft.com/en-us/onedrive/developer/rest-api/getting-
started/?view=odsp-graph-online

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

Title:
  [upstream] Access to the Google remote account does not work

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I have a Google account with 2FA login, from LibreOffice I try to add the 
remote account, but it doesn't work, it asks me for a 6-digit PIN.
  Investigating to see if it was just my problem, I discovered that this is a 
long-standing LibreOffice bug (1) and seems unresolved.

  The last report confirms this: "2019-07-04 04:44:41 UTC
  This feature doesn't work with my Google account _w/o_
  2FA.

  Bug hasn't be resolved for about 3 years and "very soon"
  we may celebrate 5 years anniversary.  %-("

  1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 17 23:00:10 2019
  InstallationDate: Installed on 2019-02-18 (210 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1844453]

2020-05-16 Thread Vermelhusco1904

Just an FYI. In the "This week in KDE" of May 15th 2020 Nate Ingraham
reported that a similar issue to this one was solved for KMail and
Kontacts.

This is their bug report:
https://bugs.kde.org/show_bug.cgi?id=404990

In comment 122 from that bug report they state the following:

<>

They link to a Reddit topic where a lot of the steps to fix this are detailed!
https://www.reddit.com/r/kde/comments/gi5bol/kmailkontact_oauth_signin_with_gmail_enabled_again/

Here are the relevant comments:

"Hi all,

I would like to share some news :) This morning Google has approved our
verification request to allow KMail/Kontact to sign into Gmail using the
Google Sign In, which supports 2FA out-of-the-box and is more secure,
since KMail/Kontact never sees your password.

If you have your IMAP account in KMail already configured in KMail and
you would like to start using the OAuth sign-in, go to the account
configuration (Settings→Configure KMail→Accounts→Receiving→[your Gmail
IMAP account]→Modify) and in the Advanced tab select "Gmail" in the
Authentication combo box.

If you want to add a new account, the Gmail authentication method will
be chosen automatically by KMail.

I apologize it took so long to make Gmail login work again. The
bureaucracy that had to be sorted out in order to comply with Google
usage policies was non-trivial and I'll admit then whenever I had some
spare time to work on KDE, I usually chose to write some code rather
than read legal documents and write privacy policy...

Should you still see "Sign in with Google temporarily disabled for this
app" or some other error, let me know, please."

"Nothing was wrong with KMail really, but if any application wants to
access Gmail through OAuth, it needs to request access to this part of
API from Google. Google considers Gmail to be a "restricted" scope and
applications needs to pass verification and satisfy some extra
requirements to get access to it. So there's a manual process of
submitting the application for verification, writing a dedicated privacy
policy, having numerous rounds with Google support to clear things app
and making sure everything is aligned with their terms and policies for
accessing the restricted scopes - it might be fun for a lawyer, but it
certainly isn't the kind of activity a programmer would want to do in
their spare time... :)"

Here's more detail to satisfy Google's requirements to link to Gmail:
https://support.google.com/cloud/answer/9110914?hl=en

Additional Requirements for Specific API Scopes:
https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes

Example of privacy policy that Google requires:
https://community.kde.org/KDE_PIM/Privacy_Policy


Hopefully this is enough information for work to be done to fix this bug. It's 
worth research how this works for Microsoft's One Drive as well since that one 
is also broken.

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

Title:
  [upstream] Access to the Google remote account does not work

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I have a Google account with 2FA login, from LibreOffice I try to add the 
remote account, but it doesn't work, it asks me for a 6-digit PIN.
  Investigating to see if it was just my problem, I discovered that this is a 
long-standing LibreOffice bug (1) and seems unresolved.

  The last report confirms this: "2019-07-04 04:44:41 UTC
  This feature doesn't work with my Google account _w/o_
  2FA.

  Bug hasn't be resolved for about 3 years and "very soon"
  we may celebrate 5 years anniversary.  %-("

  1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 17 23:00:10 2019
  InstallationDate: Installed on 2019-02-18 (210 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1844453] Re: [upstream] Access to the Google remote account does not work

2020-05-16 Thread Bug Watch Updater

** Bug watch added: KDE Bug Tracking System #404990
   https://bugs.kde.org/show_bug.cgi?id=404990

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

Title:
  [upstream] Access to the Google remote account does not work

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I have a Google account with 2FA login, from LibreOffice I try to add the 
remote account, but it doesn't work, it asks me for a 6-digit PIN.
  Investigating to see if it was just my problem, I discovered that this is a 
long-standing LibreOffice bug (1) and seems unresolved.

  The last report confirms this: "2019-07-04 04:44:41 UTC
  This feature doesn't work with my Google account _w/o_
  2FA.

  Bug hasn't be resolved for about 3 years and "very soon"
  we may celebrate 5 years anniversary.  %-("

  1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 17 23:00:10 2019
  InstallationDate: Installed on 2019-02-18 (210 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1879087] [NEW] dbus errors, frequent roaming and unstable connectivity

2020-05-16 Thread Thomas M Steenholdt

Public bug reported:

When using this version of wpa_supplicant with my company
WPA2-Enterprise wireless setup, I'm experiencing far too frequent
roaming events (even when not moving around) accompanied by hiccups in
connectivity. I also see these messages in the wpa_supplicant log:

dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

Having done a little research, at least the dbus errors seem to be fixed
by this commit upstream:

https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

So I built a version of wpa_supplicant including this particular patch
and installed on my machine. Apart from solving the dbus errors
completely, it seems to have had a positive impact on the frequent
roaming and unstable connectivity as well (I've run for a day with no
burst of roaming events at all, where they used to happen every few
minutes most of the time.)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: wpasupplicant 2:2.9-1ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sat May 16 16:47:27 2020
InstallationDate: Installed on 2020-05-12 (4 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  dbus errors, frequent roaming and unstable connectivity

Status in wpa package in Ubuntu:
  New

Bug description:
  When using this version of wpa_supplicant with my company
  WPA2-Enterprise wireless setup, I'm experiencing far too frequent
  roaming events (even when not moving around) accompanied by hiccups in
  connectivity. I also see these messages in the wpa_supplicant log:

  dbus: wpa_dbus_property_changed: no property RoamComplete in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property RoamTime in object 
/fi/w1/wpa_supplicant1/Interfaces/3
  dbus: wpa_dbus_property_changed: no property SessionLength in object 
/fi/w1/wpa_supplicant1/Interfaces/3

  Having done a little research, at least the dbus errors seem to be
  fixed by this commit upstream:

  
https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756

  So I built a version of wpa_supplicant including this particular patch
  and installed on my machine. Apart from solving the dbus errors
  completely, it seems to have had a positive impact on the frequent
  roaming and unstable connectivity as well (I've run for a day with no
  burst of roaming events at all, where they used to happen every few
  minutes most of the time.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: wpasupplicant 2:2.9-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat May 16 16:47:27 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+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 1861310] Re: Overlay with shortcut numbers not showing on dock with pressing Super+0 or Super+Q

2020-05-16 Thread Amr Ibrahim

Fixed in Focal.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Overlay with shortcut numbers not showing on dock with pressing
  Super+0 or Super+Q

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  The dock no longer shows the overlay with digits corresponding to
  shortcuts to launch apps (with ). It stopped appearing after I
  upgraded to Eoan.

  The numbers are show neither with q nor by holding .
  Unlike #1846718, no overlay appears when hitting +0 either (or
  some other number), although the corresponding item is
  launched/focused.

  I have tried changing a number of things in org.gnome.shell.extensions
  .dash-to-dock, including setting hot-keys to false, as advised
  [here](https://askubuntu.com/questions/1082772/keyboard-shortcut-for-
  launching-application-from-dock-in-ubuntu-18). Alas, I couldn't make
  it work.

  Not sure if it matters, but this is the second upgrade (install was on
  Cosmic originally). Here is the output of some commands that may be
  relevant:

  $ gsettings get org.gnome.shell enabled-extensions
  ['appindicatorsupp...@rgcjonas.gmail.com', 'gnomeGlobalAppMenu@lestcape', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'remove-activities-but...@missoft.fr', 
'notifications-alert-on-user-m...@hackedbellini.gmail.com', 
'ubuntu-appindicat...@ubuntu.com', 
'alternate-...@gnome-shell-extensions.gcampax.github.com', 
'custom-hot-corn...@janrunx.gmail.com', 'openweather-extens...@jenslody.de', 
'OverviewAllWindows@amiller27', 'system-moni...@paradoxxx.zero.gmail.com', 
'clipboard-indica...@tudmotu.com', 'gTile@vibou', 
'hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz', 
'ubuntu-d...@ubuntu.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com']

  $ ls ~/.local/share/gnome-shell/extensions/
  alternate-...@gnome-shell-extensions.gcampax.github.com
  clipboard-indica...@tudmotu.com
  custom-hot-corn...@janrunx.gmail.com
  drive-m...@gnome-shell-extensions.gcampax.github.com
  gTile@vibou
  hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz
  notifications-alert-on-user-m...@hackedbellini.gmail.com
  openweather-extens...@jenslody.de
  system-moni...@paradoxxx.zero.gmail.com

  $ ls /usr/share/gnome-shell/extensions/
  apps-m...@gnome-shell-extensions.gcampax.github.com
  auto-move-wind...@gnome-shell-extensions.gcampax.github.com
  desktop-icons@csoriano
  drive-m...@gnome-shell-extensions.gcampax.github.com
  horizontal-workspa...@gnome-shell-extensions.gcampax.github.com
  launch-new-insta...@gnome-shell-extensions.gcampax.github.com
  native-window-placem...@gnome-shell-extensions.gcampax.github.com
  places-m...@gnome-shell-extensions.gcampax.github.com
  screenshot-window-si...@gnome-shell-extensions.gcampax.github.com
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com
  user-th...@gnome-shell-extensions.gcampax.github.com
  window-l...@gnome-shell-extensions.gcampax.github.com
  windowsnaviga...@gnome-shell-extensions.gcampax.github.com
  workspace-indica...@gnome-shell-extensions.gcampax.github.com

  $ gsettings list-recursively org.gnome.shell.extensions.dash-to-dock
  org.gnome.shell.extensions.dash-to-dock transparency-mode 'FIXED'
  org.gnome.shell.extensions.dash-to-dock shortcut-text 'q'
  org.gnome.shell.extensions.dash-to-dock apply-custom-theme false
  org.gnome.shell.extensions.dash-to-dock show-favorites true
  org.gnome.shell.extensions.dash-to-dock click-action 'focus-or-previews'
  org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9']
  org.gnome.shell.extensions.dash-to-dock custom-background-color false
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock multi-monitor false
  org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock isolate-workspaces false
  org.gnome.shell.extensions.dash-to-dock shift-click-action 'launch'
  org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0
  org.gnome.shell.extensions.dash-to-dock show-delay 0.25
  org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock show-windows-preview true
  org.gnome.shell.extensions.dash-to-dock show-trash true
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock autohide-in-fullscreen false
  org.gnome.shell.extensions.dash-to-dock icon-size-fixed true
  org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace'
  org.gnome.shell.extensions.dash-to-dock shift-midd

[Desktop-packages] [Bug 1878921] Re: USB 3 NVMe SSD dongle doesn't flip

2020-05-16 Thread Josua Dietze

Thanks for the lsusb output!
It enabled me to provide a solution.

usb_modeswitch can check for additional attributes beside the USB ID,
precisely *because* of those IDs being re-used for different devices.
The original idea was to have one ID for each device model or at least
for one series of devices which are behaving alike. Manufacturers are
messing this up occasionally though.

Fortunately, the previous devices with the ID 1de1:1101 have a specific
entry for the attribute "iManufacturer". It's "actions" for the Pico Pix
and "action" for the picture frame.

Your device has "AMicro". So for the solution of the problem, the only thing
that needs to be done is RENAMING usb_modeswitch's configuration file named
"1de1:1101" to "1de1:1101:uMa=action".
This will make usb_modeswitch work for the previous devices but ignore your
device.

So this is all the maintainers of the "usb-modeswitch-data" package have to do:
In /usr/share/usb_modeswitch unpack the file "configPack.tar.gz". Rename the
file "1de1:1101" as described. Repack the file.

I will do the same upstream, but since Ubuntu seems to be a bit slow
with incorporating updated packages of usb-modeswitch-data, maintainers
may want to patch the currently used version.

** Attachment added: "solution.txt"

https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1878921/+attachment/5372683/+files/solution.txt

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

Title:
USB 3 NVMe SSD dongle doesn't flip

Status in usb-modeswitch package in Ubuntu:
Confirmed

Bug description:
I have a AM8180 AMicro adapter. It is an adapter for an M.2 SSD NVMe
disk to USB 3. It works fine on Windows, but on Ubuntu, when I plug it
in, the drive shows for a second then disappears. If I try to do fdisk
or gparted, it seems to lock something and I can't shutdown the laptop
(it is stuck on the Disk Management Unmounting step.

My info:
1) Release:
Description: Ubuntu 20.04 LTS
Release: 20.04

2) Package version:
usb-modeswitch:
Installed: 2.5.2+repack0-2ubuntu3
Candidate: 2.5.2+repack0-2ubuntu3
Version table:
*** 2.5.2+repack0-2ubuntu3 500
500 http://th.archive.ubuntu.com/ubuntu focal/main amd64 Packages

3) What I expect to happen:
I expect the drive to stay mounted

4) What happened instead:
The disk is mounted then immediately unmount. Before I create the partitions
in Windows, nothing mounted but the disk briefly appeared in the Disk Manager.

Attached is my (filtered) syslog when I plug to the USB-C (notice the message
advising to tell the developers about the model. Maybe it's just vendor info
missing).

I have modified 2 flags in /etc/usb_modeswitch.conf:
- DisableSwitching=0 changed to 1
- #SetStorageDelay=4 changed to un-commented
then restarted. That didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1878921/+subscriptions

[Desktop-packages] [Bug 1879089] [NEW] Single background colour and colour-gradient options are missing after upgrading from 18.04 to 20.04

2020-05-16 Thread antonaid

Public bug reported:

The options for selecting a single colour background, or, a colour gradient 
background, are missing in the settings, after upgrading from 18.04LTS to 
20.04LTS. The upgrade was done according to this guide: 
https://www.linuxtechi.com/upgrade-ubuntu-18-04-lts-to-ubuntu-20-04-lts/
Also tried to make a clean install of 20.04LTS on a virtual machine, with the 
same result, those functions are missing.
Kind regards
Anton

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Single background colour and colour-gradient options are missing after
  upgrading from 18.04 to 20.04

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The options for selecting a single colour background, or, a colour gradient 
background, are missing in the settings, after upgrading from 18.04LTS to 
20.04LTS. The upgrade was done according to this guide: 
https://www.linuxtechi.com/upgrade-ubuntu-18-04-lts-to-ubuntu-20-04-lts/
  Also tried to make a clean install of 20.04LTS on a virtual machine, with the 
same result, those functions are missing.
  Kind regards
  Anton

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1879089/+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 1879090] [NEW] XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set

2020-05-16 Thread kenn

Public bug reported:

I installed Ubuntu 20.04, it is running well. I switched display manager to 
lightdm. I noticed that it fails to set environment variables XDG_SEAT, 
XDG_VTNR, XDG_SESSION_ID.
I also tested gdm3, it's the same. I also tried liveiso to no vail.


apt-cache policy lightdm
lightdm:
  Installed: 1.30.0-0ubuntu3.1
  Candidate: 1.30.0-0ubuntu3.1
  Version table:
 *** 1.30.0-0ubuntu3.1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set

Status in lightdm package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 20.04, it is running well. I switched display manager to 
lightdm. I noticed that it fails to set environment variables XDG_SEAT, 
XDG_VTNR, XDG_SESSION_ID.
  I also tested gdm3, it's the same. I also tried liveiso to no vail.

  
  apt-cache policy lightdm
  lightdm:
Installed: 1.30.0-0ubuntu3.1
Candidate: 1.30.0-0ubuntu3.1
Version table:
   *** 1.30.0-0ubuntu3.1 500
  500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879090/+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 1869561] Re: Libreoffice Help does not work

2020-05-16 Thread Marcos Nascimento

Replacing the main.xcd file is opening the help by the browser FF and
not by the conventional window. :(

ubuntu 20.04
LibreOffice Version: 6.4.3.2
Build ID: 1:6.4.3-0ubuntu0.20.04.1

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

Title:
  Libreoffice Help does not work

Status in libreoffice package in Ubuntu:
  Confirmed
Status in libreoffice source package in Focal:
  Confirmed

Bug description:
  In the latest PPA release of Libreoffice, the Help does not work.  IN
  version 6.3.5.2 it is OK.  I the version below it returns an error.

  Version: 6.4.2.2
  Build ID: 1:6.4.2-0ubuntu0.19.10.3
  CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

  
  The Error is:

  Object not accessible.
  The object cannot be accessed
  due to insufficient user rights.

  
  The Help used to open the help in a browser window.  This latest version 
seems to try to open the old type of local help (rather than using a browser).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+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 1878921] Re: USB 3 NVMe SSD dongle doesn't flip

2020-05-16 Thread Ubuntu Foundations Team Bug Bot

The attachment "solution.txt" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  USB 3 NVMe SSD dongle doesn't flip

Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  I have a AM8180 AMicro adapter. It is an adapter for an M.2 SSD NVMe
  disk to USB 3. It works fine on Windows, but on Ubuntu, when I plug it
  in, the drive shows for a second then disappears. If I try to do fdisk
  or gparted, it seems to lock something and I can't shutdown the laptop
  (it is stuck on the Disk Management Unmounting step.

  My info:
  1) Release:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2) Package version:
  usb-modeswitch:
Installed: 2.5.2+repack0-2ubuntu3
Candidate: 2.5.2+repack0-2ubuntu3
Version table:
   *** 2.5.2+repack0-2ubuntu3 500
  500 http://th.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  3) What I expect to happen:
  I expect the drive to stay mounted

  4) What happened instead:
  The disk is mounted then immediately unmount. Before I create the partitions 
in Windows, nothing mounted but the disk briefly appeared in the Disk Manager.

  
  Attached is my (filtered) syslog when I plug to the USB-C (notice the message 
advising to tell the developers about the model. Maybe it's just vendor info 
missing).

  I have modified 2 flags in /etc/usb_modeswitch.conf:
  - DisableSwitching=0 changed to 1
  - #SetStorageDelay=4 changed to un-commented
  then restarted. That didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1878921/+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 1879044] Re: gnome-shell restarts due to bluetooth disconnection

2020-05-16 Thread Manuel Carro

It also happens when the disconnection is made through the user
interface (either blueman or settings -> bluetooth).

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

Title:
  gnome-shell restarts due to bluetooth disconnection

Status in xorg package in Ubuntu:
  New

Bug description:
  I am logged in an X session with gnome.  Just after logging, I start a
  Sony Bluetooth headphones (WH-1000XM3).  After they connect (and they
  work), I switch them off (using the switch in the headphones).  < 3
  seconds after disconnections, the gnome-session crashes (and
  restarts).

  If I do this in Wayland, since the server does not seem to support
  restarts, I am logged out of the session and the laptop returns to the
  login screen.

  Best,

  Manuel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 11:23:01 2020
  DistUpgraded: 2020-05-09 00:31:28,496 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-03-26 (416 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-05-08 (7 days ago)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET71W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1879044/+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 1878670] Re: Gnome crash frequently

2020-05-16 Thread Kurt Aaholst

As there are no files in /var/crash, I checked the apport-settings:

kaa@kaa-XPS-13-9300:~$ cat /etc/default/apport 
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1

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

Title:
  Gnome crash frequently

Status in OEM Priority Project:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1879096] Re: speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.

2020-05-16 Thread Kai Kasurinen

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

** This bug has been marked a duplicate of bug 1862650
   Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade

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

Title:
  speech-dispatcher; please update the tmpfiles.d/ drop-in  file
  accordingly.

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  user@ubuntu:~$ sudo apt full-upgrade

  Setting up systemd (242-7ubuntu3.8) ...
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher → 
/run/speech-dispatch
  er; please update the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher/.cache → 
/run/speech-d
  ispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher 
→ /
  run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ 
drop-in 
  file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below 
legacy
   directory /var/run/, updating 
/var/run/speech-dispatcher/.cache/speech-dispatch
  er → /run/speech-dispatcher/.cache/speech-dispatcher; please update the 
tmpfiles
  .d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher/log → 
/run/speech-disp
  atcher/log; please update the tmpfiles.d/ drop-in file accordingly.

  Description:  Ubuntu 19.10
  Release:  19.10

  systemd:
Installed: 242-7ubuntu3.8
Candidate: 242-7ubuntu3.8
Version table:
   *** 242-7ubuntu3.8 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   242-7ubuntu3.6 500
  500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 
Packages
   242-7ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  speech-dispatcher:
Installed: 0.9.1-2
Candidate: 0.9.1-2
Version table:
   *** 0.9.1-2 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 15:40:31 2020
  InstallationDate: Installed on 2020-02-27 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1879096/+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 1862650] Re: Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade

2020-05-16 Thread Kai Kasurinen

Fixed in version speech-dispatcher/0.9.1-4

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

** Also affects: speech-dispatcher (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912749
   Importance: Unknown
   Status: Unknown

** Changed in: speech-dispatcher (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd
  upgrade

Status in speech-dispatcher package in Ubuntu:
  Fix Released
Status in speech-dispatcher package in Debian:
  Unknown

Bug description:
  When upgrading to the latest systemd SRU:

  Setting up systemd (242-7ubuntu3.6) ...
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher → 
/run/speech-dispatcher; please upda
  te the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → 
/run/speech-dispatcher/.cach
  e; please update the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.speech-dispatcher → /run/speech-disp
  atcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file 
accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speec
  h-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in 
file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/log → 
/run/speech-dispatcher/log; ple
  ase update the tmpfiles.d/ drop-in file accordingly.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: i3
  Date: Mon Feb 10 10:50:26 2020
  InstallationDate: Installed on 2019-08-13 (181 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: speech-dispatcher
  UpgradeStatus: Upgraded to eoan on 2020-01-10 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1862650/+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 1878707] Re: Openconnect provided DNS servers are not read by NetworkManager

apport information

** Tags added: apport-collected

** Description changed:

  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!
  
  PS: worked without issue on 19.10
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-05-13 (3 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ IpRoute:
+  default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
+  default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
+  169.254.0.0/16 dev wlp4s0 scope link metric 1000 
+  192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
+  192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
+ Package: network-manager 1.22.10-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
+ _MarkForUpload: True
+ mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
+ nmcli-nm:
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1878707/+attachment/5372699/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about

[Desktop-packages] [Bug 1878707] NetDevice.enp0s31f6.txt

apport information

** Attachment added: "NetDevice.enp0s31f6.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372703/+files/NetDevice.enp0s31f6.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372704/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.vpn0.txt

apport information

** Attachment added: "NetDevice.vpn0.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372705/+files/NetDevice.vpn0.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1878707/+attachment/5372701/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372702/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372700/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372731/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372732/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.vpn0.txt

apport information

** Attachment added: "NetDevice.vpn0.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372729/+files/NetDevice.vpn0.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.wlp4s0.txt

apport information

** Attachment added: "NetDevice.wlp4s0.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372730/+files/NetDevice.wlp4s0.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372733/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372734/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.wlp4s0.txt

apport information

** Attachment added: "NetDevice.wlp4s0.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372706/+files/NetDevice.wlp4s0.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372736/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372707/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372737/+files/nmcli-con.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372708/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] nmcli-dev.txt

apport information

** Attachment added: "nmcli-dev.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372738/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1878707/+attachment/5372735/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] modified.conffile..etc.NetworkManager.NetworkManager.conf.txt

apport information

** Attachment added: 
"modified.conffile..etc.NetworkManager.NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372713/+files/modified.conffile..etc.NetworkManager.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372712/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1878707/+attachment/5372723/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372714/+files/nmcli-con.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1878707/+attachment/5372711/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372710/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372726/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.enp0s31f6.txt

apport information

** Attachment added: "NetDevice.enp0s31f6.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372727/+files/NetDevice.enp0s31f6.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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] nmcli-dev.txt

apport information

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

** Description changed:

  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!
  
  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-05-13 (3 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ IpRoute:
+  default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
+  default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
+  169.254.0.0/16 dev wlp4s0 scope link metric 1000 
+  192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
+  192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
+ Package: network-manager 1.22.10-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
+ _MarkForUpload: True
+ modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
+ mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
+ nmcli-nm:
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0u

[Desktop-packages] [Bug 1878707] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372709/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372728/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1878707/+attachment/5372725/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1878707] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1878707/+attachment/5372724/+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/1878707

Title:
  Openconnect provided DNS servers are not read by NetworkManager

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  If I connect using openconnect comamnd line, all works fine!
  If I add connection to NetworkManager, when I connect, I loose dns, and with 
that, all connectivity!

  PS: worked without issue on 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.86.1 dev enp0s31f6 proto dhcp metric 100 
   default via 192.168.86.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.86.0/24 dev enp0s31f6 proto kernel scope link src 192.168.86.220 
metric 100 
   192.168.86.0/24 dev wlp4s0 proto kernel scope link src 192.168.86.245 metric 
600
  Package: network-manager 1.22.10-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-05-14T20:00:14.210715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1878707/+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 1879101] [NEW] Printing pdfs extremely slow

2020-05-16 Thread Eric Hazen

Public bug reported:

HP Laserjet 3030 prints PDFs with photos extremely slowly (sometimes 10 min per 
page).
Worked fine under Ubuntu 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sat May 16 18:14:06 2020
InstallationDate: Installed on 2020-05-12 (4 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat:
 device for hp_LaserJet_3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM023795
 device for hp_LaserJet_3030_fax: 
hpfax:/usb/hp_LaserJet_3030?serial=00CNBM023795
MachineType: MSI MS-7977
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/hp_LaserJet_3030.ppd', '/etc/cups/ppd/hp_LaserJet_3030_fax.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/hp_LaserJet_3030.ppd: Permission 
denied
 grep: /etc/cups/ppd/hp_LaserJet_3030_fax.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=a373b71f-c986-48fa-897f-bb1349f51f82 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.A0
dmi.board.asset.tag: Default string
dmi.board.name: Z170A GAMING M5 (MS-7977)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.A0:bd07/22/2016:svnMSI:pnMS-7977:pvr1.0:rvnMSI:rnZ170AGAMINGM5(MS-7977):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7977
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apparmor apport-bug focal

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

Title:
  Printing pdfs extremely slow

Status in cups package in Ubuntu:
  New

Bug description:
  HP Laserjet 3030 prints PDFs with photos extremely slowly (sometimes 10 min 
per page).
  Worked fine under Ubuntu 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat May 16 18:14:06 2020
  InstallationDate: Installed on 2020-05-12 (4 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat:
   device for hp_LaserJet_3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM023795
   device for hp_LaserJet_3030_fax: 
hpfax:/usb/hp_LaserJet_3030?serial=00CNBM023795
  MachineType: MSI MS-7977
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/hp_LaserJet_3030.ppd', '/etc/cups/ppd/hp_LaserJet_3030_fax.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/hp_LaserJet_3030.ppd: Permission 
denied
   grep: /etc/cups/ppd/hp_LaserJet_3030_fax.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=a373b71f-c986-48fa-897f-bb1349f51f82 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.A0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M5 (MS-7977)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.A0:bd07/22/2016:svnMSI:pnMS-7977:pvr1.0:rvnMSI:rnZ170AGAMINGM5(MS-7977):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7977
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879101/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set

2020-05-16 Thread Gunnar Hjalmarsson

The im-config impact on this issue should be fixed via this upload:

https://launchpad.net/ubuntu/+source/im-config/0.44.1-1ubuntu1

** Changed in: im-config (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue when
  GTK_IM_MODULE=xim is set

Status in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Fix Released
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1760818/+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 1879104] [NEW] Nautilus hangs on restore from rubbish bin

2020-05-16 Thread Paul Tansom

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

Public bug reported:

If there is a file or directory of the same name as one being restored
Nautilus will lock up until you force it to quit.

This can be a failed restore which has copied the file but not set the
date stamp and completed deleting the file from the rubbish bin - so
when you try to restore again the file is already there in a form.

This can also happen if you have created a file or directory of the same
name as the one being restored in the location it is to be restored to.

Clearly you don't want to restore over the top of the new file, but this
should be error trapped and an appropriate message given, preferably
with the option to overwrite or rename on restore.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 00:13:12 2020
InstallationDate: Installed on 2016-08-01 (1384 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: nautilus
UpgradeStatus: Upgraded to focal on 2020-04-29 (17 days ago)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  Nautilus hangs on restore from rubbish bin

Status in nautilus package in Ubuntu:
  New

Bug description:
  If there is a file or directory of the same name as one being restored
  Nautilus will lock up until you force it to quit.

  This can be a failed restore which has copied the file but not set the
  date stamp and completed deleting the file from the rubbish bin - so
  when you try to restore again the file is already there in a form.

  This can also happen if you have created a file or directory of the
  same name as the one being restored in the location it is to be
  restored to.

  Clearly you don't want to restore over the top of the new file, but
  this should be error trapped and an appropriate message given,
  preferably with the option to overwrite or rename on restore.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 00:13:12 2020
  InstallationDate: Installed on 2016-08-01 (1384 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-29 (17 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1879104/+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 1862650] Re: Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade

2020-05-16 Thread Bug Watch Updater

** Changed in: speech-dispatcher (Debian)
   Status: Unknown => Fix Released

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

Title:
  Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd
  upgrade

Status in speech-dispatcher package in Ubuntu:
  Fix Released
Status in speech-dispatcher package in Debian:
  Fix Released

Bug description:
  When upgrading to the latest systemd SRU:

  Setting up systemd (242-7ubuntu3.6) ...
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher → 
/run/speech-dispatcher; please upda
  te the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → 
/run/speech-dispatcher/.cach
  e; please update the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.speech-dispatcher → /run/speech-disp
  atcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file 
accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below 
legacy directory /var/run/, updating 
/var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speec
  h-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in 
file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below 
legacy directory /var/run/, updating /var/run/speech-dispatcher/log → 
/run/speech-dispatcher/log; ple
  ase update the tmpfiles.d/ drop-in file accordingly.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: i3
  Date: Mon Feb 10 10:50:26 2020
  InstallationDate: Installed on 2019-08-13 (181 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: speech-dispatcher
  UpgradeStatus: Upgraded to eoan on 2020-01-10 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1862650/+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 1879104] Re: Nautilus hangs on restore from rubbish bin

2020-05-16 Thread Paul White

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1839380, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.

Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1839380
   Nautilus freezes when restoring files and a copy already exists

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

Title:
  Nautilus hangs on restore from rubbish bin

Status in nautilus package in Ubuntu:
  New

Bug description:
  If there is a file or directory of the same name as one being restored
  Nautilus will lock up until you force it to quit.

  This can be a failed restore which has copied the file but not set the
  date stamp and completed deleting the file from the rubbish bin - so
  when you try to restore again the file is already there in a form.

  This can also happen if you have created a file or directory of the
  same name as the one being restored in the location it is to be
  restored to.

  Clearly you don't want to restore over the top of the new file, but
  this should be error trapped and an appropriate message given,
  preferably with the option to overwrite or rename on restore.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 00:13:12 2020
  InstallationDate: Installed on 2016-08-01 (1384 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-04-29 (17 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1879104/+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 1879111] [NEW] Sync libcmis 0.5.2-2 (main) from Debian unstable (main)

2020-05-16 Thread Logan Rosen

Public bug reported:

Please sync libcmis 0.5.2-2 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * debian/patches/include-libxml-headers-outside-of-extern-c: Take patch
suggested on upstream bug to fix FTBFS with new ICU. (LP: #1870062)
This change was applied in Debian.

Changelog entries since current groovy version 0.5.2-1ubuntu1:

libcmis (0.5.2-2) unstable; urgency=medium

  * add patch to move include outside of "extern C" block to fix build
with ICU 64.1, thanks Iain Lane (closes: #956115)

 -- Rene Engelhard   Mon, 13 Apr 2020 18:11:03 +0200

** Affects: libcmis (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: libcmis (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync libcmis 0.5.2-2 (main) from Debian unstable (main)

Status in libcmis package in Ubuntu:
  New

Bug description:
  Please sync libcmis 0.5.2-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/patches/include-libxml-headers-outside-of-extern-c: Take patch
  suggested on upstream bug to fix FTBFS with new ICU. (LP: #1870062)
  This change was applied in Debian.

  Changelog entries since current groovy version 0.5.2-1ubuntu1:

  libcmis (0.5.2-2) unstable; urgency=medium

* add patch to move include outside of "extern C" block to fix build
  with ICU 64.1, thanks Iain Lane (closes: #956115)

   -- Rene Engelhard   Mon, 13 Apr 2020 18:11:03 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcmis/+bug/1879111/+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 1879096] [NEW] speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly.

2020-05-16 Thread Hugh

Public bug reported:

user@ubuntu:~$ sudo apt full-upgrade

Setting up systemd (242-7ubuntu3.8) ...
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy
 directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatch
er; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy
 directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-d
ispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy
 directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /
run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in 
file accordingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy
 directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatch
er → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles
.d/ drop-in file accordingly.
[/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy
 directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-disp
atcher/log; please update the tmpfiles.d/ drop-in file accordingly.

Description:Ubuntu 19.10
Release:19.10

systemd:
  Installed: 242-7ubuntu3.8
  Candidate: 242-7ubuntu3.8
  Version table:
 *** 242-7ubuntu3.8 500
500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages
100 /var/lib/dpkg/status
 242-7ubuntu3.6 500
500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages
 242-7ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

speech-dispatcher:
  Installed: 0.9.1-2
  Candidate: 0.9.1-2
  Version table:
 *** 0.9.1-2 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: speech-dispatcher 0.9.1-2
ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 15:40:31 2020
InstallationDate: Installed on 2020-02-27 (79 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: speech-dispatcher
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  speech-dispatcher; please update the tmpfiles.d/ drop-in  file
  accordingly.

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  user@ubuntu:~$ sudo apt full-upgrade

  Setting up systemd (242-7ubuntu3.8) ...
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher → 
/run/speech-dispatch
  er; please update the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher/.cache → 
/run/speech-d
  ispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher 
→ /
  run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ 
drop-in 
  file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below 
legacy
   directory /var/run/, updating 
/var/run/speech-dispatcher/.cache/speech-dispatch
  er → /run/speech-dispatcher/.cache/speech-dispatcher; please update the 
tmpfiles
  .d/ drop-in file accordingly.
  [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below 
legacy
   directory /var/run/, updating /var/run/speech-dispatcher/log → 
/run/speech-disp
  atcher/log; please update the tmpfiles.d/ drop-in file accordingly.

  Description:  Ubuntu 19.10
  Release:  19.10

  systemd:
Installed: 242-7ubuntu3.8
Candidate: 242-7ubuntu3.8
Version table:
   *** 242-7ubuntu3.8 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   242-7ubuntu3.6 500
  500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 
Packages
   242-7ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  speech-dispatcher:
Installed: 0.9.1-2
Candidate: 0.9.1-2
Ve

[Desktop-packages] [Bug 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

2020-05-16 Thread Nate

I am brand new to linux. Just purchased a System76 laptop that shipped
to me with PopOS 20.04 installed. In checking out the new system, I can
confirm this bug exists there too (makes sense, given the ubuntu base).

Launching the Fonts app from their launcher bring the app up, but that's as far 
as it goes. It becomes immediately unresponsive and the window cannot be closed.
I am only able to exit by ending the process. Repeated a couple times with the 
same results.

I googled the issue and found this thread.

Going from the posts above, I launched the 'gnome-font-viewer' from the command 
line.
In doing so, the app launched, and appears to be fully functional. Subsequent 
launches both from the command line, and the gui launcher now, are also 
functional.

The first launch from the command line did generate the error message
below however. Since I've never used linux, I don't know what it means,
but maybe it'll help.

Gtk-Message: 17:33:41: Failed to load module "appmenu-gtk-module"

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of
  application during ISO testing of a live-session.

  Application will crash if there is an attempt to close it or scroll
  through fonts. On one occasion my laptop was rendered unusable when
  Firefox was launched while trying to report the crash to Launchpad.

  After the bug report has been sent gnome-font-viewer will freeze when
  automatically restarted. No fonts are displayed.

  Work around
  ---
  gnome-font-viewer appears to start correctly when started from the command 
line of my Ubuntu 20.04 installation. Then subsequent attempts to start the 
program succeed when started from the dock or the Application Overview.

  I have found that this work around wasn't necessary when using Xubuntu
  20.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.416
  CurrentDesktop: XFCE
  Date: Wed Sep 25 17:34:17 2019
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
  ProcCmdline: gnome-font-viewer
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+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 1879113] [NEW] package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

2020-05-16 Thread Power Station

Public bug reported:

Installing ra1nstorm virtual Mac

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-gi-cairo 3.26.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun May 17 13:06:06 2020
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2020-05-16 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.3
SourcePackage: pygobject
Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in pygobject package in Ubuntu:
  New

Bug description:
  Installing ra1nstorm virtual Mac

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-gi-cairo 3.26.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun May 17 13:06:06 2020
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-05-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.3
  SourcePackage: pygobject
  Title: package python3-gi-cairo 3.26.1-2ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1879113/+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 1879114] [NEW] Sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main)

2020-05-16 Thread Logan Rosen

Public bug reported:

Please sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * debian/control: Build-Depends on the versioned python binary
  * debian/patches/vapi-skip-properties.patch:
- Disable properties that fail to build on newer versions of Vala and aren't
  required
  * Drop dependency on python and python3; package should not depend on
python just because it provides python bindings.
  * debian/patches/build_no_werror.patch
- Don't build with Werror, it makes the build fail on some glib
  deprecations (lp: #1843730)
Both of the patch files were incorporated into Debian. They dropped Python 2 
support, so the versioned build dependency is no longer relevant. They also 
dropped the hardcoded dependencies on python/python3 for gir1.2-dee-1.0.

Changelog entries since current groovy version
1.2.7+17.10.20170616-4ubuntu6:

dee (1.2.7+17.10.20170616-6) unstable; urgency=low

  * Bumped dh to 12.
  * Updated Standards-Version to 4.4.0
  * Added patches from Ubuntu:
+ build_no_werror.patch: Don't build with Werror (Closes: #940163)
+ vapi-skip-properties.patch: Disable properties that fail to build
  on newer versions of Vala and aren't required.
  * Removed python2 support (Closes: #936379)
  * debian/rules:
+ Update for dh 12.
  * Updated examples.

 -- Kartik Mistry   Mon, 30 Sep 2019 23:12:16 +0530

dee (1.2.7+17.10.20170616-5) unstable; urgency=low

  * Do not add unnecessary dependency on python. Thanks to
Steve Langasek for patch. (Closes: #922632)
  * Added debian/gitlab-ci.yml for pipeline.

 -- Kartik Mistry   Thu, 21 Feb 2019 10:35:44 +0530

** Affects: dee (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: dee (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable (main)

Status in dee package in Ubuntu:
  New

Bug description:
  Please sync dee 1.2.7+17.10.20170616-6 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/control: Build-Depends on the versioned python binary
* debian/patches/vapi-skip-properties.patch:
  - Disable properties that fail to build on newer versions of Vala and 
aren't
required
* Drop dependency on python and python3; package should not depend on
  python just because it provides python bindings.
* debian/patches/build_no_werror.patch
  - Don't build with Werror, it makes the build fail on some glib
deprecations (lp: #1843730)
  Both of the patch files were incorporated into Debian. They dropped Python 2 
support, so the versioned build dependency is no longer relevant. They also 
dropped the hardcoded dependencies on python/python3 for gir1.2-dee-1.0.

  Changelog entries since current groovy version
  1.2.7+17.10.20170616-4ubuntu6:

  dee (1.2.7+17.10.20170616-6) unstable; urgency=low

* Bumped dh to 12.
* Updated Standards-Version to 4.4.0
* Added patches from Ubuntu:
  + build_no_werror.patch: Don't build with Werror (Closes: #940163)
  + vapi-skip-properties.patch: Disable properties that fail to build
on newer versions of Vala and aren't required.
* Removed python2 support (Closes: #936379)
* debian/rules:
  + Update for dh 12.
* Updated examples.

   -- Kartik Mistry   Mon, 30 Sep 2019 23:12:16 +0530

  dee (1.2.7+17.10.20170616-5) unstable; urgency=low

* Do not add unnecessary dependency on python. Thanks to
  Steve Langasek for patch. (Closes: #922632)
* Added debian/gitlab-ci.yml for pipeline.

   -- Kartik Mistry   Thu, 21 Feb 2019 10:35:44 +0530

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1879114/+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 1870270] Re: gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from intel_flush_front() from intel_glFlush()

2020-05-16 Thread hn23

@Daniel, 
thank you for the work on this! 

I will add the PPA you made and test it. 
Recently I came to think that this issue might actually be due to a bad kernel 
module which I am running on my system (DiplayLink USD Docking station). 
I installed the module on a second PC after which similar problems as in this 
book started. 
I will get back to you once I get a change to verify the fixes from your PPA. 

I don't know the flow so well on launchpad: is there some time window
until this ticket should be closed?

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

Title:
  gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from
  intel_flush_front() from intel_glFlush()

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Eoan:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter package in CentOS:
  Unknown

Bug description:
  [Impact]

  gnome-shell crashes a lot on bionic:
  https://errors.ubuntu.com/problem/3841a5bc586bc3f532d2313a35f51e511772751f

  [Test Case]

  ** Someone who can reproduce the crash please fill this in **

  [Regression Potential]

  Low. The same fix has been released to newer versions already for most
  of a year.

  [Other Info]

  gnome shell crashed / froze while switching keyboard layouts.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.13
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Mar 31 22:47:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1571973788
  InstallationDate: Installed on 2020-03-13 (19 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  SegvAnalysis:
   Segfault happened at: 0x7fedbfa22393:jmpq   *%rax
   PC (0x7fedbfa22393) ok
   source "*%rax" (0xfffaffed90151620) not located in a known VMA region 
(needed readable region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgbm.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870270/+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 1879054] Re: No sound after 20.04 update

2020-05-16 Thread Hui Wang

Is the package timidity installed on your machine? If yes, please remove
it. "sudo apt -r timidity;reboot"

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

Title:
  No sound after 20.04 update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After update from 18.04 to 20.04 sound stopped working.
  KDE does not display Xonar sound card at all.

  $ aplay /usr/share/sounds/alsa/Front_Center.wav
  does not make any sound

  Alsamixer displays Xonar set at full volume but changing anything
  there does not seem to have any effect.

  Moving/deleting the pulse config (  ~/.config/pulse/ ) and restarting
  machine did not have any effect.

  
  Running:
  $ sudo alsa force-reload
  fixes the issue (until restart sound is back, and is displayed properly in 
KDE)

  
  (data arecord and cards display same data before and after restart)
  $ arecord -l
   Lista CAPTURE urządzeń 
  karta 0: DX [Xonar DX], urządzenie 0: Multichannel [Multichannel]
    Urządzenia podrzędne: 1/1
    Urządzenie podrzędne #0: subdevice #0
  karta 0: DX [Xonar DX], urządzenie 1: Digital [Digital]
    Urządzenia podrzędne: 1/1
    Urządzenie podrzędne #0: subdevice #0

  $  cat /proc/asound/cards
   0 [DX ]: AV200 - Xonar DX
    Asus Virtuoso 100 at 0xd000, irq 31
   1 [HDMI   ]: HDA-Intel - HDA ATI HDMI
    HDA ATI HDMI at 0xfe96 irq 67

  $ lspci | grep -i audio
  21:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen 
HD Audio]
  23:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  (build in motherboard soundcard is disabled in BIOS)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nait   5242 F pulseaudio
   /dev/snd/controlC1:  nait   5242 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat May 16 14:54:07 2020
  InstallationDate: Installed on 2018-11-11 (552 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-01 (14 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.J0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd09/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879054/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2020-05-16 Thread Kevin Lin

+1

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1879117] [NEW] desktop icon get pixel error

2020-05-16 Thread Le Trong Bao

Public bug reported:

temporarily fixed by changing tweak options

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 10:15:21 2020
DisplayManager: gdm3
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-osp1-20171027-1
InstallationDate: Installed on 2018-11-20 (543 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-05-04 (12 days ago)

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


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

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

Title:
  desktop icon get pixel error

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  temporarily fixed by changing tweak options

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 10:15:21 2020
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2018-11-20 (543 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-05-04 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879117/+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 1867490] Re: Persistent GNOME Application Platform update that won't install