[01:55] <lubot> tttomat19 was added by: tttomat19
[02:03] <lubot> <tsimonq2> @tttomat19, Welcome!
[04:22] <lubot> <ShiBonCip> @wxl23, Yes, broadcom here; ie: BCM43142
[04:22] <lubot> <ShiBonCip> sometimes i have to use nmcli to connect
[04:23] <lubot> <wxl23> https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
[04:24] <lubot> <ShiBonCip> @wxl23, thanks
[04:24] <lubot> <wxl23> That's only supported by the proprietary driver which you have to explicitly install
[04:24] <lubot> <ShiBonCip> noted
[04:24] <lubot> <ShiBonCip> no worries
[04:25] <lubot> <wxl23> That's true across all of the Ubuntu flavors and derivatives
[04:26] <lubot> <wxl23> Which is to say it's not an LXQt and/or Lubuntu issue
[04:26] <lubot> <ShiBonCip> noted
[04:27] <lubot> <wxl23> Most distros won't ship proprietary software. That said, it's a general Linux issue
[04:27] <lubot> <wxl23> Or rather an issue with Broadcom not generally supporting open source
[04:27] <lubot> <ShiBonCip> @Sam, but i think that im facing the same problem like sam the network applet not quit intuitive because it only said connected
[04:28] <lubot> <ShiBonCip> *quite
[04:28] <lubot> <ShiBonCip> that's why i usually have to use nmcli rather than network applet
[04:29] <lubot> <wxl23> I would expect erratic or incomplete behavior from the chip given the fact that whatever driver you might be using doesn't fully support it.
[04:29] <lubot> <wxl23> What driver are you using?
[04:30] <lubot> <ShiBonCip> checking
[04:31] <lubot> <ShiBonCip> vendor: Broadcom Corporation
[04:31] <lubot>        physical id: 0
[04:31] <lubot>        bus info: pci@0000:08:00.0
[04:31] <lubot>        logical name: wlan0
[04:31] <lubot>        version: 01
[04:31] <lubot>        capabilities: bus_master cap_list ethernet physical wireless
[04:31] <lubot>        configuration: broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334)
[04:33] <lubot> <wxl23> Ok so you are running the right thing if you're on Xenial or later
[04:34] <lubot> <wxl23> So if there is a bug, figure out how to clearly reproduce it, and then file a bug report.
[04:34] <lubot> <ShiBonCip> yes 16.04
[04:35] <lubot> <wxl23> In other words, you should be able to follow the exact same steps on a freshly installed system and see the exact same results
[04:36] <lubot> <wxl23> It also might be wise to try a newer version and see if it has the same problem
[04:36] <lubot> <ShiBonCip> 17.10 is a good start?
[04:36] <lubot> <wxl23> I'm sure the applet has been updated and I know the wl driver has been
[04:36] <lubot> <wxl23> Yep
[12:08] <lubot> <Sam> https://www.youtube.com/watch?v=Vhh_GeBPOhs
[15:59] <lubot> Dave K was added by: Dave K
[15:59] <lubot> <tsimonq2> @Dave K, Welcome!
[16:00] <lubot> <Dave K> Hey thanks! I was wondering where lubot was piping everything in from lol
[16:03] <lubot> <drkokandy> it's been awhile since I've been actively contributing but hopefully on the "better late than never" side I thought I would try to reconnect and see whether I can be helpful now that things have calmed down in my life
[16:40] <lubot> <tsimonq2> @drkokandy, Awesome :D