[Touch-packages] [Bug 1906906] Re: Memory leak in X.org

[Antoine Fontaine]

** Description changed:

  Hi, I think I've found a memory leek in X.org. The memory usage goes up
  and up (I was at ~3.4GB when I decided to open this bug report), and
- barely goes down when I close X clients (windows) (closing half of them
- brought me to 3.3GB).
+ barely goes down when I close X clients (closing half of the windows
+ brought me down to 3.3GB).
  
  https://paste.gnugen.ch/raw/oUhi
  
  I'm using Ubuntu 20.04 LTS and I am kinda stuck with X.org for Wacom
- tablet support. This is quite annoying and made the system hang (out of
- memory -> 100% CPU usage while Linux was trying not to kill anything. A
- force reboot was required). I had to add more swap, because 8GB + 2GB of
- swap (the default) wasn't enough.
+ tablet support. This is quite annoying and made the system hang twice.
+ (The system ran out of memory, which caused 100% CPU usage while Linux
+ was trying not to kill anything, and a force reboot was required). I had
+ to add more swap, because 8GB + the default 2GB of swap weren't enough.
  
  From the debugging X wiki page http://wiki.ubuntu.com/X/Reporting (last 
edited in 2012) :
  ```
  $ sudo cat /sys/kernel/debug/dri/0/i915_gem_objects
  412 shrinkable [0 free] objects, 140279808 bytes
  
  systemd-logind: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 
unbound, 0 closed)
  Xorg: 221 objects, 113086464 bytes (0 active, 52482048 inactive, 33603584 
unbound, 0 closed)
  Xorg: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 unbound, 0 
closed)
  Xorg: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 unbound, 
0 closed)
  gnome-shell: 857 objects, 274239488 bytes (0 active, 127623168 inactive, 
146616320 unbound, 0 closed)
  gnome-shell: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 
unbound, 0 closed)
  Xorg: 1 objects, 4096 bytes (0 active, 0 inactive, 4096 unbound, 0 closed)
  ```
  After conversion, all bytes values are between 100 and 260MiB, which is large 
but not *that* large.
  
  I know the basics of how to use GDB, but don't know how to find what's
  using the memory. I am willing to compile and test a patched package
  someone suggests a patch.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  5 05:51:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
  InstallationDate: Installed on 2020-11-05 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
-  Bus 001 Device 002: ID 8087:8001 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 002 Device 003: ID 5986:0366 Acer, Inc Integrated Camera
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 002: ID 8087:8001 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 002 Device 003: ID 5986:0366 Acer, Inc Integrated Camera
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20CLS28G02
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=356b9ac9-6bdb-4fd6-83a5-5fcec346ace9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET40W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CLS28G02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: 479364
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET40W(1.19):bd12/08/2015:svnLENOVO:pn20CLS28G02:pvrThinkPadX250:rvnLENOVO:rn20CLS28G02:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X250
  dmi.product.name: 20CLS28G02
  dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250
  dmi.product.version: ThinkPad X250
  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.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  

[Touch-packages] [Bug 1906906] [NEW] Memory leak in X.org

[Antoine Fontaine]

Public bug reported:

Hi, I think I've found a memory leek in X.org. The memory usage goes up
and up (I was at ~3.4GB when I decided to open this bug report), and
barely goes down when I close X clients (closing half of the windows
brought me down to 3.3GB).

https://paste.gnugen.ch/raw/oUhi

I'm using Ubuntu 20.04 LTS and I am kinda stuck with X.org for Wacom
tablet support. This is quite annoying and made the system hang twice.
(The system ran out of memory, which caused 100% CPU usage while Linux
was trying not to kill anything, and a force reboot was required). I had
to add more swap, because 8GB + the default 2GB of swap weren't enough.

>From the debugging X wiki page http://wiki.ubuntu.com/X/Reporting (last edited 
>in 2012) :
```
$ sudo cat /sys/kernel/debug/dri/0/i915_gem_objects
412 shrinkable [0 free] objects, 140279808 bytes

systemd-logind: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 
unbound, 0 closed)
Xorg: 221 objects, 113086464 bytes (0 active, 52482048 inactive, 33603584 
unbound, 0 closed)
Xorg: 221 objects, 113086464 bytes (0 active, 0 inactive, 33603584 unbound, 0 
closed)
Xorg: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 unbound, 0 
closed)
gnome-shell: 857 objects, 274239488 bytes (0 active, 127623168 inactive, 
146616320 unbound, 0 closed)
gnome-shell: 857 objects, 274239488 bytes (0 active, 0 inactive, 146616320 
unbound, 0 closed)
Xorg: 1 objects, 4096 bytes (0 active, 0 inactive, 4096 unbound, 0 closed)
```
After conversion, all bytes values are between 100 and 260MiB, which is large 
but not *that* large.

I know the basics of how to use GDB, but don't know how to find what's
using the memory. I am willing to compile and test a patched package
someone suggests a patch.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  5 05:51:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
InstallationDate: Installed on 2020-11-05 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 001 Device 002: ID 8087:8001 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 5986:0366 Acer, Inc Integrated Camera
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20CLS28G02
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=356b9ac9-6bdb-4fd6-83a5-5fcec346ace9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N10ET40W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CLS28G02
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: 479364
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET40W(1.19):bd12/08/2015:svnLENOVO:pn20CLS28G02:pvrThinkPadX250:rvnLENOVO:rn20CLS28G02:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X250
dmi.product.name: 20CLS28G02
dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250
dmi.product.version: ThinkPad X250
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.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
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 ubuntu

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

Title:
  Memory leak in X.org

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi, I think I've found a memory leek in X.org. The memory usage goes
  up and up (I was at ~3.4GB when I decided to open this bug report),
  and barely goes down when I close X clients (closing half of the
  windows brought me down to 3.3GB).

  https://paste.gnugen.ch/raw/oUhi

  I'm using Ubuntu 20.04 LTS and I am kinda 

[Touch-packages] [Bug 1895405] Re: Bluetooth mouse does not work in Ubuntu 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth mouse does not work in Ubuntu 16.04

Status in bluez package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  1. Submitted bug report
  2. Manufactuere of mous is Windows surface mouse pink
  3. Mouse is connected via bluetooth
  4. Mouse uses trackpad
  5. Mouse has 1 physical button, can press on left side or right side of 
button for different functions
  6. Using Ubuntu 16.04

  Wireless bluetooth mouse does not work in Ubuntu 16.04 but works in my
  standard Windows 10 OS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-117.118~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-117-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 12 13:21:38 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:82c1]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:82c1]
  InstallationDate: Installed on 2020-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  Lsusb:
   Bus 002 Device 002: ID 125f:0001 A-DATA Technology Co., Ltd. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=94a7e873-47e3-4c72-af71-ef0c3fb72af1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.39
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 82C1
  dmi.board.vendor: HP
  dmi.board.version: 09.42
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.39:bd11/12/2018:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn82C1:rvr09.42:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Sep 12 13:15:30 2020
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1895405] Re: Bluetooth mouse does not work in Ubuntu 16.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth mouse does not work in Ubuntu 16.04

Status in bluez package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  1. Submitted bug report
  2. Manufactuere of mous is Windows surface mouse pink
  3. Mouse is connected via bluetooth
  4. Mouse uses trackpad
  5. Mouse has 1 physical button, can press on left side or right side of 
button for different functions
  6. Using Ubuntu 16.04

  Wireless bluetooth mouse does not work in Ubuntu 16.04 but works in my
  standard Windows 10 OS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-117.118~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-117-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 12 13:21:38 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:82c1]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:82c1]
  InstallationDate: Installed on 2020-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  Lsusb:
   Bus 002 Device 002: ID 125f:0001 A-DATA Technology Co., Ltd. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic 
root=UUID=94a7e873-47e3-4c72-af71-ef0c3fb72af1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.39
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 82C1
  dmi.board.vendor: HP
  dmi.board.version: 09.42
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.39:bd11/12/2018:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn82C1:rvr09.42:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Sep 12 13:15:30 2020
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1895710] Re: Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden.

[Launchpad Bug Tracker]

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

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

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

Title:
  Die Paketliste oder die Statusdatei konnte nicht eingelesen oder
  geöffnet werden.

Status in apt package in Ubuntu:
  Expired

Bug description:
  The following message popped up:
  Bitte melden Sie einen Fehler im Paket »update-manager« und fügen Sie die 
folgende Fehlermeldung an den Fehlerbericht an:
  E:can not open 
/var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_focal-updates_InRelease - 
fopen (13: Keine Berechtigung), E:Die Paketliste oder die Statusdatei konnte 
nicht eingelesen oder geöffnet werden.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: update-manager 1:20.04.10.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Aptdaemon:
   
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 15 19:00:28 2020
  InstallationDate: Installed on 2020-08-01 (45 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash

[Sandro]

Sorry read the message only partially on my phone at the time.   Here is
the requisite info:

Tested on Ubuntu 20.04 (KDE Neon, the only way this bug manifests
currently, as it only affects systems running Qt >= 5.19.0)

Updated the package and it successfully fixes the bug, using package in
proposed channel: 8.59+17.10.20170606-0ubuntu2.20.04.1

Opening SystemSettings/Online Accounts and adding a new Google account
now works:  A window appears with a web view asking user to submit
authentication credentials.  I added two accounts, and all worked fine.
Removing and re-adding an account also worked.  Closing the window
without completing workflow and trying again also works.  I couldn't
think of any other reasonable scenario.

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

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Committed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons

[Bryce Harrington]

I'd like to give you all an update and outline our plans for this.

The Canonical server team has made analysis of this issue a top
priority.  We've identified and tested out several possible theories.
Our findings suggest that the breakage involves two distinct issues, one
the BindTo= issue mentioned above, the other caused by a bug in the
docker.io package causing the service to stop on package upgrade; see
specifically the service stop command at the end of
/var/lib/dpkg/info/docker.io.prerm.  We'll use LP: #1870514 to track the
former issue, and #1906364 the latter.  LP: #1658691 gives some past
background for reference.

The tricky part is that unfortunately any change we make to docker.io
requires the running of the prerm script (the version of the script
already present on your system, not the one we'd be installing), and
thus triggers the bug.  In other words, updating your system to prevent
the bug will cause one more docker stop.  Thereafter, the upgrade will
not restart the service when rolling out CVE fixes to either containerd
or docker.io; it may prompt to do so if running interactively (e.g.
https://imgur.com/2Za5dbQ.png), otherwise it should respect the debconf
setting.

We would appreciate feedback, testing and/or review of the proposed fix,
available in this PPA:

   https://launchpad.net/~bryce/+archive/ubuntu/containerd-sru-lp1870514
-docker-dh/


** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: containerd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Hirsute)
   Importance: Undecided
   Status: Won't Fix

** Also affects: docker.io (Ubuntu Hirsute)
   Importance: Undecided
   Status: Confirmed

** Also affects: containerd (Ubuntu Hirsute)
   Importance: Undecided
   Status: Confirmed

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: unattended-upgrades (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: containerd (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: containerd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: unattended-upgrades (Ubuntu Groovy)
   Status: New => Won't Fix

** No longer affects: containerd (Ubuntu)

** Changed in: unattended-upgrades (Ubuntu Focal)
   Status: New => Won't Fix

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: docker.io (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: docker.io (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Xenial)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Changed in: docker.io (Ubuntu Xenial)
   Importance: High => Critical

** Changed in: docker.io (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Focal)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Groovy)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Hirsute)
   Importance: Undecided => Critical

** Changed in: docker.io (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: docker.io (Ubuntu Hirsute)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** No longer affects: containerd (Ubuntu Xenial)

** No longer affects: containerd (Ubuntu Bionic)

** No longer affects: containerd (Ubuntu Focal)

** No longer affects: containerd (Ubuntu Groovy)

** No longer affects: containerd (Ubuntu Hirsute)

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

Title:
  unattended-upgrade still restarts blacklisted daemons

Status in docker.io package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Won't Fix
Status in docker.io source package in Xenial:
  In Progress
Status in unattended-upgrades source package in Xenial:
  Won't Fix
Status in docker.io source package in 

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  adcli fails, can't contact LDAP server

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in adcli source package in Bionic:
  In Progress
Status in cyrus-sasl2 source package in Bionic:
  In Progress

Bug description:
  Package: adcli
  Version: 0.8.2-1ubuntu1
  Release: Ubuntu 18.04 LTS

  When trying to join the domain with this new version of adcli, it gets
  to the point of 'Using GSS-SPNEGO for SASL bind' and then it will not
  do anything for 10 minutes. It will then fail, complaining it can't
  reach the LDAP server.

  Logs:
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: process exited: 6459
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain

  On the network level, adcli gets to the point of send an ldap query to
  the domain controller and the domain controller returns an ack tcp
  packet, but then there is no more traffic between the domain
  controller and the server except for ntp packets until it fails.

  The domain controller traffic also shows that it is receiving the ldap
  query packet from the server but it never sends a reply and there is
  no log in directory services regarding the query. We also couldn't
  find anything in procmon regarding this query either.

  Workaround/Fix:
  Downgrading the adcli package back to version 0.8.2-1 fixes the issues and 
domain join works properly again.

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

-- 

[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash

[Sandro]

I can confirm that the updated packages work for me.  After adding them
to my system using -proposed as suggested, I am now able to get the
window to open asking for my google credentials when selecting to add a
new Google account.

As far as I'm concerned this fixes it for me.  Thanks to all for taking
the time to fix this :)

Please note, in case people come back here and start conflating issues
again - the scope of this fix is *only* to get the web view window where
you can enter your Google credentials.  It is well known that there were
other issues that may come along *after* that, but they are not related
to this bug at all.  As long as you get the window where you can enter
your email address, this bug is fixed.

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Committed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

[Ubuntu Foundations Team Bug Bot]

The attachment "Debdiff for adcli on Bionic" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  adcli fails, can't contact LDAP server

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in adcli source package in Bionic:
  In Progress
Status in cyrus-sasl2 source package in Bionic:
  In Progress

Bug description:
  Package: adcli
  Version: 0.8.2-1ubuntu1
  Release: Ubuntu 18.04 LTS

  When trying to join the domain with this new version of adcli, it gets
  to the point of 'Using GSS-SPNEGO for SASL bind' and then it will not
  do anything for 10 minutes. It will then fail, complaining it can't
  reach the LDAP server.

  Logs:
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: process exited: 6459
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain

  On the network level, adcli gets to the point of send an ldap query to
  the domain controller and the domain controller returns an ack tcp
  packet, but then there is no more traffic between the domain
  controller and the server except for ntp packets until it fails.

  The domain controller traffic also shows that it is receiving the ldap
  query packet from the 

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

** Changed in: cyrus-sasl2 (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: cyrus-sasl2 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: cyrus-sasl2 (Ubuntu Bionic)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

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

Title:
  adcli fails, can't contact LDAP server

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in adcli source package in Bionic:
  In Progress
Status in cyrus-sasl2 source package in Bionic:
  In Progress

Bug description:
  Package: adcli
  Version: 0.8.2-1ubuntu1
  Release: Ubuntu 18.04 LTS

  When trying to join the domain with this new version of adcli, it gets
  to the point of 'Using GSS-SPNEGO for SASL bind' and then it will not
  do anything for 10 minutes. It will then fail, complaining it can't
  reach the LDAP server.

  Logs:
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: process exited: 6459
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain

  On the network level, adcli gets to the point of send an ldap query to
  the domain controller and the domain controller returns an ack tcp
  packet, but then there is no more traffic between the domain
  controller and the server except for ntp packets until it fails.

  The domain controller traffic also shows that it is receiving the ldap
  query packet from the server but it never sends a reply and there is
  no log in directory services regarding the query. We also couldn't
  find anything in procmon regarding this query either.

  Workaround/Fix:
  Downgrading the adcli package back to version 0.8.2-1 

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

[Launchpad Bug Tracker]

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

** Changed in: cyrus-sasl2 (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  adcli fails, can't contact LDAP server

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in adcli source package in Bionic:
  In Progress
Status in cyrus-sasl2 source package in Bionic:
  Confirmed

Bug description:
  Package: adcli
  Version: 0.8.2-1ubuntu1
  Release: Ubuntu 18.04 LTS

  When trying to join the domain with this new version of adcli, it gets
  to the point of 'Using GSS-SPNEGO for SASL bind' and then it will not
  do anything for 10 minutes. It will then fail, complaining it can't
  reach the LDAP server.

  Logs:
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: process exited: 6459
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain

  On the network level, adcli gets to the point of send an ldap query to
  the domain controller and the domain controller returns an ack tcp
  packet, but then there is no more traffic between the domain
  controller and the server except for ntp packets until it fails.

  The domain controller traffic also shows that it is receiving the ldap
  query packet from the server but it never sends a reply and there is
  no log in directory services regarding the query. We also couldn't
  find anything in procmon regarding this query either.

  Workaround/Fix:
  Downgrading the adcli package back to version 0.8.2-1 fixes the issues and 
domain join works properly again.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

[Launchpad Bug Tracker]

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

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  adcli fails, can't contact LDAP server

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in adcli source package in Bionic:
  In Progress
Status in cyrus-sasl2 source package in Bionic:
  Confirmed

Bug description:
  Package: adcli
  Version: 0.8.2-1ubuntu1
  Release: Ubuntu 18.04 LTS

  When trying to join the domain with this new version of adcli, it gets
  to the point of 'Using GSS-SPNEGO for SASL bind' and then it will not
  do anything for 10 minutes. It will then fail, complaining it can't
  reach the LDAP server.

  Logs:
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: process exited: 6459
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain

  On the network level, adcli gets to the point of send an ldap query to
  the domain controller and the domain controller returns an ack tcp
  packet, but then there is no more traffic between the domain
  controller and the server except for ntp packets until it fails.

  The domain controller traffic also shows that it is receiving the ldap
  query packet from the server but it never sends a reply and there is
  no log in directory services regarding the query. We also couldn't
  find anything in procmon regarding this query either.

  Workaround/Fix:
  Downgrading the adcli package back to version 0.8.2-1 fixes the issues and 
domain join works properly again.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~bryce/ubuntu/+source/docker.io/+git/docker.io/+merge/394913

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

Title:
  unattended-upgrade still restarts blacklisted daemons

Status in containerd package in Ubuntu:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  Today plenty of our systems running ubuntu 20.04 were restarting the
  docker daemon, even if i blacklisted the docker package. Since docker
  has an dependency on containerd thats the reason why it was restarted.
  IMO the blacklist should also check the full tree of dependencies...
  This should NOT happen!

  From the log you find:

  2020-12-01 06:40:13,881 INFO Starting unattended upgrades script
  2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:13,882 INFO Initial whitelist (not strict):
  2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui 
qemu-system-x86 qemu-utils
  2020-12-01 06:40:19,140 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2020-12-01 06:40:46,996 INFO All upgrades installed
  2020-12-01 06:40:50,732 INFO Starting unattended upgrades script
  2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:50,733 INFO Initial whitelist (not strict):

  Also this happened for us on plenty of our servers almost at the same
  (why the unattended updates are not spread over time?), which
  destroyed the second time an production environment.

  This is not how unattended-upgraded should be, sadly this package lost
  our trust and we disable it and schedule the 'unattended updates' now
  on our own.

  PS: Not to say that on some servers the docker daemon did not even
  restart..

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Brian Murray]

I installed the version of apport from xenial-proposed and no longer
received a Traceback when running the test case.

Preparing to unpack .../python3-apport_2.20.1-0ubuntu2.28_all.deb ...
Unpacking python3-apport (2.20.1-0ubuntu2.28) over (2.20.1-0ubuntu2.27) ...
Preparing to unpack .../apport_2.20.1-0ubuntu2.28_all.deb ...
Unpacking apport (2.20.1-0ubuntu2.28) over (2.20.1-0ubuntu2.27) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for systemd (229-4ubuntu21.29) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
Setting up python3-apport (2.20.1-0ubuntu2.28) ...
Setting up apport (2.20.1-0ubuntu2.28) ...
bdmurray@clean-xenial-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...(no debugging symbols found)...done.
(gdb) Starting program: /bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77b04320 in __read_nocancel () at 
../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) Saved corefile /tmp/tmplo7od5en/my.core
(gdb) ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: called for pid 2915, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: executable: /bin/cat 
(command line "/bin/cat")
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 2923) Fri Dec  4 15:48:31 2020: wrote report 
/tmp/tmplo7od5en/_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
(gdb) --- post-processing /tmp/tmplo7od5en/_bin_cat.1000.crash


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

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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Brian Murray]

I installed the version of apport from bionic-proposed and no longer
received a Traceback when following the test case.

Setting up python3-apport (2.20.9-0ubuntu7.21) ...
Setting up apport (2.20.9-0ubuntu7.21) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for systemd (237-3ubuntu10.43) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
bdmurray@clean-bionic-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...(no debugging symbols found)...done.
(gdb) Starting program: /bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77af2151 in __GI___libc_read (fd=0, buf=0x77fc2000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:27
27  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmp1o0onv61/my.core
(gdb) ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: called for pid 2615, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: executable: /bin/cat 
(command line "/bin/cat")
ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2623) Fri Dec  4 15:42:10 2020: debug: session gdbus call: 
ERROR: apport (pid 2623) Fri Dec  4 15:42:11 2020: wrote report 
/tmp/tmp1o0onv61/_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
(gdb) --- post-processing /tmp/tmp1o0onv61/_bin_cat.1000.crash


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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906627] Re: adcli fails, can't contact LDAP server

[Matthew Ruffell]

Attached is a debdiff to revert the changes we made to adcli to restore
functionality to GSS-API.

** Patch added: "Debdiff for adcli on Bionic"
   
https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1906627/+attachment/5441133/+files/lp1906627_adcli_bionic.debdiff

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

Title:
  adcli fails, can't contact LDAP server

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  New
Status in adcli source package in Bionic:
  In Progress
Status in cyrus-sasl2 source package in Bionic:
  New

Bug description:
  Package: adcli
  Version: 0.8.2-1ubuntu1
  Release: Ubuntu 18.04 LTS

  When trying to join the domain with this new version of adcli, it gets
  to the point of 'Using GSS-SPNEGO for SASL bind' and then it will not
  do anything for 10 minutes. It will then fail, complaining it can't
  reach the LDAP server.

  Logs:
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Authenticated as user: 
domain-join-acco...@domain.com
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com realmd[6419]:  * Using GSS-SPNEGO for 
SASL bind
  Dec 03 01:39:50 example001.domain.com adcli[6459]: GSSAPI client step 1
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup domain 
short name: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using fully qualified 
name: example001.domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain name: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using computer account 
name: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using domain realm: 
domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Calculated computer 
account name from fqdn: EXAMPLE001
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * With user principal: 
host/example001.domain@domain.com
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Generated 120 
character computer password
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  * Using keytab: 
FILE:/etc/krb5.keytab
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Couldn't lookup 
computer account: EXAMPLE001$: Can't contact LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: adcli: joining domain 
domain.com failed: Couldn't lookup computer account: EXAMPLE001$: Can't contact 
LDAP server
  Dec 03 01:55:27 example001.domain.com realmd[6419]: process exited: 6459
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain
  Dec 03 01:55:27 example001.domain.com realmd[6419]:  ! Failed to join the 
domain

  On the network level, adcli gets to the point of send an ldap query to
  the domain controller and the domain controller returns an ack tcp
  packet, but then there is no more traffic between the domain
  controller and the server except for ntp packets until it fails.

  The domain controller traffic also shows that it is receiving the ldap
  query packet from the server but it never sends a reply and there is
  no log in directory services regarding the query. We also couldn't
  find anything in procmon regarding this query either.

  Workaround/Fix:
  Downgrading the adcli package back to version 0.8.2-1 fixes the 

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Brian Murray]

I installed the version of apport from focal-proposed and no longer
received a Traceback when running the traceback.

Unpacking apport (2.20.11-0ubuntu27.14) over (2.20.11-0ubuntu27.12) ...
Setting up python3-apport (2.20.11-0ubuntu27.14) ...
Setting up apport (2.20.11-0ubuntu27.14) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (245.4-4ubuntu3.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
bdmurray@clean-focal-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...
(No debugging symbols found in cat)
(gdb) Starting program: /usr/bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77ed7142 in __GI___libc_read (fd=0, buf=0x77835000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:26
26  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmp3m7fnzeq/my.core
(gdb) ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: called for pid 3172, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: executable: /usr/bin/cat 
(command line "/usr/bin/cat")
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: debug: session gdbus call: 
ERROR: apport (pid 3180) Fri Dec  4 15:33:28 2020: wrote report 
/tmp/tmp3m7fnzeq/_usr_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
[Inferior 1 (process 3172) killed]
(gdb) --- post-processing /tmp/tmp3m7fnzeq/_usr_bin_cat.1000.crash


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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

-- 
Mailing list: 

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Brian Murray]

I installed the version of apport from groovy-proposed and there is no
longer a Traceback when running the test case.

Setting up python3-apport (2.20.11-0ubuntu50.3) ...
Setting up apport (2.20.11-0ubuntu50.3) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Processing triggers for systemd (246.6-1ubuntu1) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
bdmurray@clean-groovy-amd64:~$ python3 generate-sigsegv-crash.py cat
GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from cat...
(No debugging symbols found in cat)
(gdb) Starting program: /usr/bin/cat 

Program received signal SIGSEGV, Segmentation fault.
0x77ed3cb2 in __GI___libc_read (fd=0, buf=0x77837000, 
nbytes=131072) at ../sysdeps/unix/sysv/linux/read.c:26
26  ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) warning: Memory read failed for corefile section, 4096 bytes at 
0xff60.
Saved corefile /tmp/tmpehzet8ma/my.core
(gdb) ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: called for pid 3631, 
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: executable: /usr/bin/cat 
(command line "/usr/bin/cat")
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name o
rg.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: debug: session gdbus call: 
ERROR: apport (pid 3639) Fri Dec  4 15:25:32 2020: wrote report 
/tmp/tmpehzet8ma/_usr_bin_cat.1000.crash
(gdb) Kill the program being debugged? (y or n) [answered Y; input not from 
terminal]
[Inferior 1 (process 3631) killed]
(gdb) --- post-processing /tmp/tmpehzet8ma/_usr_bin_cat.1000.crash


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

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906887] Re: 3rd level key options hidden in Tweaks if show-all-sources is true

[Gunnar Hjalmarsson]

Originally reported at .

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

Title:
  3rd level key options hidden in Tweaks if show-all-sources is true

Status in gnome-tweaks package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  * Enable show-all-sources

gsettings set org.gnome.desktop.input-sources show-all-sources
  'true'

  * Open Tweaks and navigate to Keyboard & Mouse ->
Additional Layout Options -> Key to choose the 3rd level

  * Find that only two odd options are shown

  I would have expected the lv3:* options to be shown, i.e.:

grep lv3 /usr/share/X11/xkb/rules/base.lst

  If I downgrade xkb-data to 2.26-2ubuntu4, the issue is not present. So
  the issue seems to be caused by some kind of incompatibility between
  gnome-tweaks and xkb-data 2.29-2.

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

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

[Touch-packages] [Bug 1906887] [NEW] 3rd level key options hidden in Tweaks if show-all-sources is true

[Gunnar Hjalmarsson]

Public bug reported:

Steps to reproduce:

* Enable show-all-sources

  gsettings set org.gnome.desktop.input-sources show-all-sources 'true'

* Open Tweaks and navigate to Keyboard & Mouse ->
  Additional Layout Options -> Key to choose the 3rd level

* Find that only two odd options are shown

I would have expected the lv3:* options to be shown, i.e.:

  grep lv3 /usr/share/X11/xkb/rules/base.lst

If I downgrade xkb-data to 2.26-2ubuntu4, the issue is not present. So
the issue seems to be caused by some kind of incompatibility between
gnome-tweaks and xkb-data 2.29-2.

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

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal groovy hirsute

** Also affects: xkeyboard-config (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  3rd level key options hidden in Tweaks if show-all-sources is true

Status in gnome-tweaks package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  * Enable show-all-sources

gsettings set org.gnome.desktop.input-sources show-all-sources
  'true'

  * Open Tweaks and navigate to Keyboard & Mouse ->
Additional Layout Options -> Key to choose the 3rd level

  * Find that only two odd options are shown

  I would have expected the lv3:* options to be shown, i.e.:

grep lv3 /usr/share/X11/xkb/rules/base.lst

  If I downgrade xkb-data to 2.26-2ubuntu4, the issue is not present. So
  the issue seems to be caused by some kind of incompatibility between
  gnome-tweaks and xkb-data 2.29-2.

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

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

[Touch-packages] [Bug 1906565] Autopkgtest regression report (apport/2.20.1-0ubuntu2.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apport (2.20.1-0ubuntu2.28) for xenial 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.1-0ubuntu2.28 (i386, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/xenial/update_excuses.html#apport

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906565] Autopkgtest regression report (apport/2.20.9-0ubuntu7.21)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.21) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.9-0ubuntu7.21 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#apport

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

[Tom]

I have the same issue.  On 20.04, pulse audio creates of the HDMI/DP
device on wake after sleep, and starts using it even though I previously
configured the earlier copy of itself to "Off" using pavucontrol.

This is particularly annoying because it the device is built into my
monitor, is crappy, and there is no way to physically turn off the
device.

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

[Tom]

I have the same issue.  On 20.04, pulse audio creates of the HDMI/DP
device on wake after sleep, and starts using it even though I previously
configured the earlier copy of itself to "Off" using pavucontrol.

This is particularly annoying because it the device is built into my
monitor, is crappy, and there is no way to physically turn off the
device.

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Touch-packages] [Bug 1906078] Re: Whoopsie sends bug reports automatically without consent

[Brian Murray]

Do you happen to have the apport-noui package installed?

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

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

Title:
  Whoopsie sends bug reports automatically without consent

Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  So, I just realized about an hour ago that whoopsie has been sending
  bug reports without my consent since May (2020-05-11 to be exact) from
  checking journalctl where I can see lines like these:

  Uploading /var/crash/[...]
  Sent; server replied with: No error
  Response code: 200
  Reported OOPS ID [...]

  I checked the "Diagnostics" GUI in the gnome-control-center and it
  does have "Send error reports to Canonical" set to "Never"... I tried
  switching it to "Manual" and back to "Never" and that did have an
  effect in /etc/, namelely when going from "Never" to "Manual":

    renamed:rc2.d/K01whoopsie -> rc2.d/S01whoopsie
    renamed:rc3.d/K01whoopsie -> rc3.d/S01whoopsie
    renamed:rc4.d/K01whoopsie -> rc4.d/S01whoopsie
    renamed:rc5.d/K01whoopsie -> rc5.d/S01whoopsie
    new file:   systemd/system/multi-user.target.wants/whoopsie.service

  and the opposite effect is achieved when switching back to "Never". So
  far so good, I guess...

  My /etc/ does have a "whoopsie" file (/etc/whoopsie) which doesn't
  seem to be present in clean installations of Ubuntu and which has the
  following contents:

  [General]
  report_metrics=true

  Switching from "true" to "false" does seem to disable whoopsie, so
  that's nice I guess... but what is this file doing here in the first
  place? To clarify, this was originally an Ubuntu 18.04 system which I
  recently upgraded to 20.04 but the unsolicited error report uploads
  have been going on since well before the upgrade so that's not the
  issue.

  I don't remember touching anything on my system relating to apport or
  whoopsie and my shell history doesn't contain anything about whoopsie
  or apport so this situation seems to have occurred on its own (perhaps
  after an update?).

  This is a pretty serious breach of privacy (and of the GDPR) and
  others might also be unknowingly affected like I was, so the team in
  charge of this might want to push an update that for instance resets
  the /etc/whoopsie file if present (if that truly is the problem).

  While I'm at it I would like all the error reports sent from my
  computer to be deleted. Where can I ask for that? I haven't seen an
  option for that anywhere, apart from contacting
  dataprotect...@canonical.com.

  Best regards.

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

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

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

[Steve Langasek]

Hello Brian, or anyone else affected,

Accepted apport into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.28 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

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

[Steve Langasek]

Hello Brian, or anyone else affected,

Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.21 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apport (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

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

[Steve Langasek]

Hello Brian, or anyone else affected,

Accepted apport into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu50.3 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed-bionic

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

[Touch-packages] [Bug 1906565] Re: traceback when running apport as non-root user

[Steve Langasek]

Hello Brian, or anyone else affected,

Accepted apport into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.14 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apport (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

** Changed in: apport (Ubuntu Groovy)
   Status: Incomplete => Fix Committed

** Tags added: verification-needed-groovy

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

Title:
  traceback when running apport as non-root user

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  The apport-test-crashes package, which is used to test the Error Tracker 
deployments, fails produce crash files for binary applications since "various 
security hardening fixes" were included in apport. The problematic change is 
the dropping of supplemental groups in data/apport. This results in a 
PermissionError as it is not the root user who is calling 
/usr/share/apport/apport.

  [Test Case]
  The least convulted test case involves using the generate-sigsegv-crash.py 
script from apport-test-crashes. This ends up using a command similar to 
'/usr/share/apport/apport -p 4077 -s 11 -E /usr/bin/gnome-calculator < 
/tmp/20.10-gnome-calculator.core' which then will encounter the Traceback.

  1) Comment out "check_lock()" in /usr/share/apport/apport (This is necessary 
as we are not running as root)
  2) Put a copy of generate-sigsegv-crash.py on disk.
  3) Run 'python3 /tmp/generate-sigsegv-crash.py cat'
  4) Observe the following Traceback:

  Traceback (most recent call last):
    File "/tmp/tmpvkt5d266/apport", line 599, in 
  drop_privileges(True)
    File "/tmp/tmpvkt5d266/apport", line 125, in drop_privileges
  os.setgroups([])
  PermissionError: [Errno 1] Operation not permitted

  With the version of apport from -proposed you'll receive no such
  Traceback.

  [Regression Potential]
  If there is an error in the python code we code see a new traceback for any 
and all crashes being generated, so ensure regular crash generation works too.

  apport-test-crashes code is here:
  
https://code.launchpad.net/~daisy-pluckers/error-tracker-deployment/test-crashes/

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

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

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

[Steve Langasek]

Hello Sandro, or anyone else affected,

Accepted signon into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Committed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1901609] Re: signond causes qprocess crash

[Steve Langasek]

Hello Sandro, or anyone else affected,

Accepted signon into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.10.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: signon (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

** Changed in: signon (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  signond causes qprocess crash

Status in signon package in Ubuntu:
  Fix Released
Status in signon source package in Focal:
  Fix Committed
Status in signon source package in Groovy:
  Fix Committed
Status in signon source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without the patch users are unable to add google accounts because signond 
crashes.
  This prevents users from using KDE's online accounts feature for google.
  The fix for this is to drop the no-rtti compile flag as qprocess relies on 
type info. This has no real downside for the user as it simply brings in type 
info.

  [Test Case]

  - in a plasma session
  - install kio-gdrive
  - run `systemsettings5 kcm_kaccounts`
  - add a new account
  - click on google
  - wait for login window to appear
  - signond shouldn't be crashing

  [Where problems could occur]

  Cannot think of any. It simply adds type info to the objects. Also
  upstream has rtti disabled for months and I'm not aware of any
  problems.

  [Other Info]

  This is a fairly grave issue as far as user experience is concerned.

  
  

  
  I'm reporting this bug upstream from where I found it, since I've learned 
that the signond package in KDE Neon is sourced from Ubuntu focal.

  This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64)
  from Focal Fossa

  Steps to reproduce:

  1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon)
  2. Install the kaccounts integration and kio-gdrive packages.
  3. Open System settings and navigate to "Online Accounts"
  4. Press "+ Add New Account"
  5. Select "Google"

  Observed behaviour:

  - Window that would ask for authentication fails to load, and Online Accounts 
goes back to overview
  - system logs show a segfault in libqt5core.so which can be traced to a 
failure in qporcess, casued by signond (see links for further details)

  Expected behaviour:
  - New window opens with a webview where Google authentication credentials can 
be posted.
  - When qprocess runs it does not crash.

  Further reference information at the following links:

  1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034

  3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts-
  sso/signond/-/merge_requests/27

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Alexander Selyutin]

I have similar issues - suddenly closed installation. Asrock z370
samsung 860 evo if it matters

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 

[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

[Alistair Cunningham]

This *appears* to be fixed in the latest Ubuntu 20.10 updates.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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

[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

[Alistair Cunningham]

This *appears* to be fixed in the latest Ubuntu 20.10 updates.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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

[Touch-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

[Wayne Schroeder]

Additionally, I've noted that I really need to disable/re-enable
bluetooth to re-associate with the same device that I've unpaired, even
with PPA.  My BT mouse is usable, but significantly more laggy than the
same mouse used via it's 2.4ghz usb, and I use this same model mouse in
BT with win10 and linux on other machines with great results.  Not sure
this isn't a more general issue though, but figured I'd mention it, even
if it is somewhat off-topic for this bug report.

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

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Incomplete
Status in linux-raspi package in Ubuntu:
  Incomplete
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  Incomplete
Status in linux-raspi source package in Groovy:
  Incomplete
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Touch-packages] [Bug 1906869] [NEW] PCI/internal sound card not detected

[Helena Morais]

Public bug reported:

Suddenly microphone not detected anymore. On sound settings there is no
listed input device. It was working before.


alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://br.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status


inxi -SMA
System:Host: Latitude-3410 Kernel: 5.4.0-56-generic x86_64
   bits: 64
   Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.5 LTS
Machine:   Device: laptop System: Dell product: Latitude 3410 serial: N/A
   Mobo: Dell model: 0JYV3W v: A00 serial: N/A
   UEFI: Dell v: 1.4.1 date: 08/26/2020
Audio: Card Intel Device 02c8 driver: snd_hda_intel
   Sound: Advanced Linux Sound Architecture v: k5.4.0-56-generic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-56.62~18.04.1-generic 5.4.73
Uname: Linux 5.4.0-56-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  helena 1506 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  4 15:44:35 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
InstallationDate: Installed on 2020-09-21 (74 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 0JYV3W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd08/26/2020:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn0JYV3W:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 3410
dmi.product.sku: 09EC
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Suddenly microphone not detected anymore. On sound settings there is
  no listed input device. It was working before.

  
  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://br.archive.ubuntu.com/ubuntu bionic/main i386 Packages
  100 /var/lib/dpkg/status

  
  inxi -SMA
  System:Host: Latitude-3410 Kernel: 5.4.0-56-generic x86_64
 bits: 64
 Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.5 LTS
  Machine:   Device: laptop System: Dell product: Latitude 3410 serial: N/A
 Mobo: Dell model: 0JYV3W v: A00 serial: N/A
 UEFI: Dell v: 1.4.1 date: 08/26/2020
  Audio: Card Intel Device 02c8 driver: snd_hda_intel
 Sound: Advanced Linux Sound Architecture v: k5.4.0-56-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-56.62~18.04.1-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  helena 1506 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 15:44:35 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  InstallationDate: Installed on 2020-09-21 (74 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 0JYV3W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Steve Langasek]

** Changed in: ubuntu-cdimage
 Assignee: Shiroe (shiroe26102001) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] nmcli-con.txt

[Bryan J Smalley]

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441089/+files/nmcli-con.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] acpidump.txt

[Bryan J Smalley]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441088/+files/acpidump.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook 

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

[Bryan J Smalley]

apport information

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

** Changed in: ubuntu-mate
   Status: New => Confirmed

** Description changed:

  Hello everybody and thank you in advance for your help.  After a recent
  update, my machine rebooted and appeared to be fine, but after a short
  time the WiFi dropped and the NetworkManager applet shows that the
  interface is down.  I am also getting prompted for a password (which was
  previously saved) and when I click on connect it will establish the
  connection for a short time, but then goes down again.  In some cases
  this is immediate in others, I will be online for up to approximately 15
  minutes before it goes down again.  I have tried restarting
  NetworkManager, but I get the same results (short time up, then down).
  I tried to review log data, but I am not a linux expert and so I'm not
  sure that I am looking at the right log, nor do I know exactly what to
  look for.  Here are some lines from around the time of the disconnect
  and the restarting of NetworkManager:
  
   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: 
disconnected -> scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.6408] device (wlo1): supplicant interface state: scanning -> 
inactive
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.6409] device 

[Touch-packages] [Bug 1906600] nmcli-con.txt

[Bryan J Smalley]

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441061/+files/nmcli-con.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] NetDevice.wlo1.txt

[Bryan J Smalley]

apport information

** Attachment added: "NetDevice.wlo1.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441078/+files/NetDevice.wlo1.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] NetDevice.enp3s0.txt

[Bryan J Smalley]

apport information

** Attachment added: "NetDevice.enp3s0.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441076/+files/NetDevice.enp3s0.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] Lsusb-v.txt

[Bryan J Smalley]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441075/+files/Lsusb-v.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

[Touch-packages] [Bug 1906600] Lsusb-t.txt

[Bryan J Smalley]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441074/+files/Lsusb-t.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

[Touch-packages] [Bug 1906600] Lspci-vt.txt

[Bryan J Smalley]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441072/+files/Lspci-vt.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] acpidump.txt

[Bryan J Smalley]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441060/+files/acpidump.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] device 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook 

[Touch-packages] [Bug 1906600] AlsaInfo.txt

[Bryan J Smalley]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441065/+files/AlsaInfo.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook 

[Touch-packages] [Bug 1906600] Lsusb-t.txt

[Bryan J Smalley]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441046/+files/Lsusb-t.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

[Touch-packages] [Bug 1906600] Lsusb-v.txt

[Bryan J Smalley]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441047/+files/Lsusb-v.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] NetDevice.wlo1.txt

[Bryan J Smalley]

apport information

** Attachment added: "NetDevice.wlo1.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441050/+files/NetDevice.wlo1.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1906600] NetDevice.enp3s0.txt

[Bryan J Smalley]

apport information

** Attachment added: "NetDevice.enp3s0.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441048/+files/NetDevice.enp3s0.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

[Touch-packages] [Bug 1906600] Lspci-vt.txt

[Bryan J Smalley]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1906600/+attachment/5441044/+files/Lspci-vt.txt

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] 

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   

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

[Bryan J Smalley]

apport information

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

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

Title:
  WiFi disconnects continually (goes "down" in NetworkManager)

Status in Ubuntu MATE:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello everybody and thank you in advance for your help.  After a
  recent update, my machine rebooted and appeared to be fine, but after
  a short time the WiFi dropped and the NetworkManager applet shows that
  the interface is down.  I am also getting prompted for a password
  (which was previously saved) and when I click on connect it will
  establish the connection for a short time, but then goes down again.
  In some cases this is immediate in others, I will be online for up to
  approximately 15 minutes before it goes down again.  I have tried
  restarting NetworkManager, but I get the same results (short time up,
  then down).  I tried to review log data, but I am not a linux expert
  and so I'm not sure that I am looking at the right log, nor do I know
  exactly what to look for.  Here are some lines from around the time of
  the disconnect and the restarting of NetworkManager:

   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] device 

[Touch-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)

[Bryan J Smalley]

apport information

** Tags added: apport-collected focal

** Description changed:

  Hello everybody and thank you in advance for your help.  After a recent
  update, my machine rebooted and appeared to be fine, but after a short
  time the WiFi dropped and the NetworkManager applet shows that the
  interface is down.  I am also getting prompted for a password (which was
  previously saved) and when I click on connect it will establish the
  connection for a short time, but then goes down again.  In some cases
  this is immediate in others, I will be online for up to approximately 15
  minutes before it goes down again.  I have tried restarting
  NetworkManager, but I get the same results (short time up, then down).
  I tried to review log data, but I am not a linux expert and so I'm not
  sure that I am looking at the right log, nor do I know exactly what to
  look for.  Here are some lines from around the time of the disconnect
  and the restarting of NetworkManager:
  
   '
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 
'none', sys-iface-state: 'managed')
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3945] device (wlo1): Activation: successful, device activated.
  Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]:   
[1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8909] device (wlo1): supplicant interface state: completed -> 
authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: 
completed -> authenticating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9011] device (wlo1): supplicant interface state: authenticating -> 
associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: 
authenticating -> associating
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (wlo1): supplicant interface state: associating -> 
4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: 
associating -> 4-way handshake
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected 
(reason -1)
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> 
disconnected
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9318] device (wlo1): Activation: (wifi) disconnected during 
association, asking for new key
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 
'supplicant-disconnect', sys-iface-state: 'managed')
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9527] dhcp4 (wlo1): state changed bound -> done
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9544] manager: NetworkManager state is now CONNECTING
  Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:   
[1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 
4-way handshake -> disconnected
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4819] device (wlo1): supplicant interface state: disconnected -> 
scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.4820] device (p2p-dev-wlo1): supplicant management interface state: 
disconnected -> scanning
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.6408] device (wlo1): supplicant interface state: scanning -> 
inactive
  Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]:   
[1606875349.6409] device (p2p-dev-wlo1): supplicant management interface state: 
scanning -> inactive
  Dec 01 21:16:42 bryan-HP-Notebook NetworkManager[22616]:   

[Touch-packages] [Bug 1903849] Re: vim ftbfs

[Brian Murray]

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

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

Title:
  vim ftbfs

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  see
  https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1

  blocking the perl transition

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

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

[Touch-packages] [Bug 1906864] [NEW] [4384FF3, Conexant CX20585, Speaker, Internal] fails after a while

[menou]

Public bug reported:

After a while my laptop is playing music it dies and I have no sound at
all . The time the occur differs 3 mins-20 mins. I run ubuntu-bug audio
and  got here reporting a bug. Also when I had Mint it did that , a week
ago I did a format and install Ubuntu. I choose speaker internal built
in audio _HDA Intel MID from Apport tab.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  menou  1810 F pulseaudio
 /dev/snd/pcmC0D0p:   menou  1810 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  4 19:13:58 2020
InstallationDate: Installed on 2020-11-18 (16 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 Nov 29 06:23:05 Ubaba dbus-daemon[1112]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.27' (uid=125 pid=1344 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
 Nov 29 06:23:05 Ubaba dbus-daemon[1112]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.33' 
(uid=125 pid=1344 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
 Nov 29 06:23:24 Ubaba systemd[1297]: pulseaudio.service: Succeeded.
 Nov 29 06:23:35 Ubaba systemd[1297]: pulseaudio.socket: Succeeded.
Symptom_Type: Sound works for a while, then breaks
Title: [4384FF3, Conexant CX20585, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6MET81WW (1.41 )
dmi.board.name: 4384FF3
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 0
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO:pn4384FF3:pvrThinkPadT510:rvnLENOVO:rn4384FF3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T510
dmi.product.name: 4384FF3
dmi.product.version: ThinkPad T510
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  [4384FF3, Conexant CX20585, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After a while my laptop is playing music it dies and I have no sound
  at all . The time the occur differs 3 mins-20 mins. I run ubuntu-bug
  audio and  got here reporting a bug. Also when I had Mint it did that
  , a week ago I did a format and install Ubuntu. I choose speaker
  internal built in audio _HDA Intel MID from Apport tab.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  menou  1810 F pulseaudio
   /dev/snd/pcmC0D0p:   menou  1810 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 19:13:58 2020
  InstallationDate: Installed on 2020-11-18 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   Nov 29 06:23:05 Ubaba dbus-daemon[1112]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.27' (uid=125 pid=1344 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Nov 29 06:23:05 Ubaba dbus-daemon[1112]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.33' 
(uid=125 pid=1344 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
   Nov 29 06:23:24 Ubaba systemd[1297]: pulseaudio.service: Succeeded.
   Nov 29 06:23:35 Ubaba systemd[1297]: pulseaudio.socket: Succeeded.
  Symptom_Type: Sound works for a while, then breaks
  Title: [4384FF3, Conexant CX20585, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh 

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Shiroe]

** Changed in: ubuntu-cdimage
 Assignee: (unassigned) => Shiroe (shiroe26102001)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  

[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

[Marcelo Pires]

** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu)

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

Title:
  [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working

Status in PulseAudio:
  Unknown
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When you start playing some audio, the sound disappears.

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
Subsystem: ASUSTeK Computer Inc. M5A78L LE
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  
  uname -a
  Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  alsa-info

  
  !!
  !!ALSA Information Script v 0.4.65
  !!

  !!Script ran on: Fri Jun 19 13:38:12 UTC 2020

  
  !!Linux Distribution
  !!--

  Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
  20.04 LTS" HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
  /privacy-policy" UBUNTU_CODENAME=focal

  
  !!DMI Information
  !!---

  Manufacturer:  System manufacturer
  Product Name:  System Product Name
  Product Version:   System Version
  Firmware Version:  1201   
  Board Vendor:  ASUSTeK Computer INC.
  Board Name:M5A78L-M LX/BR

  
  !!ACPI Device Status Information
  !!---

  /sys/bus/acpi/devices/ATK0110:00/status15
  /sys/bus/acpi/devices/PNP0103:00/status15
  /sys/bus/acpi/devices/PNP0400:00/status15
  /sys/bus/acpi/devices/PNP0501:00/status15
  /sys/bus/acpi/devices/PNP0C0C:00/status11
  /sys/bus/acpi/devices/PNP0C0F:00/status9
  /sys/bus/acpi/devices/PNP0C0F:01/status9
  /sys/bus/acpi/devices/PNP0C0F:02/status9
  /sys/bus/acpi/devices/PNP0C0F:03/status9
  /sys/bus/acpi/devices/PNP0C0F:04/status9
  /sys/bus/acpi/devices/PNP0C0F:05/status9
  /sys/bus/acpi/devices/PNP0C0F:06/status9
  /sys/bus/acpi/devices/PNP0C0F:07/status9
  /sys/bus/acpi/devices/device:20/status 15
  /sys/bus/acpi/devices/device:21/status 15

  
  !!Kernel Information
  !!--

  Kernel release:5.4.0-37-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes

  
  !!ALSA Version
  !!

  Driver version: k5.4.0-37-generic
  Library version:1.2.3
  Utilities version:  1.2.2

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe9f4000 irq 16

  
  !!PCI Soundcards installed in the system
  !!--

  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 
Azalia (Intel HDA) [1002:4383]
Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445]

  
  !!Modprobe options (Sound related)
  !!

  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_usb_audio: index=-2
  snd_usb_caiaq: index=-2
  snd_usb_ua101: index=-2
  snd_usb_us122l: index=-2
  snd_usb_usx2y: index=-2
  snd_cmipci: mpu_port=0x330 fm_port=0x388
  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_hda_intel: model=auto
  snd_hda_intel: dmic detect=0

  
  !!Loaded sound module options
  !!---

  !!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
dmic_detect : Y
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
   

[Touch-packages] [Bug 1903614] Re: Please merge kbd 2.3.0-3 from Debian unstable

[Balint Reczey]

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

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

Title:
  Please merge kbd 2.3.0-3 from Debian unstable

Status in kbd package in Ubuntu:
  Fix Released

Bug description:
  Please merge kbd 2.3.0-3 from Debian unstable.

  Updated changelog and diff against Debian unstable is attached below.
  Test build available from
  https://launchpad.net/~waveform/+archive/ubuntu/kbd/+packages

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Steve Langasek]

** Changed in: ubuntu-cdimage
 Assignee: William Chin (wmchin2003) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Triaged
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  

[Touch-packages] [Bug 1647285] Re: SSL trust not system-wide

[Treviño]

Also adding SSSD here, would be easy enough to make its default PAM CA
ring to point to /etc/ssl/certs/ca-certificates.crt by default (and
change-able in settings) but not sure if we want to go this route as it
may make SSSD documentation confusing (as it everywhere mentions
/etc/sssd/pki/sssd_auth_ca_db.pem or /etc/sssd/pki/sssd_auth_ca_db.pem).

Maybe a nice way would be to provide a default sssd.conf file that
explicitly set that instead of hard-coding it, so we won't break current
installations.

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

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Fix Released
Status in sssd package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+subscriptions

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

[Touch-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf

[Stefan Bader]

Could someone try to put the attached script into /etc/kernel/postinst.d
and let me know whether that make installkernel work? Thanks.

** Attachment added: "Copy to /etc/kernel/postinst.d/xx-update-initrd-links"
   
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1877088/+attachment/5441001/+files/xx-update-initrd-links

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

Title:
  [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
  which is required with the default zipl.conf

Status in Ubuntu on IBM z Systems:
  Triaged
Status in debianutils package in Ubuntu:
  New
Status in linux-base package in Ubuntu:
  New

Bug description:
  When testing development kernels I usually rely on the installkernel
  script either through the "make install" target of the Kernel source
  or manually. This used to work great on Ubuntu on Z.

  On Ubuntu 20.04 (freshly installed up to date) this fails however because
  /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
  wrong kernel/initrd combination rendering the system unbootable.

  (with the correct modules already copied to 
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
  # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  run-parts: executing /etc/kernel/postinst.d/zz-zipl 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (3844).
  Done.
  # ls -l /boot
  total 178364
  -rw--- 1 root root135168 May  6 11:52 bootmap
  -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img -> 
initrd.img-5.4.0-29-generic   <== should point to new version
  -rw-r--r-- 1 root root  19663996 May  6 11:42 initrd.img-5.4.0-29-generic
  -rw-r--r-- 1 root root 125339494 May  6 11:52 
initrd.img-5.7.0-rc4-06500-gb67ea026badd
  lrwxrwxrwx 1 root root27 May  6 11:40 initrd.img.old -> 
initrd.img-5.4.0-29-generic
  -rw--- 1 root root   3087920 Apr 29 15:34 System.map-5.4.0-29-generic
  -rw-r--r-- 1 root root   4031691 May  6 11:52 
System.map-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   4031691 May  6 11:49 
System.map-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root37 May  6 11:52 vmlinuz -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw--- 1 root root   8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic
  -rw-r--r-- 1 root root   9080832 May  6 11:52 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  -rw-r--r-- 1 root root   9080832 May  6 11:49 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old
  lrwxrwxrwx 1 root root41 May  6 11:52 vmlinuz.old -> 
vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old

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

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

[Touch-packages] [Bug 1906263] Re: Udev Randomly Doesn't Run Run Script on Remove

[Marjan]

Hello, just to be sure, I've tried with different kernel versions (5.3.18 and 
5.4.81) and the problem's still here.
Same udev version (last) 237-3ubuntu10.43.

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

Title:
  Udev Randomly Doesn't Run Run Script on Remove

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello, I'm running ubuntu (Description: Ubuntu 18.04.4 LTS, Release: 18.04) 
with 5.0.21-sunxi kernel.
  I've updated udev to latest version (237-3ubuntu10.43 500).
  I've written the following rule to create (and removing) symlink to modem 
ports:

  https://pastebin.com/cUwHrf1f

  Since many usb modems hase more than one serial i enumerate them with
  their port number (as just some specific serial can be used to
  connect)

  Here link to mu RUN script /opt/trx/gprs-modem-symlink-handler.bash

  https://pastebin.com/2XTCiV27

  What I expect to happen is having many /dev/ttyTRXGPRSMODEM*
  (enumerated) when I plug-in a modem in the list, and having symlink
  cleared on removing.

  every modem listed in rule is using "option" usb serial driver.

  When i plug in a device I have no issues, everything works fine.
  But sometimes, on removing, I found that some links are still there (it's not 
happening everytime).

  I've enabled debug log with udev and found that sometimes is not
  calling RUN script:

  Here the working situation (3 tty remove events and 3 RUN events):

  https://pastebin.com/EKX5zMh7

  And here is the buggy situation (3 tty remove events, but only 2 RUN
  events) with the same device as the example above:

  https://pastebin.com/dB7ujQ79

  Since it's happening randomly I can't figure out whats causing the
  problem.

  I guess it's not the rule because on an old debian 7 release it's
  working fine, and on the release described above I get others symlinks
  removed even in the buggy situation (as in the example: two are
  removed, one not).

  It seems like sometimes udev ignores totally the run event.

  Last thing to report: I'm not opening these links! So are not locked
  or protected.

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

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

[Touch-packages] [Bug 1840268] Re: Bluetooth headphones and wifi video streaming causes buffering

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth headphones and wifi video streaming causes buffering

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When using headphones via bluetooth and streaming a youtube video in Chrome, 
unacceptable buffering occurs.
  Switch off bluetooth and the video streams as expected.
  Switch on bluetooth and video buffers.
  I tried this several times with consistent results.
  Hardware:
  DELL Inspiron N5110
  processor: Intel® Core™ i3-2350M CPU @ 2.30GHz × 4
  64 bit.
  O.S. Ubuntu 18.04.3
  Headphones: mixcder

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ftf1575 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 14:56:36 2019
  InstallationDate: Installed on 2019-03-11 (156 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 034W60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd09/30/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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