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 '<dropped>' 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 '<dropped>' f ailed Apr 26 03:39:34 g6 NetworkManager[917]: ((src/settings/nm-settings- connection.c:361)): assertion '<dropped>' 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 📪 — < adrian@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 >
Attachment:
signature.asc
Description: This is a digitally signed message part