SOLVED: Release 1.1.0 doesn't start on Ubuntu LTS. 1.0.0 still works.

[dubigrasu]

Tested all three options (source, Nuitka and pyinstaller) and all fail to start with similar errors.

Source:

Error reading kernel setting /proc/sys/kernel/sched_cfs_bandwidth_slice_us: [Errno 2] No such file or directory: '/proc/sys/kernel/sched_cfs_bandwidth_slice_us'
Error reading kernel setting /proc/sys/kernel/sched_autogroup_enabled: [Errno 2] No such file or directory: '/proc/sys/kernel/sched_autogroup_enabled'
Error reading kernel setting /proc/sys/kernel/watchdog: [Errno 2] No such file or directory: '/proc/sys/kernel/watchdog'
Error reading kernel setting /proc/sys/kernel/nmi_watchdog: [Errno 2] No such file or directory: '/proc/sys/kernel/nmi_watchdog'
Traceback (most recent call last):
File "volt-gui.py", line 799, in
File "volt-gui.py", line 791, in main
File "volt-gui.py", line 159, in init
File "volt-gui.py", line 199, in setup_ui
File "options.py", line 21, in init
File "options.py", line 42, in setup_ui
File "options.py", line 234, in load_options
File "options.py", line 281, in apply_options_values
File "configparser.py", line 1224, in getitem
KeyError: 'LastActiveProfile'
[PYI-10120:ERROR] Failed to execute script 'volt-gui' due to unhandled exception!

Nuitka:

Error reading kernel setting /proc/sys/kernel/sched_cfs_bandwidth_slice_us: [Errno 2] No such file or directory: '/proc/sys/kernel/sched_cfs_bandwidth_slice_us'
Error reading kernel setting /proc/sys/kernel/sched_autogroup_enabled: [Errno 2] No such file or directory: '/proc/sys/kernel/sched_autogroup_enabled'
Error reading kernel setting /proc/sys/kernel/watchdog: [Errno 2] No such file or directory: '/proc/sys/kernel/watchdog'
Error reading kernel setting /proc/sys/kernel/nmi_watchdog: [Errno 2] No such file or directory: '/proc/sys/kernel/nmi_watchdog'
Traceback (most recent call last):
File "/tmp/onefile_10243_1754825444_413932/volt-gui.py", line 799, in
File "/tmp/onefile_10243_1754825444_413932/volt-gui.py", line 791, in main
File "/tmp/onefile_10243_1754825444_413932/volt-gui.py", line 159, in init
File "/tmp/onefile_10243_1754825444_413932/volt-gui.py", line 199, in setup_ui
File "/tmp/onefile_10243_1754825444_413932/options.py", line 21, in init
File "/tmp/onefile_10243_1754825444_413932/options.py", line 42, in setup_ui
File "/tmp/onefile_10243_1754825444_413932/options.py", line 234, in load_options
File "/tmp/onefile_10243_1754825444_413932/options.py", line 281, in apply_options_values
File "/tmp/onefile_10243_1754825444_413932/configparser.py", line 1273, in getitem
KeyError: 'LastActiveProfile'

Pyinstaller:

/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
Error reading kernel setting /proc/sys/kernel/sched_cfs_bandwidth_slice_us: [Errno 2] No such file or directory: '/proc/sys/kernel/sched_cfs_bandwidth_slice_us'
Error reading kernel setting /proc/sys/kernel/sched_autogroup_enabled: [Errno 2] No such file or directory: '/proc/sys/kernel/sched_autogroup_enabled'
Error reading kernel setting /proc/sys/kernel/watchdog: [Errno 2] No such file or directory: '/proc/sys/kernel/watchdog'
Error reading kernel setting /proc/sys/kernel/nmi_watchdog: [Errno 2] No such file or directory: '/proc/sys/kernel/nmi_watchdog'
Traceback (most recent call last):
File "volt-gui.py", line 799, in
File "volt-gui.py", line 791, in main
File "volt-gui.py", line 159, in init
File "volt-gui.py", line 199, in setup_ui
File "options.py", line 21, in init
File "options.py", line 42, in setup_ui
File "options.py", line 234, in load_options
File "options.py", line 281, in apply_options_values
File "configparser.py", line 1273, in getitem
KeyError: 'LastActiveProfile'
[PYI-10339:ERROR] Failed to execute script 'volt-gui' due to unhandled exception!

...................................................................................

Bit of update:
The previous errors were given while using kernel 6.13-4 Liquorix.
With kernel 6.12.41 Xanmod the kernel related errors are gone, yet the application still doesn't start.

Pyinstaller:

/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
Traceback (most recent call last):
File "volt-gui.py", line 799, in
File "volt-gui.py", line 791, in main
File "volt-gui.py", line 159, in init
File "volt-gui.py", line 199, in setup_ui
File "options.py", line 21, in init
File "options.py", line 42, in setup_ui
File "options.py", line 234, in load_options
File "options.py", line 281, in apply_options_values
File "configparser.py", line 1273, in getitem
KeyError: 'LastActiveProfile'
[PYI-5876:ERROR] Failed to execute script 'volt-gui' due to unhandled exception!

The other two versions are missing the "libgvfs*" errors, but the rest of the output is similar.

[pythonlover02]

Alright, the kernel errors are expected and not really an issue. I work with the official kernel documentation, and modified kernels might not expose the same parameters. When that happens, we try to access them and trigger the error.

I plan to add a small patch so that instead of showing an error, it will print something like:

/proc/sys/kernel/sched_cfs_bandwidth_slice_us doesn't exist, skipping 

It also won’t appear in the GUI, which will avoid confusion and log spam. This way, future versions can work well with modified kernels. Something to add its that other than log spam the kernel errors don't stop the program from opening

The actual issue here is the KeyError: 'LastActiveProfile', which is probably caused by me changing the way config files are handled again, without providing a fallback for that setting.

Could you see if the commit i just added to the next branch fixes it?
Or this pyinstaller build that i made, be shure to mark it as executable.

[dubigrasu]

Yes, the next branch fixes it. The one from google drive as well. There are no errors displayed and the app is working fine.
Many thanks!

[pythonlover02]

Alright, a 1.1.1 version will be released later with some fixes. Thanks for reporting the issue :).