A new log; still nothing useful from colord AFAICT, despite the –verbose.

…except that –debug isn’t one of gsd-color’s recognized parameters, and adding it caused GDM to fail to start. I changed it to –verbose which is available.

10.08 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color –help-all
Usage:
gsd-color [OPTION?] color

Help Options:
-h, –help Show help options
–help-all Show all help options
–help-gtk Show GTK+ Options

GTK+ Options
–class=CLASS Program class as used by the window manager
–name=NAME Program name as used by the window manager
–gdk-debug=FLAGS GDK debugging flags to set
–gdk-no-debug=FLAGS GDK debugging flags to unset
–gtk-module=MODULES Load additional GTK+ modules
–g-fatal-warnings Make all warnings fatal
–gtk-debug=FLAGS GTK+ debugging flags to set
–gtk-no-debug=FLAGS GTK+ debugging flags to unset

Application Options:
–exit-time Exit after n seconds time
–dummy-name Name when using the dummy daemon
-v, –verbose Verbose
–display=DISPLAY X display to use

There’s also –gtk-debug and –gdk-debug, but I could do with a little help for what to select for those, as just giving ’all’ seems a little counterproductive (for instance, ”touchscreen” and ”interactive” don’t seem very useful here).

10.03 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color –gtk-debug help
Supported debug values: misc plugsocket text tree updates keybindings multihead modules geometry icontheme printing builder size-request no-css-cache baselines pixel-cache no-pixel-cache interactive touchscreen actions resize layout all help

10.04 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color –gdk-debug help
Supported debug values: events misc dnd xim nograbs input cursor multihead xinerama draw eventloop frames settings opengl all help
Error parsing option –gdk-debug

(Looks like –gdk-debug reports an error with ’help’, despite having just listed it as one of the options.)

Sure, I’ve now set it up thus and will post the results once I hit this again (it seems pretty unpredictable, so could be anything from days to weeks).

Here you go. Had this occur twice in a row just now, so my original theory of the second login never failing was false.

A hint for anyone googling for this: make sure that the value of gcmSenderId in your AndroidManifest.xmlstill has the trailing backslash (\) after you’ve changed the project number to your own. Otherwise the value gets interpreted as int, when it should be a string, which is one way to trigger the issue of devices being assigned empty/null IDs.

(The building instructions do have this documented in bold, but it’s still very easy to miss, I know I did. Complicating the debugging was my Nexus 5X, which kept getting a proper device ID even when all other devices using the same broken build failed to.)

@juliushaertl Is backporting for docs also done as per the manual? It seems pretty straightforward, so I think I can produce those pull requests too, if needed.

Fix indefinite article before Nextcloud (an->a)

Fix typo: ”parameters and are” -> ”parameters are” in Using the occ command.

@skjnldsv The points you raise are about SEO, and (from what I linked to above) I believe those issues are already being worked on. In case I was unclear, I’m not arguing for my idea to supplant the SEO work currently in progress, but to augment it.

Obviously, if #915 gets implemented as requested, my issue becomes moot, but from reading the comments there I understand it’s not so cut and dried that it will be.

As discussed in #915 and #517, Google seems to prefer old versions’ documentation at the expense of newer ones for some reason. The issue was partly mitigated by the fix for #958, which added prominent links to the latest version on top of old pages.

But these links currently point to the manual root. Ideally, I’d like these links to point directly to the latest version of the specific manual page I’m viewing, if available.

For instance, a search for nextcloud occ (for me at least) currently yields the manual page for version 9 as the top result. The ”latest version” link at the top then takes me to the server manual introduction. This means it’s still easier for me to navigate to the latest version of the ”Using the occ command” page by manually replacing the version number in the current URL with ’stable’ (or the latest release number) than to follow the ”latest version” link and try to find the page there.

Producing specific links is probably more laborious than the generic top-level-pointing link. For instance, there may no longer be a corresponding page in the stable version. Detecting such cases should be automatable I think, but there may be other issues that aren’t.

This will be much less of an issue once the SEO issue is resolved, but I think direct links would still remain useful, as people can still come up with search terms that search engines think correspond to old documentation better than the latest.