command to change profile not working show a critical error #2

Closed
opened 2021-09-28 13:03:28 -03:00 by Sourabh101 · 18 comments

when i execute the command
shows this

** (tuf-cli:2668): CRITICAL **: 21:32:30.493: tuf_manager_tuf_server_interface_get_server_version: assertion 'self != NULL' failed

** (tuf-cli:2668): WARNING **: 21:32:30.493: cli.vala:331: Invalid arguments!
Usage: tuf-cli COMMAND [SUBCOMMAND] ...

also gui doesn't not working as well

when i execute the command shows this ** (tuf-cli:2668): CRITICAL **: 21:32:30.493: tuf_manager_tuf_server_interface_get_server_version: assertion 'self != NULL' failed ** (tuf-cli:2668): WARNING **: 21:32:30.493: cli.vala:331: Invalid arguments! Usage: tuf-cli COMMAND [SUBCOMMAND] ... also gui doesn't not working as well
Owner

Some more info would be helpful. You didn't actually write the command you are trying to use in your message... I am sorry but I can't read your mind.

Other important info I need:

  • Distro/version
  • Vala version
  • Laptop model
Some more info would be helpful. You didn't actually write the command you are trying to use in your message... I am sorry but I can't read your mind. Other important info I need: * Distro/version * Vala version * Laptop model
Author

Distro : Arch
Vala Version : 0.54.1
Laptop : tuf fx505dy

I can use the fn+fan key also the "tray" shows it changed I can confirm it changes shows differnt value in lm_sensors but I can't change it through "gui and cli" whenever I try to execute the cammand it shows this

$ tuf-cli silent

** (tuf-cli:4595): WARNING **: 21:58:42.935: common.vala:41: Error calling StartServiceByName for org.tuf.manager.server: Unit tufmanager.service not found.

** (tuf-cli:4595): CRITICAL **: 21:58:42.935: tuf_manager_tuf_server_interface_get_server_version: assertion 'self != NULL' failed

** (tuf-cli:4595): WARNING **: 21:58:42.935: cli.vala:331: Invalid arguments!
Usage: tuf-cli COMMAND [SUBCOMMAND] ...

version Print the version of tuf-cli
help Show this help screen
fan [balanced, turbo, silent] Set the fan mode
lighting [static, breath, cycle, stobe] Set the keyboard lighting
speed [slow, medium, fast] Set the keyboard lighting speed
color ["#XXXXXX"] Set the keyboard color
restore Restore saved settings

info Show the current config

Examples:
Silence fan: tuf-cli fan silent
Change RGB color: tuf-cli color "#FF0000"

Distro : Arch Vala Version : 0.54.1 Laptop : tuf fx505dy I can use the fn+fan key also the "tray" shows it changed I can confirm it changes shows differnt value in lm_sensors but I can't change it through "gui and cli" whenever I try to execute the cammand it shows this $ tuf-cli silent ** (tuf-cli:4595): WARNING **: 21:58:42.935: common.vala:41: Error calling StartServiceByName for org.tuf.manager.server: Unit tufmanager.service not found. ** (tuf-cli:4595): CRITICAL **: 21:58:42.935: tuf_manager_tuf_server_interface_get_server_version: assertion 'self != NULL' failed ** (tuf-cli:4595): WARNING **: 21:58:42.935: cli.vala:331: Invalid arguments! Usage: tuf-cli COMMAND [SUBCOMMAND] ... version Print the version of tuf-cli help Show this help screen fan [balanced, turbo, silent] Set the fan mode lighting [static, breath, cycle, stobe] Set the keyboard lighting speed [slow, medium, fast] Set the keyboard lighting speed color ["#XXXXXX"] Set the keyboard color restore Restore saved settings info Show the current config Examples: Silence fan: tuf-cli fan silent Change RGB color: tuf-cli color "#FF0000"
Owner

Thanks, I can see 2 problems.

First of all you are incorrecly typing the command it is:
tuf-cli fan silent
NOT
tuf-cli silient

Second, it looks like the tuf server isn't running in the background. I assume that since you are using Arch Linux you have systemd. If that is the case it should have installed the unit into /usr/lib/systemd/system/tufmanager.service. Can you verify if that file exists?

How did you build tuf-manager and with which arguments?

Thanks, I can see 2 problems. First of all you are incorrecly typing the command it is: tuf-cli fan silent NOT tuf-cli silient Second, it looks like the tuf server isn't running in the background. I assume that since you are using Arch Linux you have systemd. If that is the case it should have installed the unit into /usr/lib/systemd/system/tufmanager.service. Can you verify if that file exists? How did you build tuf-manager and with which arguments?
Author

the systemd file named tuf-manager.service doesn't exist
I build it I first used aur then i built it myself I used meson build command while it was building I'm certain I saw a NO for systemd
then installed through Ninja but same results as aur

the systemd file named tuf-manager.service doesn't exist I build it I first used aur then i built it myself I used meson build command while it was building I'm certain I saw a NO for systemd then installed through Ninja but same results as aur
Owner

Alright found the problem. It is Arch Linux specific. Should be fixed with this commit: eabd5aaf19

With that commit it should now install the systemd service file. Please confirm if it works, if it does I will push a new version of tuf-manager.

Alright found the problem. It is Arch Linux specific. Should be fixed with this commit: eabd5aaf197ca2baf4ff88744dec19b1ab6fd56d With that commit it should now install the systemd service file. Please confirm if it works, if it does I will push a new version of tuf-manager.
Author

$tuf-cli silent

** (tuf-cli:1355): CRITICAL **: 22:52:51.553: file ../src/common.vala: line 38: unexpected error: Error calling StartServiceByName for org.tuf.manager.server: Failed to activate service 'org.tuf.manager.server': timed out (service_start_timeout=25000ms) (g-dbus-error-quark, 20)

(tuf-cli:1355): GLib-GObject-WARNING **: 22:52:51.553: invalid (NULL) pointer instance

(tuf-cli:1355): GLib-GObject-CRITICAL **: 22:52:51.553: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

** (tuf-cli:1355): CRITICAL **: 22:52:51.553: tuf_manager_tuf_server_interface_set_fan_mode: assertion 'self != NULL' failed

stucked here

$tuf-cli silent ** (tuf-cli:1355): CRITICAL **: 22:52:51.553: file ../src/common.vala: line 38: unexpected error: Error calling StartServiceByName for org.tuf.manager.server: Failed to activate service 'org.tuf.manager.server': timed out (service_start_timeout=25000ms) (g-dbus-error-quark, 20) (tuf-cli:1355): GLib-GObject-WARNING **: 22:52:51.553: invalid (NULL) pointer instance (tuf-cli:1355): GLib-GObject-CRITICAL **: 22:52:51.553: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed ** (tuf-cli:1355): CRITICAL **: 22:52:51.553: tuf_manager_tuf_server_interface_set_fan_mode: assertion 'self != NULL' failed stucked here
Owner

Did you enable/start the systemd service?

Did you enable/start the systemd service?
Author

Enabled it still it persists

** (tuf-cli:1528): CRITICAL **: 23:07:00.229: file ../src/common.vala: line 38: unexpected error: Error calling StartServiceByName for org.tuf.manager.server: Failed to activate service 'org.tuf.manager.server': timed out (service_start_timeout=25000ms) (g-dbus-error-quark, 20)

(tuf-cli:1528): GLib-GObject-WARNING **: 23:07:00.229: invalid (NULL) pointer instance

(tuf-cli:1528): GLib-GObject-CRITICAL **: 23:07:00.229: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

** (tuf-cli:1528): CRITICAL **: 23:07:00.229: tuf_manager_tuf_server_interface_set_fan_mode: assertion 'self != NULL' failed

Enabled it still it persists ** (tuf-cli:1528): CRITICAL **: 23:07:00.229: file ../src/common.vala: line 38: unexpected error: Error calling StartServiceByName for org.tuf.manager.server: Failed to activate service 'org.tuf.manager.server': timed out (service_start_timeout=25000ms) (g-dbus-error-quark, 20) (tuf-cli:1528): GLib-GObject-WARNING **: 23:07:00.229: invalid (NULL) pointer instance (tuf-cli:1528): GLib-GObject-CRITICAL **: 23:07:00.229: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed ** (tuf-cli:1528): CRITICAL **: 23:07:00.229: tuf_manager_tuf_server_interface_set_fan_mode: assertion 'self != NULL' failed
Author

systemd shows it active and runing for some reason it just showing same error
also it doesn't so tray notifications now

systemd shows it active and runing for some reason it just showing same error also it doesn't so tray notifications now
Owner

What is the output of this:

echo $DBUS_SESSION_BUS_ADDRESS
What is the output of this: ``` echo $DBUS_SESSION_BUS_ADDRESS ```
Author

output is
unix:path=/run/user/1000/bus

output is unix:path=/run/user/1000/bus
Owner

And this:

ps aux | grep tuf-server
And this: ``` ps aux | grep tuf-server ```
Author

And this:

ps aux | grep tuf-server

root 456 0.0 0.0 245924 4052 ? Ssl 23:04 0:00 /usr/local/libexec/tuf-manager/tuf-server
sourabh 5665 0.0 0.0 6496 2544 pts/2 S+ 23:24 0:00 grep tuf-server

> And this: > ``` > ps aux | grep tuf-server > ``` root 456 0.0 0.0 245924 4052 ? Ssl 23:04 0:00 /usr/local/libexec/tuf-manager/tuf-server sourabh 5665 0.0 0.0 6496 2544 pts/2 S+ 23:24 0:00 grep tuf-server
Owner

Alright, so dbus is working. The service is up and running. However dbus can't connect the the server even though it is running...

Alright, so dbus is working. The service is up and running. However dbus can't connect the the server even though it is running...
Owner

I notice that you have intsalled it into the /usr/local prefix. Could you reinstall using /usr as your prefix?

I notice that you have intsalled it into the /usr/local prefix. Could you reinstall using /usr as your prefix?
Author

Can you specify it please ?

Can you specify it please ?
Owner

I do see another issue, you didn't set your libexec dir to /usr/lib, in Arch Linux the libexec dir is /usr/lib instead of /usr/libexec.

This should give you a correct build for Arch Linux:
meson --prefix=/usr --libexecdir=/usr/lib

I do see another issue, you didn't set your libexec dir to /usr/lib, in Arch Linux the libexec dir is /usr/lib instead of /usr/libexec. This should give you a correct build for Arch Linux: meson --prefix=/usr --libexecdir=/usr/lib
Author

thank you very much It worked perfectly Please post this fix on aur as well would be easy to manage packages
Love from India!!
peace

thank you very much It worked perfectly Please post this fix on aur as well would be easy to manage packages Love from India!! peace
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cromer/tuf-manager#2
No description provided.