Comments (12)
fenrus75
commented on July 24, 2024
hmm I wonder why we have connman, since we ship systemd-network for
ethernet and NM for wifi
…On Mon, Mar 19, 2018 at 9:38 AM, Geoffroy Van Cutsem < ***@***.***> wrote:
The ConnMan service fails to start in Clear Linux (version 21400). This is
on a bare-metal installation. I tried to start connmand manually but got
the following error:
Connection ":1.157" is not allowed to own the service "net.connman" due to security policies in the configuration file
Here is the complete output of journactl -b -x -u connman*:
-- Logs begin at Mon 2018-03-19 11:46:03 UTC, end at Mon 2018-03-19 19:46:28 UTC. --
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Create a symlink to /etc/resolv.con for ConnMan...
-- Subject: Unit connman-resolvconf.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has begun starting up.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Connection service...
-- Subject: Unit connman.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has begun starting up.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Started Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has finished starting up.
--
-- The start-up result is done.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Main process exited, code=exited, status=1/FAILURE
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Connection service.
-- Subject: Unit connman.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has failed.
--
-- The result is failed.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Unit entered failed state.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Failed with result 'exit-code'.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Create a symlink to /etc/resolv.con for ConnMan...
-- Subject: Unit connman-resolvconf.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has begun starting up.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Started Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has finished starting up.
--
-- The start-up result is done.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Service hold-off time over, scheduling restart.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Create a symlink to /etc/resolv.con for ConnMan...
-- Subject: Unit connman-resolvconf.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has begun starting up.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Stopped Connection service.
-- Subject: Unit connman.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has finished shutting down.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Connection service...
-- Subject: Unit connman.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has begun starting up.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Started Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has finished starting up.
--
-- The start-up result is done.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Main process exited, code=exited, status=1/FAILURE
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Connection service.
-- Subject: Unit connman.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has failed.
--
-- The result is failed.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Unit entered failed state.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Failed with result 'exit-code'.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Create a symlink to /etc/resolv.con for ConnMan...
-- Subject: Unit connman-resolvconf.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has begun starting up.
Mar 19 16:05:03 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Started Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has finished starting up.
--
-- The start-up result is done.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Service hold-off time over, scheduling restart.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Stopped Connection service.
-- Subject: Unit connman.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has finished shutting down.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Connection service...
-- Subject: Unit connman.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has begun starting up.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Create a symlink to /etc/resolv.con for ConnMan...
-- Subject: Unit connman-resolvconf.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has begun starting up.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Started Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has finished starting up.
--
-- The start-up result is done.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Main process exited, code=exited, status=1/FAILURE
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Connection service.
-- Subject: Unit connman.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Unit entered failed state.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Failed with result 'exit-code'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Start request repeated too quickly.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Unit entered failed state.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Failed with result 'start-limit-hit'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Service hold-off time over, scheduling restart.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Start request repeated too quickly.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Failed with result 'start-limit-hit'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Stopped Connection service.
-- Subject: Unit connman.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has finished shutting down.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Connection service...
-- Subject: Unit connman.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has begun starting up.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Main process exited, code=exited, status=1/FAILURE
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Connection service.
-- Subject: Unit connman.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Unit entered failed state.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Failed with result 'exit-code'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Start request repeated too quickly.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Failed with result 'start-limit-hit'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Service hold-off time over, scheduling restart.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Start request repeated too quickly.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Failed with result 'start-limit-hit'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Stopped Connection service.
-- Subject: Unit connman.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has finished shutting down.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Starting Connection service...
-- Subject: Unit connman.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has begun starting up.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Main process exited, code=exited, status=1/FAILURE
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Connection service.
-- Subject: Unit connman.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Unit entered failed state.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Failed with result 'exit-code'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Start request repeated too quickly.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Failed with result 'start-limit-hit'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Service hold-off time over, scheduling restart.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Stopped Connection service.
-- Subject: Unit connman.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has finished shutting down.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Start request repeated too quickly.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Connection service.
-- Subject: Unit connman.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Unit entered failed state.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Failed with result 'exit-code'.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Start request repeated too quickly.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has failed.
--
-- The result is failed.
Mar 19 16:05:04 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Failed with result 'start-limit-hit'.
Mar 19 16:05:12 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Start request repeated too quickly.
Mar 19 16:05:12 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Create a symlink to /etc/resolv.con for ConnMan.
-- Subject: Unit connman-resolvconf.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman-resolvconf.service has failed.
--
-- The result is failed.
Mar 19 16:05:12 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman-resolvconf.service: Failed with result 'start-limit-hit'.
Mar 19 16:05:12 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Start request repeated too quickly.
Mar 19 16:05:12 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: Failed to start Connection service.
-- Subject: Unit connman.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit connman.service has failed.
--
-- The result is failed.
Mar 19 16:05:12 clr-85b6357ca741449d9f79ca1da6a499fd systemd[1]: connman.service: Failed with result 'exit-code'.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPeFS4k0I1IUw_duCAgR4JJZ7RALYSiks5tf97ygaJpZM4Swf2m>
.
from distribution.
gvancuts
commented on July 24, 2024
hmm I wonder why we have connman, since we ship systemd-network for
ethernet and NM for wifi
I wondered about that too. All I know was that it was added recently and based on the message, this was done to <quote>Allow users to manually configure wifi devices at installation time by adding connman to the os-installer bundle</quote> - see https://lists.clearlinux.org/pipermail/dev/2018-January/001247.html
from distribution.
ahkok
commented on July 24, 2024
We've always had connman and it's cli is somewhat intuitive and easy to use, compared to nmcli where the man page "examples" doesn't even contain a section "connect to a wifi network" (for crying out loud), nmcli --help is useless, and you have to go down into man nmcli to the bottom 30 lines to see that the 15th example is a horribly overcomplexified way of connecting to a wifi network.
I am not bitter or anything, but NM without a decent frontend is almost useless for the installer case.
So the proper solution here is to remove connman and add nmcli, but it isn't going to help anyone. The installer needs to support connecting to a simple wifi network and this work is planned, but we haven't gotten to it yet.
from distribution.
gvancuts
commented on July 24, 2024
Is NetworkManager considered a core components or rather something that got pulled when we added the GNOME desktop to Clear Linux? The reason I ask is we have always preferred ConnMan for OS that target embedded/IoT. The proper solution you describe above changes that (and I can't help but see a different solution which would be to have GNOME be able to use ConnMan instead of NM... although I have no idea how hard this would be).
from distribution.
fenrus75
commented on July 24, 2024
gnome to use connman hasn't happened in the last 5+ years and is unlikely
to happen... NM is pretty well hard coded.
THere's no reason to not use NM for IOT tbh
…On Mon, Mar 19, 2018 at 11:49 AM, Geoffroy Van Cutsem < ***@***.***> wrote:
Is NetworkManager considered a core components or rather something that
got pulled when we added the GNOME desktop to Clear Linux? The reason I ask
is we have always preferred ConnMan for OS that target embedded/IoT. The
*proper* solution you describe above changes that (and I can't help but
see a different solution which would be to have GNOME be able to use
ConnMan instead of NM... although I have no idea how hard this would be).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPeFZF5ispp67OEig_7Vp5sSF_wNfZuks5tf_20gaJpZM4Swf2m>
.
from distribution.
gvancuts
commented on July 24, 2024
gnome to use connman hasn't happened in the last 5+ years and is unlikely
to happen... NM is pretty well hard coded.
OK, that's kind of the response I expected.
THere's no reason to not use NM for IOT tbh
OK, I haven't played with NM (beyond using it through the GNOME applet) so I really don't know much about its capabilities. ConnMan seems fairly well accepted in the Embedded/IoT space (inc. automotive) so I hope that NM provides (at least most of) the features they care for.
It would be good to document this at some point (and remove whatever is not necessary from the stack). As an embedded/IoT person, I naturally tried to use ConnMan since it's part of the stack (and also since NM is not installed in the core OS) but realizing that it's broken was surprising (and disappointing).
from distribution.
ahkok
commented on July 24, 2024
Before we throw out babies with bathwater, what's the output of the connmand daemon actually? It exits with -1, so there should be some major error messaging.
Please enable telemetry as well if you can, it will significantly help us spot issues and resolve them.
from distribution.
gvancuts
commented on July 24, 2024
Don't get me wrong, I'm not advocating to throw away any baby (nor even the bathwater for that matter). Without having done a thorough analysis of the situation, the most sensible thing to do for me would be to have NM for the GNOME desktop and ConnMan for Clearlinux images that are more geared towards embedded/IoT. Is there a way with bundles to have ConnMan by default and have it being replaced by NM when you install the GNOME Desktop? It seems like the GNOME desktop is the key driver for keeping NM in there. It's a valid reason but for all other use cases, we could use ConnMan?
I pasted the output as given by journalctl on my first posting (I couldn't see anything interesting there) and there is also the one-line error connmand spits out when I attempt to start it manually - see #24 (comment) . That's all I get even when attempting to start it manually with -d. Is there some other log I could collect to help you?
from distribution.
fenrus75
commented on July 24, 2024
can we at least talk about embedded and iot separately please? iot tends to
have a UI and full connectivity etc...
On Wed, Mar 21, 2018 at 5:05 PM, Arjan van de Ven <[email protected]>
wrote:
… can we at leas
On Wed, Mar 21, 2018 at 4:56 PM, Geoffroy Van Cutsem <
***@***.***> wrote:
> Don't get me wrong, I'm not advocating to throw away any baby (nor even
> the bathwater for that matter). Without having done a thorough analysis of
> the situation, the most sensible thing to do for me would be to have NM for
> the GNOME desktop and ConnMan for Clearlinux images that are more geared
> towards embedded/IoT. Is there a way with bundles to have ConnMan by
> default and have it being replaced by NM when you install the GNOME
> Desktop? It seems like the GNOME desktop is the key driver for keeping NM
> in there. It's a valid reason but for all other use cases, we could use
> ConnMan?
>
> I pasted the output as given by journalctl on my first posting (I
> couldn't see anything interesting there) and there is also the one-line
> error connmand spits out when I attempt to start it manually - see #24
> (comment)
> <#24 (comment)> .
> That's all I get even when attempting to start it manually with -d. Is
> there some other log I could collect to help you?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#24 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABPeFXzd8T1XlnK0OCJASDk_Grtadtflks5tguiXgaJpZM4Swf2m>
> .
>
from distribution.
gvancuts
commented on July 24, 2024
can we at least talk about embedded and iot separately please? iot tends to
have a UI and full connectivity etc...
That would be useful if we want to drill down to the next level as both terms mean different things to different people. I don't think it will fundamentally change the fact that we may need both though.
from distribution.
tpleavitt
commented on July 24, 2024
@gvancuts , can this issue be closed?
from distribution.
gvancuts
commented on July 24, 2024
Yes
from distribution.
Related Issues (20)
- dstat goes wrong HOT 1
- [Missing Instructions] mpv bundle "/usr/lib64/libSvtAv1Enc.so.1: CPU ISA level is lower than required" HOT 3
- xwayland support for wlroots HOT 2
- New SOF (2.8.1) HOT 2
- python: Illegal instruction HOT 6
- [CL 41150] GNOME Night Light is broken HOT 5
- AWS marketplace page has outdated URLs and email link on it
- Azure Marketplace page has outdated URLs on it
- Illegal instruction (core dumped) while build mesa 24.0+1977 package on Xeon 2680V2 HOT 9
- `Illegal instruction` when running `swupd update [whatever]` on Clear Linux 41150 HOT 1
- update opus to 1.5 HOT 1
- The clr-power service may not enable autogroup automatically HOT 4
- UxPlay HOT 2
- The entirety of https://www.clearlinux.org/ is in the header of https://community.clearlinux.org/ HOT 4
- opencl headers to v2023.12.14 HOT 1
- Missing libwinecrt0.a in wine bundle HOT 1
- File content hash mismatch (bad server data?) HOT 1
- zathura to 5.5 HOT 1
- gst-editing-services-1.0.pc
- mingw-gcc to use --enable-threads=posix instead?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from distribution.