Connman issue on Lubuntu Next 18.04: wifi works (after writing "sudo apt-get install bcmwl-kernel-source" and removing Connman). After reinstalling Connman, the conexion is lost again.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lubuntu-meta (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
Connman issue on Lubuntu Next 18.04: wifi works (after writing "sudo apt-get install bcmwl-kernel-
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: connman 1.35-6
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: LXQt
Date: Sat Apr 21 17:18:18 2018
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2018-04-21 (0 days ago)
InstallationMedia: Lubuntu-Next 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180420)
MachineType: Hewlett-Packard HP Stream Notebook PC 11
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: connman
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.08
dmi.board.
dmi.board.name: 8023
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 54.12
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnInsyde:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Stream Notebook PC 11
dmi.product.
dmi.sys.vendor: Hewlett-Packard
affects: | connman (Ubuntu) → lubuntu-meta (Ubuntu) |
Changed in lubuntu-meta (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Simon Quigley (tsimonq2) |
Changed in lubuntu-meta (Ubuntu): | |
assignee: | Simon Quigley (tsimonq2) → nobody |
Erm - only two remarks - the problem isn't connman, the problem sit in front of the screen.
* Right now there are two daemons for network handling activated (network-manager and connman). Both managers come with a ui - nm-applet and cmst. So purging connman might be a good idea - or just drop network-manager and nm-applet.
* The real problem is that the connection is created and configured for n-m. if connman is reinstalled afterwards it will mostly win and take over the network handling. But Wifi isn't configured for connman - so i hardly see any bug in connman in this bug - i would call it expected behaviour.