apparmor error causing deauthentication for certain SSID's

[Edgars Piņķis]

dmesg output:
[ 83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/UDisks2" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name=":1.4" pid=1922 label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[ 165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
[ 165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
[ 165.568883] wlan0: authenticated
[ 165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
[ 165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 aid=3)
[ 165.579888] wlan0: associated
[ 165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING)
Release Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Expected outcome:
Connecting to the home network
Actual outcome:
deauthentication by local choice (Reason:3=DEAUTH_LEAVING)
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: edgars 1716 F.... pulseaudio
 /dev/snd/pcmC0D0p: edgars 1716 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-01-07 (195 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 2350BH1
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=acfd7db3-c0d2-4d87-8707-c3be819efb41 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-62-generic N/A
 linux-backports-modules-5.3.0-62-generic N/A
 linux-firmware 1.173.19
Tags: bionic
Uname: Linux 5.3.0-62-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/08/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETA7WW (2.67 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2350BH1
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG1ETA7WW(2.67):bd12/08/2014:svnLENOVO:pn2350BH1:pvrThinkPadT430:rvnLENOVO:rn2350BH1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 2350BH1
dmi.product.sku: LENOVO_MT_2350
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1888390/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

[Sebastien Bacher (seb128)]

the warning you shared indicates that a snap called indicator-sensors tries to talking to udisks without having the proper permission, that's not sign of an authentification issue...

[Edgars Piņķis (eddypin)]

audit: type=1107 audit(1595014020.261:196): pid=1051 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager/ActiveConnection/4" interface="org.freedesktop.NetworkManager.Connection.Active" member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[ 477.870889] audit: type=1107 audit(1595014065.447:197): pid=1051 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[ 477.870985] audit: type=1107 audit(1595014065.447:198): pid=1051 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager/ActiveConnection/4" interface="org.freedesktop.NetworkManager.Connection.Active" member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[ 477.871464] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice (Reason: 3=DEAUTH_LEAVING)

this was the output from dmesg previously before I, along with family members who are more versed in tech in general, attempted to fix the issue, which sadly did not bring results at my home. The behaviour I expected was that my laptop will connect to the home network (already known network) as per usual. What I encountered was/is that whenever I attempt to connect to the network, the ssid is recognized, it briefly attempts to connect before deauthenticating by local choice (Reason:3=DEAUTH_LEAVING).

I have done nothing to cause this to occur. I have done almost everything I can, excluding resetting the settings of the home network

[Sebastien Bacher (seb128)]

The warning you are copying are not related to your connectivity issue, but the problem you describe seems rather one with wpasupplicant or with the driver, I'm reassigning to the kernel

[Sebastien Bacher (seb128)]

Could you give details on the wifi card you have in your computer?

[Edgars Piņķis (eddypin)]

Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

I'm using a Lenovo Thinkpad T430 laptop.
And yeah, sorry for not supplying the correct information, I'm quite new to reporting bugs of this kind and still learning the ropes and copying out the exact dmesg output that I interpret as related (mostly due to appearing in the output just before the deauthentication) seems the proper thing to do.

[Edgars Piņķis (eddypin)]

And christ, I just realized in my post-seizure state, that I have yet to mentioned that I can connect to other networks, including a hotspot created from my phone. I'm not sure if it's any help with this issue though

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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

apport-collect 1888390

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

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

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

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information

[Edgars Piņķis (eddypin)]

apport information