[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#920139: sddm: GTK and GNOME: Applications won't launch due error of glib2



Hello Adrian,


> Using a console login and startx, everything works fine though.
> 
> 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.
> 
> 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.

So I have installed in a minimal Buster amd64 VM these packages:
    xdm gnome
And configured xdm as default.
With that I could login just fine, so this seems not an issue
in a fresh installation.


In this configuration it looks like gnome is running with xorg.
Therefore you might also have a look into $HOME/.xsession-errors
and /var/log/Xorg.0.log or /var/log/Xorg.1.log.

Do you get dropped back to xdm immediately or do you stay at e.g. a
black screen?

Is there anything in the syslog above the "Started User Manager for..."
message in the same second and a few before?


> Does this read any package maintainer?

Currently this bug is assigned to package sddm, so just
sddm maintainer might have this on the screen.
Also your last email describes kind of a different issue,
with not even sddm involved.

Because you say this can be seen with sddm and xdm I guess
the problem might not be in these packages, therefore reassigning
to gnome-session might attract the right people?

Kind regards,
Bernhard


Reply to: