Modem-manager-gui segmentation fault

Hi. The program "modem-manager-gui" fails with segmentation fault after clicking "Let's start". Doesn't matter what I choose or if my mobile modem is plugged in or not. This is from starting it from the shell:

modem-manager-gui
Connection manager: Network Manager >= 0.9.0
Modem manager: Modem Manager >= 0.7.0
Segmentation fault at address: 0x56271b815e0c
Stack trace:
1. /usr/lib/libc.so.6(+0x1590ab) [0x7f54d94670ab]
2. /usr/lib/libc.so.6(+0x1590ab) [0x7f54d94670ab]
3. /usr/lib/libglib-2.0.so.0(g_str_equal+0xe) [0x7f54da20158e]
4. modem-manager-gui(mmgui_notifications_new+0x227) [0x5622780c8967]
5. modem-manager-gui(+0x48f81) [0x5622780f9f81]
6. modem-manager-gui(mmgui_svcmanager_start_services_activation+0x14d) [0x5622780d661d]
7. modem-manager-gui(mmguicore_start+0x11b) [0x5622780dc0eb]
8. modem-manager-gui(mmgui_welcome_window_button_clicked_signal+0x182) [0x5622780ef062]
9. /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x1209) [0x7f54da04abc9]

λ sudo garuda-inxi:

System:
Kernel: 6.3.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f98349e3-8520-4d18-968f-b7d3b3f4b259 rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=f38c84c4-3b3e-4abc-afd9-6f44ced56afd loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK (MS-7C91) v: 2.0
serial: <filter> UEFI: American Megatrends LLC. v: A.A0 date: 05/26/2022
CPU:
Info: model: AMD Ryzen 5 5600G with Radeon Graphics socket: AM4 bits: 64
type: MT MCP arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000D
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 3900 min/max: 1400/4464 boost: enabled
base/boost: 3900/4450 scaling: driver: acpi-cpufreq governor: performance
volts: 1.4 V ext-clock: 100 MHz cores: 1: 3900 2: 3900 3: 3900 4: 3900
5: 3900 6: 3900 7: 3900 8: 3900 9: 3900 10: 3900 11: 3900 12: 3900
bogomips: 93420
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1,DP-2 bus-ID: 30:00.0
chip-ID: 1002:1638 class-ID: 0300 temp: 35.0 C
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: Philips PHL 273V5
serial: <filter> built: 2016 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.2 renderer: AMD Radeon Graphics (renoir LLVM
15.0.7 DRM 3.52 6.3.8-zen1-1-zen) direct-render: Yes
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s bus-ID: 30:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 30:00.6 chip-ID: 1022:15e3
class-ID: 0403
API: ALSA v: k6.3.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.71 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: e000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: d000 bus-ID: 2a:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp42s0 state: down mac: <filter>
Device-3: Qualcomm Atheros AR9271 802.11n driver: ath9k_htc type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1:10
chip-ID: 0cf3:9271 class-ID: ff00 serial: <filter>
IF: wlp48s0f3u1 state: up mac: <filter>
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1
bus-ID: 1-2.2.3:9 chip-ID: 0a12:0001 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 8.31 TiB used: 7.21 TiB (86.8%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 1B4QFXO7 temp: 37.9 C
scheme: GPT
SMART: yes health: PASSED on: 50 hrs cycles: 271
read-units: 15,756,442 [8.06 TB] written-units: 3,407,387 [1.74 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Kingchuxing model: 128GB
size: 119.24 GiB block-size: physical: 512 B logical: 512 B sata: 3.2
speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: A25E temp: 40 C
scheme: GPT
SMART: yes state: enabled health: PASSED on: 164d 8h cycles: 157
read: 24.4 MiB written: 38.1 MiB
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD50NDZW-11BCSS0 family: Elements / My Passport (USB, AF)
size: 4.55 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 sata: 3.1 speed: 6.0 Gb/s
tech: HDD rpm: 4800 serial: <filter> fw-rev: 1034 drive-rev: 01.01A01
temp: 47 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 39d 5h cycles: 13
ID-4: /dev/sdc maj-min: 8:32 model: MXT-USB Storage Device size: 7.5 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1501 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-5: /dev/sdd maj-min: 8:48 vendor: Seagate model: Expansion Desk
size: 2.73 TiB block-size: physical: 4096 B logical: 4096 B type: USB
rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 0737
SMART Message: A mandatory SMART command failed. Various possible causes.
Partition:
ID-1: / raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 101.2 GiB (97.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 101.2 GiB (97.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-4: /var/log raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 101.2 GiB (97.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-5: /var/tmp raw-size: 104.05 GiB size: 104.05 GiB (100.00%)
used: 101.2 GiB (97.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 13.54 GiB used: 942.8 MiB (6.8%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 14.9 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 43.9 C mobo: N/A gpu: amdgpu temp: 36.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 417 Uptime: 14h 21m wakeups: 0 Memory: available: 13.54 GiB
used: 5.22 GiB (38.6%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 13.1.1 clang: 15.0.7 Packages: pm: guix-sys
pkgs: 0 pm: guix-usr pkgs: 0 pm: nix-default pkgs: 0 pm: nix-sys pkgs: 0
pm: nix-usr pkgs: 0 pm: pacman pkgs: 2567 libs: 565 tools: octopi,paru,yay
pm: flatpak pkgs: 0 Shell: garuda-inxi (sudo) default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.27
Garuda (2.6.16-1):
System install date:     2022-10-03
Last full system update: 2023-06-21 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       No/Undetected
Failed units:

Hi there, welcome to the forum.

This is probably unrelated, but please reboot…

1 Like

Why do I need to reboot after upgrades? This isn't Windows. I sometimes only reboot every few months.
Edit: That said, since I do have a problem, this is another situation. So I will do it as soon as I don't need the system.

Yes, correct, but you use KDE :slight_smile: and

Most of the time only less things, like new kernel need reboot, but KDE is special, you newer knew. Like KDE said, its not a bug, its a feature :wink:

If you change something in KDE and it doesn’t work, the first thing you should do is reboot.

1 Like

The reboot topic has been resolved, since I had a loss of power at home and no battery.

If you change something in KDE and it doesn’t work, the first thing you should do is reboot.

I’ll keep it in mind, but I also hate it. My ideal is never needing to reboot, but also having everything in regards to open windows coming back as it was after doing it, and the second part works more or less.

Oh, and it didn’t work. Reboot doesn’t change anything.

Me too, update and reboot need often very long time in M$, but in arch max. 5 min. and reboot 10 sec… So, no problem for me and I do not use KDE often :smiley: , just use i3wm :slight_smile:

There are a feature in KDE for that, it open with last “workspaces” (virt. desktops) and apps. You must activate in settings and save before reboot, something like “leave” in the window if you click the mod/super key. Just whoogle for a manual, I am not fit in KDE :smiley:

You must activate in settings and save before reboot

Yeah, I have that. It’s how it should be. Not perfect yet but this is they way.

Anyways, the modem-manager just works for everyone else here?

Yes.

Hmm. I forgot to mention that I also made pacman -Dk and everything is fine. Well.

pacman -Qikk modem-manager-gui
Name            : modem-manager-gui
Version         : 0.0.20-2
Description     : Frontend for ModemManager daemon able to control specific modem functions
Architecture    : x86_64
URL             : https://linuxonly.ru/page/modem-manager-gui
Licenses        : GPL3
Groups          : None
Provides        : None
Depends On      : gdbm  gtk3  gtkspell3  libnotify  modemmanager
Optional Deps   : networkmanager: monitor network traffic [installed]
Required By     : None
Optional For    : networkmanager-support
Conflicts With  : None
Replaces        : None
Installed Size  : 6.14 MiB
Packager        : Jelle van der Waa <[email protected]>
Build Date      : Sun 18 Jul 2021 20:46:14 WEST
Install Date    : Fri 09 Sep 2022 15:36:24 WEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

modem-manager-gui: 487 total files, 0 altered files
  • I also installed "amd-ucode-git" but it didn't help.
  • Reinstalling gdbm gtk3 gtkspell3 libnotify modemmanager also doesn't solve it.
  • I will try to add the mobile connection through the regular KDE network manager. Didn't know this works, I just looked into some tutorial and found this modem-manager. Anyways, my SIM is back in my tablet for now. I will try again but I'll try to work around the problem by using the other way to do it.

have you seen this post:

1 Like

No, but now I looked into it. The same files don't exist on my system, though. I looked around and didn't find them yet. They might only exist if the program ran before and stopped working.

I think this is just a case of unmaintained project. As you can see this project was last updated a year ago. A lot of time for things to change and libraries to drop/depreciate functionalities.

Also the project’s website is down for undefined period further solidifying my belief.

https://linuxonly.ru/page/modem-manager-gui

3 Likes

Thanks, I think you're right. Not sure if I should flag this as resolved, but I won't look further into it.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.