Author Topic: Gnome: oops something gone wrong, both xorg and wayland  (Read 487 times)

dufresnep

  • Newbie
  • *
  • Posts: 28
  • Karma: +0/-0
Gnome: oops something gone wrong, both xorg and wayland
« on: Fri Oct 25 18:10:29 2019 »
I have installed gnome, and got the almost usual "oops, something gone wrong".

I tried to install xorg-xf86-video-ati (rather than use kms), but it did not change anything.

I don't really know where I should looks for debug messages. I took a short look inside /var/log ... but did not seens pertinent info.

dufresnep

  • Newbie
  • *
  • Posts: 28
  • Karma: +0/-0
Re: Gnome: oops something gone wrong, both xorg and wayland
« Reply #1 on: Sat Oct 26 00:50:28 2019 »
Well, first I have found:  cat /var/log/sys| grep -i gnome
Code: [Select]
Oct 25 19:22:58 nutyx dbus-daemon[3070]: [session uid=0 pid=3068] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=3080 comm="/usr/libexec/gnome-session-check-accelerated ")
Oct 25 19:22:58 nutyx dbus-daemon[3070]: [session uid=0 pid=3068] Activating service name='org.gtk.vfs.Daemon' requested by ':1.2' (uid=0 pid=3080 comm="/usr/libexec/gnome-session-check-accelerated ")
Oct 25 19:22:58 nutyx gnome-session-binary[3052]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1 was not provided by any .service files
Oct 25 19:22:58 nutyx gnome-session-binary[3052]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 25 19:22:58 nutyx gnome-session-binary[3052]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Oct 25 19:22:58 nutyx gnome-session-binary[3052]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Oct 25 19:22:58 nutyx gnome-session-binary[3052]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Oct 25 19:22:59 nutyx gnome-session-binary[3052]: WARNING: App 'pulseaudio.desktop' exited with code 1

Now, this Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
seems to be often present on Linux distros NOT USING Systemd. The solution is easy: use systemd  ;D

No more seriously, one can read that it has been a problem with Gnome:
https://www.phoronix.com/scan.php?page=news_item&px=Gentoo-GNOME-3.30-No-Systemd
which links to:
https://www.gentoo.org/news/2019/03/27/gnome-330-openrc.html

which explains that elogind, is a program that somehow fake the presence of systemd, and allows login.

We have a very recent (if not the last) of elogind.
But this is not enough, some programs must be patched to use elogind (through the use of pkg-config):
https://github.com/elogind/elogind/issues/70
but I have not investigated (not even sure I am qualified to investigate this) that we haved patched versions for these packages.

In a related bug: https://github.com/elogind/elogind/issues/61
the guy seems to suggest the problem was that he was using a su from busybox, rather than from... I don't know, I don't really understood this.

Thierry

  • Administrator
  • Hero Member
  • *****
  • Posts: 513
  • Karma: +7/-0
  • Gender: Male
    • NuTyX distribution
Re: Gnome: oops something gone wrong, both xorg and wayland
« Reply #2 on: Thu Oct 31 08:44:33 2019 »
I confirm this bug  >:(

Working on it
 

Thierry

  • Administrator
  • Hero Member
  • *****
  • Posts: 513
  • Karma: +7/-0
  • Gender: Male
    • NuTyX distribution
[FIXED]Re: Gnome: oops something gone wrong, both xorg and wayland
« Reply #3 on: Fri Nov 01 07:08:04 2019 »
Fixed