Failed to start modem manager linux

Modem Manager Gui breaks after first time

I installed the application with apt and the first time app running well. I have connected my usb modem huawei e320 and works. the application showed me the sms and when i tried to click to see it, breaks and close. My linux version:

~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial 

~$ modem-manager-gui Connection manager: Network Manager >= 0.9.0 Modem manager: Modem Manager >= 0.7.0 ** (modem-manager-gui:3907): WARNING **: Modem Manager >= 0.7.0: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.79" (uid=1000 pid=3907 comm="modem-manager-gui ") interface="org.freedesktop.ModemManager1.Modem.Contacts" member="GetCount" error name="(unset)" requested_reply="0" destination=":1.2" (uid=0 pid=727 comm="/usr/sbin/ModemManager ") Segmentation fault at address: 0x30 Stack trace: 1. /lib/x86_64-linux-gnu/libc.so.6(+0xc2641) [0x7f5c2b194641] 2. /lib/x86_64-linux-gnu/libc.so.6(+0xc2641) [0x7f5c2b194641] 3. /lib/x86_64-linux-gnu/libc.so.6(strftime_l+0x16) [0x7f5c2b196676] 4. modem-manager-gui(mmgui_str_format_sms_time+0xe7) [0x411b87] 5. modem-manager-gui() [0x42cdb0] 6. modem-manager-gui(mmgui_main_sms_list_fill+0x306) [0x42f226] 7. modem-manager-gui() [0x438450] 8. modem-manager-gui(mmguicore_devices_open+0x149) [0x421879] 9. modem-manager-gui(mmgui_main_device_select_from_list+0x10a) [0x430d8a] 

$ sudo modem-manager-gui No protocol specified Failed to connect to Mir: Failed to connect to server socket: No such file or directory Unable to init server: Could not connect: Connection refused Command line option parsing failed: Cannot open display: 

~$ sudo ModemManager ModemManager[6476]: ModemManager (version 1.4.12) starting in system bus. ModemManager[6476]: Could not acquire the 'org.freedesktop.ModemManager1' service name ModemManager[6476]: ModemManager is shut down 

Источник

Arch Linux

I have a problem with getting modem-manager work under gnome. After first Arch install to this laptop, Network manager didn’t show my 3G-modem, so I installed modem-manager and usb_modeswitch. Modem is Huawei E367 and it works well with wvdial. Only problem is to get it working with Network manager.

From output of dmesg I see that there is an error, when Network manager is trying to start modem-manager:

[ 3224.705193] do_trap: 322 callbacks suppressed [ 3224.705198] modem-manager[3112] trap int3 ip:7ff7baab4143 sp:7fff996e62b0 error:0 [ 3224.719275] modem-manager[3114] trap int3 ip:7f58f4c5e143 sp:7fffc82b2400 error:0 [ 3224.733880] modem-manager[3116] trap int3 ip:7f579dda4143 sp:7fff77910850 error:0 [ 3224.748789] modem-manager[3118] trap int3 ip:7ff752c6f143 sp:7fff8ae42e20 error:0 [ 3224.763501] modem-manager[3120] trap int3 ip:7fb4db83f143 sp:7fff3023cbf0 error:0 [ 3224.777865] modem-manager[3122] trap int3 ip:7fa17a33a143 sp:7fffc1628260 error:0 [ 3224.792165] modem-manager[3124] trap int3 ip:7f00a39fb143 sp:7fff075a0fb0 error:0 [ 3224.806603] modem-manager[3126] trap int3 ip:7f9a62e23143 sp:7fffc2ccfed0 error:0 [ 3224.820736] modem-manager[3128] trap int3 ip:7f3d2994d143 sp:7ffff2581340 error:0 [ 3224.834985] modem-manager[3130] trap int3 ip:7f5adda9a143 sp:7fff8a70a4a0 error:0

From /var/log/messages.log I found also something:

Apr 14 16:02:14 localhost NetworkManager[713]: trying to start the modem manager. Apr 14 16:02:14 localhost dbus[651]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Apr 14 16:02:14 localhost dbus[651]: [system] Successfully activated service 'org.freedesktop.ModemManager' Apr 14 16:02:14 localhost NetworkManager[713]: modem-manager is now available Apr 14 16:02:14 localhost modem-manager: libhal_ctx_init() failed: (null) Apr 14 16:02:14 localhost NetworkManager[713]: the modem manager disappeared

If I try to run modem-manager manually with debug:

$ sudo modem-manager --debug ** ERROR **: libhal_ctx_init() failed: (null) Make sure the hal daemon is running?

So it seems to be because of hal isn’t running, if I try to start hal daemon it fails:

$ sudo /etc/rc.d/hal start :: Starting Hardware Abstraction Layer [FAIL]

I also tried to start hal at boot by putting it to DAEMONS in rc.conf. but didn’t start either.

The laptop is Asus X61SL with x86_64 version of ArchLinux.
Kernel: 3.3.1-1-ARCH

Would be cool if anyone can solve this.

Last edited by Jompu (2012-04-14 20:42:20)

#2 2012-04-14 14:18:51

Re: [SOLVED]Modem-manager won’t start with Network manager

You don’t need hal (it is deprecated), that error message is confusing it. Also you don’t need to start modem-manager usually as it is started by networkmanager (see the log).

You might have to invoke usb_modeswitch manually though.

Best reboot or restart networkmanager with unplugged 3G stick, plug it in and look with «lsusb» for the USB stick. Post that line here, if networkmanager still does not recognise it.

Then change the -v (=vendor) and -p (=product) parameters of the following according to the info given by lsusb and look if that helped switching it to modem mode:

sudo usb_modeswitch -v 12d1 -p 1c0b -M '55534243123456780000000000000011062000000100000000000000000000' 

#3 2012-04-14 14:57:54

Re: [SOLVED]Modem-manager won’t start with Network manager

Thanks for your quick reply Strike0!

I ran lsusb and usb_modeswitch as you instructed:

[louis@Louis-Laptop ~]$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 002 Device 002: ID 045e:00dd Microsoft Corp. Comfort Curve Keyboard 2000 V1.0 Bus 003 Device 002: ID 046d:c526 Logitech, Inc. Nano Receiver Bus 001 Device 006: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard [louis@Louis-Laptop ~]$ sudo usb_modeswitch -v 12d1 -p 1506 -M '55534243123456780000000000000011062000000100000000000000000000' Password: Looking for default devices . found matching product ID adding device Found device in default mode, class or configuration (1) Accessing device 006 on bus 001 . Getting the current device configuration . OK, got current device configuration (1) Using first interface: 0x00 Using endpoints 0x01 (out) and 0x82 (in) Not a storage device, skipping SCSI inquiry USB description data (for identification) ------------------------- Manufacturer: Huawei Technologies Product: HUAWEI Mobile Serial No.: not provided ------------------------- Looking for active driver . OK, driver found; name unknown, limitation of libusb1 OK, driver "unkown" detached Setting up communication with interface 0 Using endpoint 0x01 for message sending . Trying to send message 1 to endpoint 0x01 . OK, message successfully sent Resetting response endpoint 0x82 Resetting message endpoint 0x01 -> Run lsusb to note any changes. Bye.

It didn’t help. Network manager doesn’t show anything related 3G.

I don’t think it’s usb_modeswitch since 3G stick works great with wvdial on same system. Could it be a bug on modem-manager?
I start only the Network manager on boot, but while Network manager tries to start modem-manager, it throws error continuously in dmesg. Error is the same as in first post.

#4 2012-04-14 17:18:36

Re: [SOLVED]Modem-manager won’t start with Network manager

Ok, lsusb shows the device is detected correctly without manually calling modeswitch. So that part works like it should. I am not sure about the error, maybe someone else.

How did you determine the modem is not available in networkmanager? It is not listed when you

and start to try setup a 3G profile I suppose?

#5 2012-04-14 19:39:16

Re: [SOLVED]Modem-manager won’t start with Network manager

Yes, it’s not listed there. And didn’t work if tried to setup profile.

When I run ‘ip a’ there is not ppp0 device, I remember that on previous installations it have been there.

Edit————
And I think it should not give error message repeatedly, non-stop. That repeats in /var/log/messages.log:

Apr 14 23:08:33 localhost NetworkManager[719]: trying to start the modem manager. Apr 14 23:08:33 localhost dbus[665]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) Apr 14 23:08:33 localhost dbus[665]: [system] Successfully activated service 'org.freedesktop.ModemManager' Apr 14 23:08:33 localhost NetworkManager[719]: modem-manager is now available Apr 14 23:08:33 localhost modem-manager: libhal_ctx_init() failed: (null) Apr 14 23:08:33 localhost NetworkManager[719]: the modem manager disappeared

Last edited by Jompu (2012-04-14 20:13:15)

#6 2012-04-14 20:39:10

Re: [SOLVED]Modem-manager won’t start with Network manager

Okey, now feel embarrassed!

I recognized that I had installed wrong package for modem manager. For some reason I installed network-manager from AUR. I don’t know why there is that version, if I understood right it is old versio of modem manager.

The right version is from extra repositoriy named: modemmanager.

Anyway thanks for your help.

#7 2012-04-15 11:56:58

Re: [SOLVED]Modem-manager won’t start with Network manager

Alrighty & welcome, good you found out. That AUR package is outdated (2009..) indeed, should be flagged out-of-date.

Источник

Thread: Ubuntu 16.04 LTS update problem; can’t reach login screen after reboot

First Cup of Ubuntu

Ubuntu 16.04 LTS update problem; can’t reach login screen after reboot

I’ve been using a dual-boot system with Windows 10 and Ubuntu 14.04, and decided to upgrade Ubuntu to 16.04. After the upgrade process and reboot, I get stuck in a black screen. Pressing CTRL-ALT-F1 brings me to an Ubuntu loading screen, and pressing ESC brings me to the console screen, showing a bunch on information, some of which is shown here:

. [ OK ] Started LSB: Record successful boot for GRUB. [ OK ] Started LSB: automatic crash report generation. [ OK ] Started LSB: daemon to balance interrupts for SMP systems. [FAILED] Failed to start Login Service. See 'systemctl status systemd-logind.service' for details. [FAILED] Failed to start Accounts Service. See 'systemctl status accounts-daemon.service' for details. [FAILED] Failed to start Modem Manager. See 'systemctl status ModemManager.service' for details. [FAILED] Failed to start Thermal Daemon Service. See 'systemctl status thermald.service' for details. [FAILED] Failed to start Bluetooth Service. See 'systemctl status bluetooth.service' for details. [FAILED] Failed to start Avahi mDNS/DNS-SD Stack. See 'systemctl status avahi-daemon.service' for details. [FAILED] Failed to start Network Manager. See 'systemctl status NetworkManager.service' for details. [ *** ] A start job is running for Enable support for additional executable binary formats (49min 50s / no limit)

Then, the console gets stuck on that screen, just updating the time elapsed in the last line, so I can’t enter the ‘systemctl’ commands here. I tried entering them in recovery mode’s root prompt, and it just says that the services are inactive / dead. Is there anything I’ve missed or overlooked?
For reference, here are the specs of my computer:
i7-4790 @ 3.60 GHz
8.00 GB RAM
64-bit
NVIDIA GeForce GTX 745

While I am okay with reformatting the partition and reinstalling Ubuntu, I’d prefer a solution which doesn’t require a reformat.
Thanks in advance.

Источник