FS#73403 - [modem-manager-gui] doesnt start

Attached to Project: Community Packages
Opened by antonmaier (x3oo) - Tuesday, 18 January 2022, 08:02 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Balló György (City-busz)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:

[buttermelted@thinkpad ~]$ sudo modem-manager-gui
[sudo] password for buttermelted:
Connection manager: Network Manager >= 0.9.0
Modem manager: Modem Manager >= 0.7.0

(modem-manager-gui:5037): libnotify-WARNING **: 09:00:55.159: Failed to connect to proxy

(modem-manager-gui:5037): GLib-CRITICAL **: 09:00:55.159: g_strrstr: assertion 'haystack != NULL' failed

(modem-manager-gui:5037): GLib-CRITICAL **: 09:00:55.274: g_variant_lookup_value: assertion 'g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{s*}")) || g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{o*}"))' failed

(modem-manager-gui:5037): GLib-CRITICAL **: 09:00:55.274: g_variant_lookup_value: assertion 'g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{s*}")) || g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{o*}"))' failed

(modem-manager-gui:5037): GLib-CRITICAL **: 09:00:55.274: g_variant_lookup_value: assertion 'g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{s*}")) || g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{o*}"))' failed

(modem-manager-gui:5037): GLib-CRITICAL **: 09:00:55.274: g_variant_lookup_value: assertion 'g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{s*}")) || g_variant_is_of_type (dictionary, G_VARIANT_TYPE ("a{o*}"))' failed

(modem-manager-gui:5037): GLib-CRITICAL **: 09:00:55.274: g_variant_unref: assertion 'value != NULL' failed
Segmentation fault at address: 0x20
Stack trace:
1. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7f17313ecad0]
2. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7f17313ecad0]
3. /usr/lib/libglib-2.0.so.0(g_variant_n_children+0x1e) [0x7f17314689ee]
4. /usr/lib/modem-manager-gui/modules/libmodcm_nm09.so(mmgui_module_connection_enum+0x4a2) [0x7f172c11d792]
5. modem-manager-gui(mmguicore_connections_enum+0x6f) [0x561aa19e5d9f]
6. modem-manager-gui(+0x4942a) [0x561aa1a0642a]
7. modem-manager-gui(mmguicore_devices_open+0x1c5) [0x561aa19e6395]
8. modem-manager-gui(+0x3af15) [0x561aa19f7f15]
9. modem-manager-gui(+0x4902b) [0x561aa1a0602b]
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:03 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/modem-manager-gui/issu es/1
Comment by Antoni Przybylik (ANTONI) - Wednesday, 23 March 2022, 18:12 GMT
I also have this bug.
Comment by David Wen Riccardi-Zhu (dwrz) - Friday, 01 April 2022, 02:18 GMT
I have the same issue:

Connection manager: Network Manager >= 0.9.0
Modem manager: Modem Manager >= 0.7.0

(modem-manager-gui:3635608): GLib-CRITICAL **: 02:18:40.726: g_strrstr: assertion 'haystack != NULL' failed
Segmentation fault at address: 0x20
Stack trace:
1. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7f509306faa0]
2. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7f509306faa0]
3. /usr/lib/libglib-2.0.so.0(g_variant_n_children+0x1e) [0x7f50930eb8fe]
4. /usr/lib/modem-manager-gui/modules/libmodcm_nm09.so(mmgui_module_connection_enum+0x4a2) [0x7f508d1e3792]
5. modem-manager-gui(mmguicore_connections_enum+0x6f) [0x55b746b7dd9f]
6. modem-manager-gui(+0x4942a) [0x55b746b9e42a]
7. modem-manager-gui(mmguicore_devices_open+0x1c5) [0x55b746b7e395]
8. modem-manager-gui(+0x3af15) [0x55b746b8ff15]
9. modem-manager-gui(+0x4902b) [0x55b746b9e02b]
Comment by Cluxter (cluxter) - Wednesday, 06 April 2022, 12:19 GMT
Same bug here and I had something similar 3 years ago. See this thread, maybe it can help a little bit: https://bbs.archlinux.org/viewtopic.php?id=243601
Comment by Sergey Kvachonok (ravenexp) - Tuesday, 02 August 2022, 16:20 GMT
I also have this issue.
Comment by Sergey Kvachonok (ravenexp) - Saturday, 27 August 2022, 13:57 GMT
There appears to be a patch floating around: https://groups.google.com/g/linux.debian.bugs.dist/c/mOT838CtS3o/m/bpLky9BcAgAJ

Can someone test it? I don't have access to my 3G modem hardware right now...
Comment by Chih-Hsuan Yen (yan12125) - Thursday, 24 August 2023, 17:10 GMT
Someone submitted an AUR package with that patch, so I assume it's tested: https://aur.archlinux.org/packages/modem-manager-gui-hg
Comment by Ted Brandon (tbdo) - Monday, 28 August 2023, 10:10 GMT
Has anyone found a working workaround ?
(The patched AUR package has the same error, on my machine at least)
Comment by mattia (nTia89) - Friday, 15 September 2023, 18:26 GMT
I cannot reproduce the issue: `modem-manager-gui` starts normally from terminal, as well.
Is it still valid for you?
Comment by David Wen Riccardi-Zhu (dwrz) - Saturday, 16 September 2023, 00:06 GMT
Yes, unfortunately. I've been using mmcli and nm-applet as a workaround.

$ modem-manager-gui
Connection manager: Network Manager >= 0.9.0
Modem manager: Modem Manager >= 0.7.0

(modem-manager-gui:523803): GLib-CRITICAL **: 00:05:44.310: g_strrstr: assertion 'haystack != NULL' failed
Segmentation fault at address: 0x30
Stack trace:
1. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7f6ebd33cdb0]
2. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7f6ebd33cdb0]
3. /usr/lib/libglib-2.0.so.0(g_variant_n_children+0x1c) [0x7f6ebd3c207c]
4. /usr/lib/modem-manager-gui/modules/libmodcm_nm09.so(mmgui_module_connection_enum+0x4a2) [0x7f6eb8dfb792]
5. modem-manager-gui(mmguicore_connections_enum+0x6f) [0x55a9fd2a5d9f]
6. modem-manager-gui(+0x4942a) [0x55a9fd2c642a]
7. modem-manager-gui(mmguicore_devices_open+0x1c5) [0x55a9fd2a6395]
8. modem-manager-gui(+0x3af15) [0x55a9fd2b7f15]
9. modem-manager-gui(+0x4902b) [0x55a9fd2c602b]
Comment by mattia (nTia89) - Saturday, 16 September 2023, 04:38 GMT
Two ideas:
- this version of modem-manager-gui cannot be back-ward compatible with old libraries; is your system up-to-date?
- old .config files can make troubles; can you try from a blank $HOME (just create a new user and login from that)?
Comment by David Wen Riccardi-Zhu (dwrz) - Saturday, 16 September 2023, 23:58 GMT
Thank you! I updated my system and ran with HOME=/var/empty -- I know it's not quite the same as a new user, but this is the output:

$ env HOME=/var/empty modem-manager-gui
Connection manager: Network Manager >= 0.9.0
Modem manager: Modem Manager >= 0.7.0

(modem-manager-gui:582867): GLib-CRITICAL **: 23:56:08.069: g_strrstr: assertion 'haystack != NULL' failed

** (modem-manager-gui:582867): WARNING **: 23:56:08.111: Failed to make XDG data directory: /var/empty/.local/share/modem-manager-gui/devices/3dbb5ac38aa6f2d86b9ae9375f775a19

** (modem-manager-gui:582867): WARNING **: 23:56:08.111: Failed to make XDG data directory: /var/empty/.local/share/modem-manager-gui/devices/3dbb5ac38aa6f2d86b9ae9375f775a19

** (modem-manager-gui:582867): WARNING **: 23:56:08.114: Cant create modem settings directory
Segmentation fault at address: 0x30
Stack trace:
1. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7fe09dcd5e10]
2. /usr/lib/libglib-2.0.so.0(g_bit_lock+0x50) [0x7fe09dcd5e10]
3. /usr/lib/libglib-2.0.so.0(g_variant_n_children+0x1c) [0x7fe09dd596ac]
4. /usr/lib/modem-manager-gui/modules/libmodcm_nm09.so(mmgui_module_connection_enum+0x4a2) [0x7fe09ba2d792]
5. modem-manager-gui(mmguicore_connections_enum+0x6f) [0x55da0d4d1d9f]
6. modem-manager-gui(+0x4942a) [0x55da0d4f242a]
7. modem-manager-gui(mmguicore_devices_open+0x1c5) [0x55da0d4d2395]
8. modem-manager-gui(+0x3af15) [0x55da0d4e3f15]
9. modem-manager-gui(+0x4902b) [0x55da0d4f202b]

This makes me think the issue isn't with either home or outdated libraries.
Comment by Bjoern Franke (bjo) - Friday, 06 October 2023, 18:18 GMT
The hg-version from AUR works, so it's fixed upstream?

Loading...