-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to call method: org.freedesktop.ScreenSaver.GetActive #9
Comments
I tested the rpg maker mv/mz games in lmde 6 using Virtual box and the games worked fine for me. Here's for example a toga game from itch.io. |
I've gotten this error message running some games, but it never kills the program; simply hangs it for a moment and then continues. |
Alright, thank you. That said, I think it would be a nice improvement if the program could just ignore it when the screensaver DBUS is unresponsive. |
This is an nwjs bug, you should probably write a report here. Specifying: System, Version of nwjs, your display server protocol: wayland or xorg and the log of this error. I also have some errors with dbus, but the games are running successfully. You can also post your report with the system config. |
using linux mint debian, every game fails with seemingly the same error:
[9888:9888:0628/111510.197357:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented
after that it just gets stuck on a blank screen.
I looked around a bit, and this seems to be a common bug in many programs in many distros.
which happens when a program is trying to interface with the screensaver via dbus to see if the screen is available or not.
for example here:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/632
the script then hangs if the reply is
this method is not implemented
instead of the expected replies of true/false?system config:
https://termbin.com/wlso
The text was updated successfully, but these errors were encountered: