Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
- To: Adrian Immanuel Kiess <adrian@kiess.onl>
- Cc: 920139@bugs.debian.org
- Subject: Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
- From: Bernhard Übelacker <bernhardu@mailbox.org>
- Date: Mon, 8 Apr 2019 17:25:56 +0200
- Message-id: <[🔎] d22ad17d-b5c8-080e-7336-c7cd9e626bff@mailbox.org>
- Reply-to: Bernhard Übelacker <bernhardu@mailbox.org>, 920139@bugs.debian.org
- In-reply-to: <e352a47d13cbbb1f4e6c4f3e22cd43e42914ec00.camel@kiess.onl>
- References: <154813536918.4967.17853563753218231627.reportbug@g6.lan.dac> <154813536918.4967.17853563753218231627.reportbug@g6.lan.dac> <d6da309e-4414-7412-9dde-6e53d55e4cf6@mailbox.org> <82fef5e9ac279ae28921e5be7b5500f08111351f.camel@kiess.onl> <af74d133-dd95-65f1-1399-f2d1ee99571c@mailbox.org> <680cfdb5092bfeb4d7ea8373a6b0f7b76e883d9f.camel@kiess.onl> <7cea4c66-66c0-5f17-fadc-7f34f7b030ca@mailbox.org> <aae45260328274a31aab2f398c050bef39736651.camel@kiess.onl> <803d8255-1545-f96a-111f-c7cd0c385899@mailbox.org> <e352a47d13cbbb1f4e6c4f3e22cd43e42914ec00.camel@kiess.onl> <154813536918.4967.17853563753218231627.reportbug@g6.lan.dac>
Hello Adrian,
> I don't have any of those old GNOME applications installed, you mentioned.
Then these files should not be there I guess like e.g.:
/usr/share/glib-2.0/schemas/org.gnome.EasyTAG.gschema.xml
On a system where e.g. easytag is installed a 'dpkg -S' returns this:
$ dpkg -S /usr/share/glib-2.0/schemas/org.gnome.EasyTAG.gschema.xml
easytag: /usr/share/glib-2.0/schemas/org.gnome.EasyTAG.gschema.xml
However, if you suspect something of the environment may be wrong,
you could try this:
- login through sddm
env | sort > /home/user/env-enlightment.txt
- login through another login manager
env | sort > /home/user/env-other.txt
- compare:
diff -Nurp /home/user/env-other.txt /home/user/env-enlightment.txt
- then you may search if GSETTINGS_SCHEMA_DIR in the differences shown.
- or set the different variables one by one in a terminal by
export VAR=value
(call from there one of the crashing programs)
and check if that changes behaviour.
Kind regards,
Bernhard
Reply to: