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.

Bug #1765974 reported by JyotiGomes
8
This bug affects 1 person
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-source" and removing Connman). After reinstalling Connman, the conexion is lost again. So, the problem must be related to Connman, maybe with the Connman tethering functionality.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: connman 1.35-6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: wl
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=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=5b4ee442-a26f-4ae2-8391-b27828af2706 ro quiet splash vt.handoff=1
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.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8023
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 54.12
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.08:bd12/26/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
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.version: Type1 - ProductConfigId
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
JyotiGomes (jyotigomes) wrote :
summary: Connman issue on Lubuntu Next 18.04: wifi works (after writing sudo apt-
- get install bcmwl-kernel-source" and remove Connman. After reinstalling
- Connman the lost the conexion again.
+ get install bcmwl-kernel-source" and remove Connman). After reinstalling
+ Connman, the conexion is lost again.
summary: - Connman issue on Lubuntu Next 18.04: wifi works (after writing sudo apt-
- get install bcmwl-kernel-source" and remove Connman). After reinstalling
- Connman, the conexion is lost again.
+ 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.
description: updated
Revision history for this message
Alf Gaida (agaida) wrote :

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.

Revision history for this message
JyotiGomes (jyotigomes) wrote : Re: [Bug 1765974] Re: 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.
Download full text (3.3 KiB)

Thanks for the quick response. But may I ask you what do you mean by "the
problem sit in front of the screen"?

...

...

A sábado, 21/04/2018, 18:00, Alf Gaida <email address hidden> escreveu:

> 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.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1765974
>
> Title:
> 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.
>
> Status in connman package in Ubuntu:
> New
>
> Bug description:
> 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. So, the problem must
> be related to Connman, maybe with the Connman tethering functionality.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: connman 1.35-6
> ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
> Uname: Linux 4.15.0-15-generic x86_64
> NonfreeKernelModules: wl
> 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=/boot/vmlinuz-4.15.0-15-generic.efi.signed
> root=UUID=5b4ee442-a26f-4ae2-8391-b27828af2706 ro quiet splash vt.handoff=1
> 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.asset.tag: Type2 - Board Asset Tag
> dmi.board.name: 8023
> dmi.board.vendor: Hewlett-Packard
> dmi.board.version: 54.12
> dmi.chassis.asset.tag: Chassis Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: Hewlett-Packard
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnInsyde:bvrF.08:bd12/26/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
> 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.version: Type1 - ProductConfigId
> dmi.sys....

Read more...

Revision history for this message
JyotiGomes (jyotigomes) wrote :

Thanks for the quick response. But may I ask you what do you mean by "the problem sit in front of the screen"?

Revision history for this message
JyotiGomes (jyotigomes) wrote :

I do not know English very well and if I am not correctly understanding the meaning of the first sentence of the answer, I am sorry. I would like to make it clear that it was not me who installed two Network Managers in the image of Lubuntu Next, both came already installed in the iso. And the least I hope is not to be offended for trying to make an improvement contribution. If it was a joke, it was no fun and I do not agree with such kind of jokes. All the best!

Revision history for this message
Alf Gaida (agaida) wrote :

Jyoti - you are sitting in front of the screen :P - but your report is valid, only about the wrong package.

There is a bug in the l-next images - two daemons for handling network connections - so you should purge the one you don't like. L-next is still work in progress. And if i understood it right the combination network-manager with nm-applet is the solution that will last - so apt purge connman will solve your networking problem. Or vice versa - but in case you go with connman you will have to set up WiFi with connman again.

Revision history for this message
JyotiGomes (jyotigomes) wrote :

Yes, I understood that you were saying that the problem was me, I just hypothesized that I was not fully understanding the meaning of what you said (about the problem being sitting in front of the screen) in a purely rhetorical way. I did this just to not to be forced to say that you should correct these your less good behaviors. You are certainly a good person and can make a lot of good contributions to the world of live software and the society in general, so do not spoil that your good side and the good things that you can do with these sarcastically offensive tirades that may give the idea of bad education (and not only this). You have a good side, follow and develop your good side. Cheers

Simon Quigley (tsimonq2)
affects: connman (Ubuntu) → lubuntu-meta (Ubuntu)
Changed in lubuntu-meta (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Simon Quigley (tsimonq2)
Revision history for this message
Simon Quigley (tsimonq2) wrote :

I actually can't confirm this with Cosmic.

Changed in lubuntu-meta (Ubuntu):
status: Confirmed → Incomplete
Simon Quigley (tsimonq2)
Changed in lubuntu-meta (Ubuntu):
assignee: Simon Quigley (tsimonq2) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in lubuntu-meta (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.