EasyOs_daedalus shutdown error message

[pp4mnklinux]

Do you know what does it mean?

Is it an important error?

How can I solve it? (excuseme if I can't "explain to you" all the situation that motivates this message, but it is large and complicated to be explained... sorry)

The message:

Easy Daedalus64 is now shutting down...
acpid: exiting
ModemManager [3825]: <warm> could not acquire the 'org.freedesktop. ModemManager1 service name'
ModemManager[3825]: <info> ModemManager is shut down

n.b.- It is possible this message appears weeks ago, but I didn't notice it till today because I "never" shutdown the computer, I usually SUSPEND It, so I never saw this system-message when shutting down the computer.

Thanks in advance, have a nice day u all.

CHEERS.

[BarryK]

That message doesn't matter.

We get it when the 'modemmanager' package is installed.
Scarthgap avoids that message because haven't installed modemmanager.

We never figured out the cause.
I recall doing an online search a couple of years ago, didn't find any responses that fixed it.

But I'm sure there must be a fix to make that message go away.
(apart from hiding it)

[rockedge]

Are there 2 different versions of ModemManager installed?

I found this a while back:

the solutions for my troubles can be found at the last section in https://wiki.archlinux.org/title/Mobile ... sing_mmcli

FCC locking.

using lsusb
to find the id of the modem, and adding the correct FCClocking script for that modem with symlink command described in the arch wiki.

Thanks to all for the suggestions that lead to the solution

the thing that was failing was for the modem to go from disabled state to enabled state.

and the service was running, and showing me that the actual problem was not to find the modem because the service status showed modem0 but not able to enable due to invalid transition

that then lead me to look for something about locking or enabling in the wiki, which turned out to be FCC locking

[Jasper]

@BarryK

Would xdg-utils resolve this issue?

https://www.freedesktop.org/wiki/Software/xdg-utils/

[tammi806]

I get that message also.
I've seen that message many times at startup in other Linux distros.
I figured some stuff never starts when booting.
It has never caused a problem on any of my desktops.

[CF-DKS]

I get that message also.
It has never caused a problem on any of my desktops.

Me too. I tend to ignore things I don't understand, especially messages that pass by quickly when booting or shutting down, and so far I've never had a problem. I do find I get different results with different hardware, e.g. I have a desktop with Easy installed to the internal drive. If I don't "babysit" when it is booting, specifically if I let it go through the 15 second hold instead of hitting enter, I get unusual problems with my browser. No idea why, and if I boot from USB it isn't an issue. This has been true from Kirkstone through to current Scarthgap. One of life's little mysteries that I really don't need to solve.

[tammi806]

I get that message also.
It has never caused a problem on any of my desktops.

Me too. I tend to ignore things I don't understand, especially messages that pass by quickly when booting or shutting down, and so far I've never had a problem. I do find I get different results with different hardware, e.g. I have a desktop with Easy installed to the internal drive. If I don't "babysit" when it is booting, specifically if I let it go through the 15 second hold instead of hitting enter, I get unusual problems with my browser. No idea why, and if I boot from USB it isn't an issue. This has been true from Kirkstone through to current Scarthgap. One of life's little mysteries that I really don't need to solve.

Yeah i'm not sure if I quite understand it myself but it has something to do with controlling of the power management from what I read.

https://www.google.com/search?q=acpi&sc ... s-wiz-serp

I used to only see it with AMD processors but now it seems to come up with some of the Intel processors so I don't know.

I use cobbled together Frankenstein builds from many other computers none of the parts match the other and that may have something to do with the error messages I get at startup on my desktops but again can't say for sure.

Since they don't seem to cause any problems that I can find anywhere I don't worry about them.

[Caramel]

The message is generated by ModemManger

Code: Select all

# strings /usr/bin/ModemManager  | grep "could not acquire"
could not acquire the '%s' service name
could not acquire SIM object

It is related to /etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf
(Test : By renaming this file the error message no longer appears)

ModemManager is a DBus-activated daemon which controls mobile broadband
(2G/3G/4G/5G) devices and connections.

ModemManager is called by NetworkManager (see /var/log/messages). It tries to launch a dbus daemon via systemd but systemd is not used in EasyOS hence the error message.

[BarryK]

ModemManager is called by NetworkManager (see /var/log/messages). It tries to launch a dbus daemon via systemd but systemd is not used in EasyOS hence the error message.

Don't forget, these are Devuan packages, without systemd. Any Debian package that requires systemd is replaced by Devuan's own, and Devuan uses elogind.

I'm not sure if I recall, but I think back in Kirkstone or Pyro, packages compiled in OpenEmbedded, with systemd disabled, still got that error message from modemmanager.

[BarryK]

It is related to /etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf
(Test : By renaming this file the error message no longer

I don't think /etc/dbus-1/system.d/ is a systemd thing.

[BarryK]

I'm running Daedalus right now, ModemManager is running:

Code: Select all

# ps | grep Modem
 4444 root      0:00 /usr/sbin/ModemManager
10917 root      0:00 grep Modem
# 

Looking at lines in /var/log/messages:

Code: Select all

# grep -i modem /var/log/messages
Oct 30 16:17:30 EASYPC27182 daemon.info dbus-daemon[4209]: [system] Activating service name='org.freedesktop.ModemManager1' requested by ':1.1' (uid=0 pid=4359 comm="") (using servicehelper)
Oct 30 16:17:30 EASYPC27182 daemon.info ModemManager[4444]: <info>  ModemManager (version 1.20.4) starting in system bus...
Oct 30 16:17:30 EASYPC27182 daemon.info dbus-daemon[4209]: [system] Successfully activated service 'org.freedesktop.ModemManager1'
Oct 30 16:17:30 EASYPC27182 daemon.info NetworkManager[4359]: <info>  [1730276250.3799] modem-manager: ModemManager not available
Oct 30 16:17:30 EASYPC27182 daemon.info NetworkManager[4359]: <info>  [1730276250.4274] modem-manager: ModemManager now available
Oct 30 16:17:32 EASYPC27182 daemon.info ModemManager[4444]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1': not supported by any plugin
Oct 30 16:17:32 EASYPC27182 daemon.info ModemManager[4444]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.6/0000:04:00.0': not supported by any plugin
Oct 30 16:17:32 EASYPC27182 daemon.info ModemManager[4444]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.0/0000:05:00.0': not supported by any plugin

Maybe the problem is simply that there is no modem.

Code: Select all

# mmcli -M
No modems were found

[Caramel]

ModemManager is called by NetworkManager (see /var/log/messages). It tries to launch a dbus daemon via systemd but systemd is not used in EasyOS hence the error message.

Don't forget, these are Devuan packages, without systemd. Any Debian package that requires systemd is replaced by Devuan's own, and Devuan uses elogind.

I'm not sure if I recall, but I think back in Kirkstone or Pyro, packages compiled in OpenEmbedded, with systemd disabled, still got that error message from modemmanager.

See : Content on the page https://pkginfo.devuan.org/cgi-bin/pack ... r=1.20.4-1

The Devuan modemmanager package is the Debian package !

[BarryK]

Searching online, I found my own post from 2020:

https://bkhome.org/news/202010/trouble- ... nager.html

[Caramel]

EDIT : useless post

Observation on Devuan Chimaera:

After the boot ModemManager is activated.
If the service networkmanager is stopped, NetworkManager and ModemManager stopped.
The direct launch of ModemManager do not work like in EasyOS
But after restart of networkmanager(the service), ModemManager is activated again

Llittle experiment on EasyOS :

# service rc.networkmanager stop
Stopping NetworkManager: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory
stopped
# service rc.networkmanager start
Starting NetworkManager daemon: /usr/sbin/NetworkManager

# ps | grep Modem
3596 root 0:00 /usr/sbin/ModemManager
14397 root 0:00 grep Modem

Now ModemManager is activated

EDIT : Useless post.