Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Hello Bernhard, when removing GSETTINGS_SCHEMA_DIR="/usr/share/glib-2.0/schemas/" from /etc/environment the system still bails out that No GSettings schemas are found. Here the error message: May 23 08:22:14 g6 at-spi-bus-launcher[16154]: dbus-daemon[16158]: Successfully activated service 'org.a11y.atspi.Registry ' May 23 08:22:14 g6 at-spi-bus-launcher[16154]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registr y May 23 08:22:14 g6 gnome-session[16073]: gnome-session-binary[16073]: GLib-GIO-ERROR: No GSettings schemas are installed $ n the system May 23 08:22:14 g6 gnome-session[16073]: aborting... May 23 08:22:14 g6 gnome-session-binary[16073]: GLib-GIO-ERROR: No GSettings schemas are installed on the system#012abort$ ng... May 23 08:22:14 g6 kernel: [199581.568915] do_trap: 166 callbacks suppressed May 23 08:22:14 g6 kernel: [199581.568918] traps: gnome-session- b[16073] trap int3 ip:7f6a30f3bca5 sp:7ffd095ea9d0 error:$ in libglib-2.0.so.0.5800.3[7f6a30f03000+7e000] May 23 08:22:15 g6 at-spi-bus-launcher[16154]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0$ May 23 08:22:15 g6 at-spi-bus-launcher[16154]: after 21 requests (21 known processed) with 0 events remaining. apt-show-versions | grep No returns roughly a hundred packages but no Gnome 3 related packages. Shall I try to remove all of these? I fixed the error setting export XDG_DATA_DIRS=/usr/share/gnome:/usr/local/share/:/usr/share/ in /etc/environment. Finally it works again! I can log in from xdm to gnome-session. All Gnome 3 applications seem to work fine again. Maybe someone can forward this to the package maintainer who can fix the issue. Thank you very much for your help! Sincerely, Adrian -- With many greetings from Leipzig, Germany. Adrian Immanuel Kieß Gothaer Straße 34 D-04155 Leipzig Administrator & programmer Unix ∧ Perl ∧ Java ∧ LaTeX 📪 — < adr...@kiess.onl > 🌍 — https://www.kiess.onl ☕ — https://arosusi.kiess.onl 🐇 — https://jexercise.kiess.onl --SYSTEM-- echo "Your fortune cookie: " && /usr/games/fortune -c -s > (fortunes) % Don't kiss an elephant on the lips today. echo "KIESS.ONL uptime: " && /usr/bin/uptime > 08:24:42 up 4 days, 3:31, 10 users, load average: 2.04, 2.24, 2.26 On Sat, 2019-04-27 at 09:59 +0200, Bernhard Übelacker wrote: > Hello Adrian, > so unfortunately it has still no clear error. > > In your .xsession-errors is tcosmonitor mentioned. > As this package got 2016 removed [1] from debian - do you > have still installed tcosmonitor or tcosmonitor-common? > > If yes, maybe that might cause some troubles? > If no, which file tries to load "tcosmonitor.shared"? > > Do you have other packages not contained in testing and > any other sources.list, that may cause trouble? > LANG=C apt-show-versions | grep No > > Back in 2010, was this system installed from a > regular debian installer? > > Kind regards, > Bernhard > > [1] https://tracker.debian.org/pkg/tcosmonitor > signature.asc Description: This is a digitally signed message part
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Hello Bernhard, I get dropped back to xdm or sddm when I try to login to gnome-session. Attached to this message is the .xsession-errors log file of my guest user. Xorg.log says nothing special. The error now seems to be that gnome-session can't find the DISPLAY variable or the DISPLAY variable does not get set for gnome-session. As I wrote before, login to other window managers as amiwm do actually work. But as I wrote before, all GTK and GNOME applications have issues or errors after login was created through a display manager on my machine. I have had a look into alle config files in /etc/X11 and the only thing could be an old config file in /etc/X11/Xsession.d. Here is the whole login of /var/log/syslog: Apr 27 06:09:29 g6 systemd[1]: Created slice User Slice of UID 10003. Apr 27 06:09:29 g6 systemd[1]: Starting User Runtime Directory /run/user/10003... Apr 27 06:09:29 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 27 06:09:29 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 27 06:09:29 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 27 06:09:29 g6 systemd[1]: Started User Runtime Directory /run/user/10003. Apr 27 06:09:29 g6 systemd[1]: Starting User Manager for UID 10003... Apr 27 06:09:29 g6 systemd[22703]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Apr 27 06:09:29 g6 systemd[22703]: Starting D-Bus User Message Bus Socket. Apr 27 06:09:29 g6 systemd[22703]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Apr 27 06:09:29 g6 systemd[22703]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Apr 27 06:09:29 g6 systemd[22703]: Reached target Timers. Apr 27 06:09:29 g6 systemd[22703]: Listening on Sound System. Apr 27 06:09:29 g6 systemd[22703]: Listening on GnuPG network certificate management daemon. Apr 27 06:09:29 g6 systemd[22703]: Listening on GnuPG cryptographic agent and passphrase cache. Apr 27 06:09:29 g6 systemd[22703]: Reached target Paths. Apr 27 06:09:29 g6 systemd[22703]: Listening on D-Bus User Message Bus Socket. Apr 27 06:09:29 g6 systemd[22703]: Reached target Sockets. Apr 27 06:09:29 g6 systemd[22703]: Reached target Basic System. Apr 27 06:09:29 g6 systemd[22703]: Reached target Default. Apr 27 06:09:29 g6 systemd[22703]: Startup finished in 128ms. Apr 27 06:09:29 g6 systemd[1]: Started User Manager for UID 10003. Apr 27 06:09:29 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 27 06:09:29 g6 systemd[1]: Started Session 494 of user guest. Apr 27 06:09:29 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 27 06:09:29 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 27 06:09:29 g6 systemd[22703]: Started D-Bus User Message Bus. Apr 27 06:09:29 g6 dbus-daemon[22725]: [session uid=10003 pid=22725] Activating via systemd: service name='org .a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.7' (uid=10003 pid=22780 comm="/usr/lib/gnome-sessio n/gnome-session-check-acceler") Apr 27 06:09:29 g6 systemd[22703]: Starting Accessibility services bus... Apr 27 06:09:29 g6 dbus-daemon[22725]: [session uid=10003 pid=22725] Successfully activated service 'org.a11y. Bus' Apr 27 06:09:29 g6 systemd[22703]: Started Accessibility services bus. Apr 27 06:09:29 g6 at-spi-bus-launcher[22788]: dbus-daemon[22793]: Activating service name='org.a11y.atspi.Reg istry' requested by ':1.0' (uid=10003 pid=22780 comm="/usr/lib/gnome- session/gnome-session-check-acceler") Apr 27 06:09:29 g6 at-spi-bus-launcher[22788]: dbus-daemon[22793]: Successfully activated service 'org.a11y.at spi.Registry' Apr 27 06:09:29 g6 at-spi-bus-launcher[22788]: SpiRegistry daemon is running with well-known name - org.a11y.a tspi.Registry Apr 27 06:09:29 g6 gnome-session-binary[22717]: Entering running state Apr 27 06:09:30 g6 gnome-session[22717]: Unable to init server: Could not connect: Connection refused Apr 27 06:09:30 g6 gnome-session-f[22809]: Cannot open display: Apr 27 06:09:30 g6 systemd[22703]: Stopping D-Bus User Message Bus... Apr 27 06:09:30 g6 at-spi2-registr[22795]: Failed to send session response The connection is closed Apr 27 06:09:30 g6 systemd[22703]: at-spi-dbus-bus.service: Succeeded. Apr 27 06:09:30 g6 systemd[22703]: dbus.service: Succeeded. Apr 27 06:09:30 g6 systemd[22703]: Stopped D-Bus User Message Bus. Apr 27 06:09:30 g6 systemd[22703]: Started D-Bus User Message Bus. Apr 27 06:09:30 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Thank you very much for your kind attention. Yours sincerely, Adrian -- With many greetings from Leipzig, Germany. Adrian Immanuel Kieß Gothaer Straße 34 D-04155 Leipzig Administrator & programmer Unix ∧ Perl ∧ Java ∧ LaTeX 📪 — < adr...@kiess.onl >
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Dear Bernhard, after some updates to Debian/testing the old bug went away. I try to login with my user guest with a clean home directory. Now the error is: Apr 26 03:39:35 g6 gnome-session-binary[9035]: Entering running state Apr 26 03:39:35 g6 gnome-session[9035]: Unable to init server: Could not connect: Connection refused Apr 26 03:39:35 g6 gnome-session-f[9128]: Cannot open display: Logging in into amiwm works fine though! I also can't use a session created through xdm or a login manager because a lot of GNOME and GTK complain or even seqfault and won't start after creating a session through xdm. Using a console login and startx, everything works fine though. I suspect this is a general bug with login manager created X sessions. I also have to note, this is is a installation from the year 2010, always kept updated to newest Debian/testing. Maybe something broke meanwhile. Does this read any package maintainer? What could be the issue GNOME and GTK applications have when run through a login manager session in current Debian/testing. I also tried googling for this topic, but couldn't find any solution. Here is the log from syslog: Apr 26 03:39:34 g6 systemd[1]: Started User Manager for UID 10003. Apr 26 03:39:34 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 26 03:39:34 g6 systemd[1]: Started Session 7 of user guest. Apr 26 03:39:34 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 26 03:39:34 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '' f ailed Apr 26 03:39:34 g6 systemd[9021]: Started D-Bus User Message Bus. Apr 26 03:39:35 g6 dbus-daemon[9043]: [session uid=10003 pid=9043] Activating via systemd: service name='org.a 11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.7' (uid=10003 pid=9098 comm="/usr/lib/gnome-session/g nome-session-check-acceler") Apr 26 03:39:35 g6 systemd[9021]: Starting Accessibility services bus... Apr 26 03:39:35 g6 dbus-daemon[9043]: [session uid=10003 pid=9043] Successfully activated service 'org.a11y.Bu s' Apr 26 03:39:35 g6 systemd[9021]: Started Accessibility services bus. Apr 26 03:39:35 g6 at-spi-bus-launcher[9107]: dbus-daemon[9112]: Activating service name='org.a11y.atspi.Regis try' requested by ':1.0' (uid=10003 pid=9098 comm="/usr/lib/gnome- session/gnome-session-check-acceler") Apr 26 03:39:35 g6 at-spi-bus-launcher[9107]: dbus-daemon[9112]: Successfully activated service 'org.a11y.atsp i.Registry' Apr 26 03:39:35 g6 at-spi-bus-launcher[9107]: SpiRegistry daemon is running with well-known name - org.a11y.at spi.Registry Apr 26 03:39:35 g6 gnome-session-binary[9035]: Entering running state Apr 26 03:39:35 g6 gnome-session[9035]: Unable to init server: Could not connect: Connection refused Apr 26 03:39:35 g6 gnome-session-f[9128]: Cannot open display: Thank you very much, Adrian -- With many greetings from Leipzig, Germany. Adrian Immanuel Kieß Gothaer Straße 34 D-04155 Leipzig Administrator & programmer Unix ∧ Perl ∧ Java ∧ LaTeX 📪 — < adr...@kiess.onl > 🌍 — https://www.kiess.onl ☕ — https://arosusi.kiess.onl 🐇 — https://jexercise.kiess.onl --SYSTEM-- echo "Your fortune cookie: " && /usr/games/fortune -c -s > (men-women) % A beautiful woman is a blessing from Heaven, but a good cigar > is a smoke. -- Kipling echo "KIESS.ONL uptime: " && /usr/bin/uptime > 03:40:50 up 5 min, 3 users, load average: 1.43, 0.87, 0.40 On Mon, 2019-04-08 at 17:25 +0200, Bernhard Übelacker wrote: > 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 > signature.asc Description: This is a digitally signed message part
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Hello Bernhard, yes, I still encounter this bug in Debian/testing (Buster). I still can't login to a GNOME session using sddm. Using startx and running gnome-session from ~/.xinitrc everything works fine. I suspect running the X session from a display manager some environment variables do not get set correctly also. Because when I login to Enlightenment DR17 through sddm I also have an error configuring desktop-file-utils though apt. Here is the error shown: Processing triggers for desktop-file-utils (0.23-4) ... dpkg: error processing package desktop-file-utils (--configure): installed desktop-file-utils package post-installation script subprocess returned error exit status 1 Running apt via an login shell on the console everything works fine and the post-installation script succeeds. I don't have any of those old GNOME applications installed, you mentioned. I still wonder what could be the issue. Thanks for your help. Yours sincerely, Adrian -- With many greetings from Leipzig, Germany. Adrian Immanuel Kieß Gothaer Straße 34 D-04155 Leipzig Administrator & programmer Unix ∧ Perl ∧ Java ∧ LaTeX 📪 — < adr...@kiess.onl > 🌍 — https://www.kiess.onl # Dem Ingenieur ist nichts zu schwör ☕ — https://arosusi.kiess.onl # Nickpage of Adrian Immanuel Kieß 🐇 — https://outanekka.kiess.onl # Outanekka online imagery --SYSTEM-- echo "Your fortune cookie: " && /usr/games/fortune -c -s > (people) % Others can stop you temporarily, only you can do it permanently. echo "KIESS.ONL uptime: " && /usr/bin/uptime > 06:07:59 up 3 days, 23:43, 6 users, load average: 1.59, 1.60, 1.63 On Sat, 2019-03-16 at 16:47 +0100, Bernhard Übelacker wrote: > > > Hello Adrian Immanuel, > I am sorry for the late reply. > > First a question: Do you still observe this fault? > > > I took a look today inside the md5sums you supplied > and tried to reproduce this setup inside a VM. > > Unfortunately I found following old packages that are not > packaged in Debian anymore or maybe not installed in the > latest version: > > nautilus-pastebin: last built 2012, found just at > snapshot.debian.org > geoclue: last in jessie > easytag: not in the lastest version? > command-runner-applet: last in jessie > gnome-search-tool: last in stretch > sflphone-gnome: last in stretch > > Can you please have a look at these packages, if you > really use them? > If not you might uninstall them and test if you still > can observe the not launching applications? > > If you use synaptic, there should be a folder with outdated packages. > > > However, I tried to put your gsettings.compiled into that VM > and could login into GNOME and GNOME Classic sessions without > hitting that fault (traps: gnome-session-b...). > > Kind regards, > Bernhard > signature.asc Description: This is a digitally signed message part
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Dear Bernhard, thank you for your message. I have in fact installed gschemas.compiled: root@g6 (/usr/share/glib-2.0/schemas) % ls -la |grep compiled -rw-r--r-- 1 root root 557484 Feb 9 08:34 gschemas.compiled I tried setting the environment variable in /etc/environment which did not fix the issue. Still I can't login to a GNOME session from sddm or start any GTK/GNOME application when logging in to another window manager like FVWM. The shell says core dumped when trying to launch gedit for example. I have installed gesettings-desktop-schemas version: root@g6 (/usr/share/glib-2.0/schemas) % dpkg -l | grep gsettings-desktop-schemas ii gsettings-desktop-schemas 3.28.1-1 all GSettings desktop-wide schemas ii gsettings-desktop-schemas-dev:amd64 3.28.1-1 amd64Development files for GSettings desktop-wide schemas Do you now have an idea how to fix this bug? Thank you very much in advance. Yours sincerely, Adrian -- With many greetings from Leipzig, Germany. Adrian Immanuel Kieß Gothaer Straße 34 D-04155 Leipzig Administrator & programmer Unix ∧ Perl ∧ Java ∧ LaTeX 📪 — < adr...@kiess.onl > 🌍 — https://www.kiess.onl # Dem Ingenieur ist nichts zu schwör ☕ — https://arosusi.kiess.onl # Nickpage of Adrian Immanuel Kieß 🐇 — https://outanekka.kiess.onl # Outanekka online imagery --SYSTEM-- echo "Your fortune cookie: " && /usr/games/fortune -c -s > (work) % Please keep your hands off the secretary's reproducing equipment. echo "KIESS.ONL uptime: " && /usr/bin/uptime > 09:55:54 up 14 min, 2 users, load average: 1.26, 0.80, 0.45 On Mon, 2019-02-04 at 23:44 +0100, Bernhard Übelacker wrote: > Control: tags 920139 + moreinfo > > > Hello Adrian, > > Am 03.02.19 um 09:24 schrieb Adrian Immanuel Kiess: > > The bug is, like I see it, that the applications cannot find the > > gsettings schema directory. > > From my point of view it might be more the file gschemas.compiled > inside that directory. Does that exist on your system? > > > When setting export GSETTINGS_SCHEMA_DIR="/usr/share/glib- > > 2.0/schemas/" > > in my .xinitrc I can launch GTK and GNOME applications when the > > xsession ist started with startx. > > > > Therefor setting GSETTINGS_SCHEMA_DIR in /etc/environment maybe > > fixes > > the issue, which I have not tried yet. > > My previous test was inside a minimal buster amd64 VM where I > installed > just "systemd-coredump xserver-xorg sddm gnome-session" and there I > can > login in sddm to a "GNOME on Xorg" session without showing that > problem. > I searched that VM and could find no file setting that environment. > > I tried renaming that file gschemas.compiled and setting the > environment > like you did - but I still got the trap. > > Therefore you might also install a coredump collector > like systemd-coredump. > That way after such an unsuccessful logon attempt you can list with: > > coredumpctl list > > And produce an exact backtrace in which function that error is > thrown by this command: > > coredumpctl gdb [PID] > bt > > Best would be if debug symbol packages > gnome-session-bin-dbgsym libglib2.0-0-dbgsym > are installed like described in [1]. > > > Shall I resubmit the bug against gsettings-desktop-schemas package? > > If you mean with resumit to create a new bug, that should not be > needed > as this bug can be reassigned to another package too. > Which version of package gsettings-desktop-schemas have you > installed? > > dpkg -l | grep gsettings-desktop-schemas > > Kind regards, > Bernhard > > [1] > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols signature.asc Description: This is a digitally signed message part
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Dear Bernhard, thank you very much for your reply. The bug is, like I see it, that the applications cannot find the gsettings schema directory. When setting export GSETTINGS_SCHEMA_DIR="/usr/share/glib-2.0/schemas/" in my .xinitrc I can launch GTK and GNOME applications when the xsession ist started with startx. Therefor setting GSETTINGS_SCHEMA_DIR in /etc/environment maybe fixes the issue, which I have not tried yet. Shall I resubmit the bug against gsettings-desktop-schemas package? Yours sincerely, Adrian -- With many greetings from Leipzig, Germany. Adrian Immanuel Kieß Gothaer Straße 34 D-04155 Leipzig Administrator & programmer Unix ∧ Perl ∧ Java ∧ LaTeX 📪 — < adr...@kiess.onl > 🌍 — https://www.kiess.onl # Dem Ingenieur ist nichts zu schwör ☕ — https://arosusi.kiess.onl # Nickpage of Adrian Immanuel Kieß 🐇 — https://outanekka.kiess.onl # Outanekka online imagery --SYSTEM-- echo "Your fortune cookie: " && /usr/games/fortune -c -s > (goedel) % For 20 dollars, I'll give you a good fortune next time ... echo "KIESS.ONL uptime: " && /usr/bin/uptime > 09:18:19 up 12 days, 2:54, 4 users, load average: 1.39, 1.33, 1.68 On Thu, 2019-01-31 at 16:59 +0100, Bernhard Übelacker wrote: > Hello Adrian Immanuel Kiess, > I tried to search the net about this message: > "GLib-GIO-ERROR: No GSettings schemas are installed on the > system" > > And found results pointing to .../share/glib-2.0/schemas/. > Therefore renamed following file: > /usr/share/glib-2.0/schemas/gschemas.compiled > > And received on the next logon attempt a similar trap > message as you did. > > Therefore I assume this is based on this file missing or corrupt, > and unrelated to the sddm package, but not sure to which package > to reassign. > > Are all packages in a configured state? Does following do any > changes: > apt install -f > > I could trigger a recreation when the file was missing by e.g.: > apt install --reinstall yelp > > Were there any faults when installing/upgrading > some gnome packages lately? > Could you inspect this file on your system > or let it be recreated? > > Kind regards, > Bernhard > > > > root@debian:~# journalctl | grep traps -B4 > Jan 31 16:30:09 debian gnome-session[1233]: gnome-session- > binary[1233]: GLib-GIO-ERROR: No GSettings schemas are installed on > the system > Jan 31 16:30:09 debian gnome-session[1233]: aborting... > Jan 31 16:30:09 debian gnome-session-binary[1233]: GLib-GIO-ERROR: No > GSettings schemas are installed on the system >aborting... > Jan 31 16:30:09 debian kernel: traps: gnome-session-b[1233] trap int3 > ip:7ff639d19be5 sp:7fff4eda4490 error:0 in libglib- > 2.0.so.0.5800.2[7ff639ce1000+7e000] > > > > (gdb) bt > #0 0x7ff639d19be5 in _g_log_abort (breakpoint=1) at > ../../../glib/gmessages.c:554 > #1 0x7ff639d1aefd in g_logv (log_domain=0x7ff639f6f4e7 "GLib- > GIO", log_level=G_LOG_LEVEL_ERROR, format=, > args=args@entry=0x7fff4eda4560) at ../../../glib/gmessages.c:1371 > #2 0x7ff639d1b0cf in g_log (log_domain=log_domain@entry=0x7ff639 > f6f4e7 "GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_ERROR, > format=format@entry=0x7ff639f8e0d8 "No GSettings schemas are > installed on the system") at ../../../glib/gmessages.c:1413 > #3 0x7ff639f1f171 in g_settings_set_property (object= out>, prop_id=, value=0x7fff4eda46c0, pspec= out>) at ../../../gio/gsettings.c:585 > #4 0x7ff639dfb8c9 in object_set_property (nqueue=0x561977752880, > value=, pspec=0x561977747e50, object=0x561977743210) > at ../../../gobject/gobject.c:1447 > #5 g_object_new_internal (class=class@entry=0x561977769520, > params=params@entry=0x7fff4eda47f0, n_params=n_params@entry=1) at > ../../../gobject/gobject.c:1839 > #6 0x7ff639dfd3a4 in g_object_new_valist (object_type= out>, first_property_name=first_property_name@entry=0x7ff639f8dbf3 > "schema-id", var_args=var_args@entry=0x7fff4eda4940) at > ../../../gobject/gobject.c:2128 > #7 0x7ff639dfd6d9 in g_object_new (object_type=, > first_property_name=first_property_name@entry=0x7ff639f8dbf3 "schema- > id") at ../../../gobject/gobject.c:1648 > #8 0x7ff639f1f1c5 in g_settings_new (schema_id=schema_id@entry=0 > x561975bb51c5 "org.gnome.SessionManager") at > ../../../gio/gsettings.c:965 > #9 0x561975ba7fec in gsm_manager_init (manager=0x56197776a100) > at ../gnome-session/gsm-manager.c:3231 > #10 0x7ff639e190b7 in g_type_create_instance (type= out>) at ../../../gobject/gtype.c:1864 > #11 0x7ff639dfafe8 in g_object_constructor (type=, > n_construct_propert
Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2
Package: sddm Version: 0.18.0-1 Severity: important Dear Maintainer, currently in Debian/testing GNOME and GTK applications won't launch when the X session is launched through sddm or xdm. When trying to launch gnome-session through sddm the following glib2 and gnome- settings-schema related error occurs: Jan 22 06:24:53 g6 at-spi-bus-launcher[2919]: dbus-daemon[2923]: Activating service name=' org.a11y.atspi.Registry' requested by ':1.0' (uid=10003 pid=2911 comm="/usr/lib/gnome-sess ion/gnome-session-check-acceler") Jan 22 06:24:53 g6 at-spi-bus-launcher[2919]: dbus-daemon[2923]: Successfully activated se rvice 'org.a11y.atspi.Registry' Jan 22 06:24:53 g6 at-spi-bus-launcher[2919]: SpiRegistry daemon is running with well-know n name - org.a11y.atspi.Registry Jan 22 06:24:53 g6 kernel: [ 85.989074] traps: gnome-session-b[2854] trap int3 ip:7fbb40 09dbe5 sp:7ffe6ab4af90 error:0 in libglib-2.0.so.0.5800.2[7fbb40065000+7e000] Jan 22 06:24:53 g6 gnome-session[2854]: gnome-session-binary[2854]: GLib-GIO- ERROR: No GSe ttings schemas are installed on the system Jan 22 06:24:53 g6 gnome-session[2854]: aborting... Jan 22 06:24:53 g6 gnome-session-binary[2854]: GLib-GIO-ERROR: No GSettings schemas are in stalled on the system#012aborting... Jan 22 06:24:53 g6 sddm-helper[2832]: [PAM] Closing session Jan 22 06:24:53 g6 sddm-helper[2832]: [PAM] Ended. Jan 22 06:24:53 g6 NetworkManager[1031]: ((src/settings/nm-settings- connection.c:361)): as sertion '' failed Jan 22 06:24:53 g6 sddm[1582]: Auth: sddm-helper exited with 5 Jan 22 06:24:53 g6 at-spi-bus-launcher[2919]: XIO: fatal IO error 11 (Resource temporaril y unavailable) on X server ":0" Jan 22 06:24:53 g6 at-spi-bus-launcher[2919]: after 21 requests (21 known processed) with 0 events remaining. Jan 22 06:24:53 g6 sddm[1582]: Socket server stopping... Jan 22 06:24:53 g6 sddm[1582]: Socket server stopped. Jan 22 06:24:53 g6 sddm[1582]: Display server stopping... When launching a xession with xinit from the console GTK and GNOME apllication due in fact launch and work. I tried amiwm and fvvm through sddm and using xterm GTK and GNOME applications won't launch without an error message. The only error message I could capture is the error above when trying to launch the gnome-session directly through sddm or xdm. I would appriciate any advice. Thank you very much. Yours Sincerely, Adrian Immanuel Kieß -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sddm depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.70 ii libc6 2.28-5 ii libgcc1 1:8.2.0-14 ii libpam0g 1.1.8-4 ii libqt5core5a 5.11.3+dfsg-2 ii libqt5dbus5 5.11.3+dfsg-2 ii libqt5gui55.11.3+dfsg-2 ii libqt5network55.11.3+dfsg-2 ii libqt5qml55.11.3-2 ii libqt5quick5 5.11.3-2 ii libstdc++68.2.0-14 ii libsystemd0 240-4 ii libxcb-xkb1 1.13.1-2 ii libxcb1 1.13.1-2 ii qml-module-qtquick2 5.11.3-2 ii x11-common1:7.7+19 ii xnest [xserver] 2:1.20.3-1 ii xserver-xephyr [xserver] 2:1.20.3-1 ii xserver-xorg [xserver]1:7.7+19 ii xvfb [xserver]2:1.20.3-1 Versions of packages sddm recommends: ii haveged 1.9.1-6 ii libpam-systemd 240-4 ii sddm-theme-breeze [sddm-theme] 4:5.14.3-1+b1 Versions of packages sddm suggests: ii libpam-kwallet5 5.14.3-1 pn qtvirtualkeyboard-plugin -- debconf information: * shared/default-x-display-manager: sddm sddm/daemon_name: /usr/bin/sddm
