bkbilly / lnxlink

🖥 Effortlessly manage your Linux machine using MQTT.

Home Page:https://bkbilly.gitbook.io/lnxlink

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Segmentation fault

FML128 opened this issue · comments

What type of installation are you running?

Desktop

Which Linux OS are you using?

Arch Linux

Which version of LNXLink has the issue?

2024.2.2

The problem

It cannot start. Even with debug log I cannot see why. The log is attached below.

Logs

[gaming@gamingtv ~]$ lnxlink -c lnxlink.yaml -l DEBUG
INFO:lnxlink:LNXlink 2024.2.2, Python 3.11.8
INFO:lnxlink:Loaded addons: required_restart, update, shutdown, idle, bash, suspend, restart, camera_used, wifi, disk_usage, systemd, notify, network, microphone_used, gpu, cpu, keep_alive, display_env, audio_select, temperature, sys_updates, xdg_open, memory, screen_onoff
INFO:lnxlink:No systemd settings found on configuration.
INFO:lnxlink:MQTT connection: Success
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): api.github.com:443
DEBUG:urllib3.connectionpool:https://api.github.com:443 "GET /repos/bkbilly/lnxlink/releases/latest HTTP/1.1" 200 892
Segmentation fault (core dumped)

I think I've encountered this issue before and it had to do with the idle module.
You could try installing xprintidle package or try adding the idle to the exclude modules list on your lnxlink.yaml config.

I found the issue on the idle module.
It's using the dbus_idle package which I've updated it, so I would recommend updating this to version 2024.3.0.

This should be done automatically on the next release of LNXlink.

Thank you, it was the idle module. However, upgrading version to 2024.3.0 and installing xprintidle did not fix the issue.

No activity on this issue recently. Make sure you update to the latest version of LNXlink to check if the issue has been resolved.
If no further activity occurs, the issue will be closed.

This is still not fixed in 2024.3.0

You should try the new version of LNXlink 2024.4.0.

This seems to be inactive so I am closing it.
The fix was introduced with the new version of dbus_idle.