![]() Otherwise, if it is some background failure, then look at the daemons. If you are having problems while adding an account or updating the credentials, then the gnome-control-center logs are the most relevant. Check your operating system's logging facilities (eg., journalctl) to find them. Run-time failures are always logged as WARNINGs and unexpected programming errors are logged as CRITICALs. It will make gnome-control-center, goa-daemon and goa-identity-service show some extra debug messages. $ /path/to/prefix/libexec/goa-daemon -replace &Įnsure that the G_MESSAGES_DEBUG environment variable is defined, and restart the daemons if needed (see above). In that case, you can restart the daemons manually: $ /path/to/prefix/libexec/goa-identity-service & On development systems the D-Bus session daemon might not know about the prefix in which you have installed gnome-online-accounts. The easiest way to restart goa-daemon and goa-identity-service is to restart the GNOME session by logging out and then logging back in. They should always have the same version or be artifacts of the same build. Strictly speaking, daemons from different builds or versions should not be run together. goa-daemon offers the application-facing interfaces, while goa-identity-service is a private daemon used by gnome-online-accounts itself to handle Kerberos credentials. GNOME Online Accounts contains a D-Bus service and comes with two D-Bus daemons - goa-daemon and goa-identity-service. Integration with GtkFileChooser and Nautilus.Empty dialog when adding an account in Settings.use the official (albeit tricky) manner of logging: GNOME on debugging. Or log a specific process that is a part of GNOME like journalctl /usr/bin/gnome-session -f -o cat, just beware that some distros and versions log to different files and old GNOME versions often log to whatever your display manager logs to. This is nice and works on all distros implementing systemd You will see some warnings no matter what, but most mention what extension they're from. use the log() function and follow journalctl in a commandline, check either GNOME or JS, use journalctl -f | grep -i js (or use grep -i gnome). Generally Debugging gnome can be done in several ways. I recommend checking the official extensions website and go through whatever interesting extensions' source code you can get, as that is your best bet to learn anything. More recent reference made by a user, although this is quite extensive, it's not of much use if you're on an older version of GNOME Shell, as deprecated and old is more likely to work than next gen stuff.You could try to clone the git repo to run it locally, but the readme.md is a verbatim copy of what they forked. Generated docs, almost everything is there, very extensive, but sometimes the site drops offline for a few days.Old, but mostly useful documentation, MathematicalCoffee has more useful things, like in depth explained code that is quite a solid learning source.Up to date generated docs at RooJS, although at least events are off as they are separated with - (minus) rather than _ (underscore).Unofficial sources aren't always up to date, however. They have some outdated tutorials for GNOME Shell 3.4 with a small difference explanation to 3.6, a few pages on the C(++) ends of the libraries you use (most of the functions, variables and constants use the same names though), but for any real info you'd need experience, digging through other GNOME and shell extension code or some unofficial sources. The reason you get r(.) = undefined is because log(String) does not return anything, thus the result is undefined.Ģ: Either log throughout init() and enable(), then check where it breaks and try to pinpoint the breaking line using log or commenting out lines of code (although the culprit is probably defined in the general logging, described in the section at the bottom).ģ: There is no official documentation. It allows you to execute and test lines of GJS, grab and manipulate objects and use r(.) to use results in following commands. 1: LookingGlass is basically a GJS console.
0 Comments
Leave a Reply. |