Bug#770130: gnome-shell: Oh no! Something has gone wrong. (Fujitsu ST4121)
Simon McVittie
smcv at debian.org
Sat Feb 7 12:24:15 UTC 2015
Control: clone -1 -2
Control: retitle -2 Requiring GSystem, version none: Typelib file for namespace 'GSystem' (any version) not found
Control: severity -2 wishlist
Control: tags -2 = patch
On Sat, 31 Jan 2015 at 12:55:56 -0500, Michael Gilbert wrote:
> > Nov 19 15:59:04 boss gnome-session[3518]: (gnome-shell:3624): Gjs-WARNING **: JS ERROR: Exception in callback for signal: startup-complete: Error: Requiring GSystem, version none: Typelib file for namespace 'GSystem' (any version) not found
>
> This error might also be worth spending some time to troubleshoot.
I believe this is a red herring: I also get that on my fully-working
GNOME 3 system. gnome-shell has an optional runtime dependency
on libgsystem, which is a GNOME library for Unix-specific misc.
It uses it exactly once, to do structured logging to systemd-journald:
if (LoginManager.haveSystemd() &&
sessionMode.currentMode != 'gdm' &&
sessionMode.currentMode != 'initial-setup') {
// Do not import globally to not depend
// on systemd on non-systemd systems.
let GSystem = imports.gi.GSystem;
GSystem.log_structured_print('GNOME Shell started at ' + _startDate,
['MESSAGE_ID=' + GNOMESHELL_STARTED_MESSAGE_ID]);
} else {
log('GNOME Shell started at ' + _startDate);
}
... which is just not worth a dependency IMO.
We don't actually package libgsystem at all, so should probably
stub that out (if (false && ...)) and just take the non-systemd code path...
but we'd have to check with the release team.
S
More information about the pkg-gnome-maintainers
mailing list