gnome-control-center (inconsistently) uses right-aligned dim-label
widgets for description labels (for example, in the System Info,
User Accounts and Printer panels)
Use them in the whole System Info panel here as well.
https://bugzilla.gnome.org/show_bug.cgi?id=665059
When calculating the total size of all filesystems, failure to query a
single filesystem results in the iteration being cancelled and a
"Calculating..." message being left on the UI. Instead, just ignore the
filesystem that failed and move on to the next.
https://bugzilla.gnome.org/show_bug.cgi?id=654563
It's possible to have systemd installed, including hostnamed,
but have it not be the init system, in which case it will fail
to auto-start. Handle that case instead of crashing.
https://bugzilla.gnome.org/show_bug.cgi?id=659367
gtk_app_chooser_button_set_show_default_item() was
added so that we could show the default application
for the content-type at the top, and selected, without
hacks.
https://bugzilla.gnome.org/show_bug.cgi?id=658693
"System Up-To-Date" when there's nothing to update,
"Install Updates" when there is something to install,
"Checking for Updates" when, well, doing that.
https://bugzilla.gnome.org/show_bug.cgi?id=657007
default_app_changed() contains a typo: we need to set the https
handler app when the user changes the http app chooser, not the
(non-existent) https app chooser.
This property can be used to name services running on the machine
such as media sharing, device sharing, or externally visible
services such as the Bluetooth name.
We don't set the statis hostname yet though, this will need
to be done to follow the recommendations from systemd.
https://bugzilla.gnome.org/show_bug.cgi?id=650044
In the case where "nomodeset" is given to Linux, or
we don't have a driver, we'll end up in VESA in most cases.
So handle this by parsing the XOrg log, and extract
from it what chipset VESA is driving.
This is again better than lspci because it corresponds
better to what the X server is doing.
For our purposes, the OpenGL renderer string from current
Mesa is about as good as it gets. When we have drivers,
the driver best knows how to handle whatever PCI etc.
devices it found, and it's also tied to the current X server,
which makes the most sense.
If you're wondering why GNOME is in fallback mode, the
lspci output isn't going to help a lot more for a bug report;
for that we need a lot of info from Xorg, kernel, etc. That
would be a separate script.
