can't start gnome-shell session

gabx · 2023-01-19 17:13:46

I have been using gnome-shell for a while with no issue at all. I had to modify part of my Arch recently (especially remove/create users) and I have now an issue with gnome-shell session.
Note: system is up-to-date; I use systemd-homed to create and manage users.
The main and only one user I have been using for years is myself, user gabx. With the very minimal home folders right after the creation of user gabx with homectl create, I can't log gnome with the command:

$ gnome-session --wayland

The above command returns:

libmutter-Message: Running Gnome Shell as a Wayland display server

but my system hangs and I need to reboot. journalctl doesn't show any error regarding gnome-session login.
Now comes the weird part.If I create a new random user (call it toto the same way with homectl create, I can now login gnome-shell!
The only diff I see between user gabx and toto is that the former has been the active one user on my system for years (so it shall owns may files on my system and in use with some services) when the later did not exist before. Both home folders are the same, limited to what homectl has created.

I don't know how to debug my issue, understand why gnome-shell login is broken and how to interpret the fact one user can log and not another one. Thank you for help.

seth · 2023-01-19 22:39:54

but my system hangs and I need to reboot

You cannot
a) switch to a different VT?
b) ssh into the system?

If I create a new random user (call it toto the same way with homectl create, I can now login gnome-shell!

* Do you have a ~/.drirc ?
* https://wiki.archlinux.org/title/GNOME/ … _the_shell
* Can you get a journal for the failing session?

gabx · 2023-01-20 16:14:06

- I can't log from another terminal. Need hard reboot
- no ~/.dric
- I removed gnome user-theme and auto-move windows as suggested,but still unable to log the session
- I don't know what you call journal for the falling session, I only run

$ journalctl -r --user

or only journalctl -r

Last edited by gabx (2023-01-20 16:15:15)

seth · 2023-01-20 16:35:42

What about

seth wrote:

ssh into the system?

the wiki wrote:

Otherwise, isolate the problem extension with trial‑and‑error.

Also try to get rid of all other extensions exclusive to your UID

"journalctl -r" will display the entire journal in reverse order, so you're seeing the journal of the running session.
The question would be whether there's an entry for the session where "my system hangs and I need to reboot" - rebooting w/ the power button will largely prevent the journal from being written, so try to restart by frenetically pressing ctrl+alt+del.

The pink elephant in the room is systemd-homed messing up the UID mapping or file permissions or perhaps decrypting the LUKS container, but in that case I'd assume that the login would fail entirely.
Can you start a weston/sway (wayland) or openbox/gnome on X11 session?

gabx · 2023-01-24 13:17:00

seth wrote:

What about ssh into the system?

No, I didn't try this way as no ssh is running

seth wrote:

rebooting w/ the power button will largely prevent the journal from being written, so try to restart by frenetically pressing ctrl+alt+del.

OK, I will give a tr y

seth wrote:

The pink elephant in the room is systemd-homed messing up the UID mapping or file permissions or perhaps decrypting the LUKS container, but in that case I'd assume that the login would fail entirely.

No LUKS in my setup,only a BTRFS subvolume.Yes, the UID maping may well be damaged. Anyway to check?

gabx · 2023-01-24 14:08:25

I was looking at my BTRFS setup and wonder if my issue does not come from a bad setup.

# btrfs subvolume list -p /
ID 256 gen 104217 top level 5 path @
ID 257 gen 104201 top level 5 path @home
ID 258 gen 103788 top level 5 path @var
...
ID 289 gen 103772 top level 5 path home
ID 315 gen 104157 top level 257 path @home/toto.homedir
ID 316 gen 104212 top level 257 path @home/gabx.homedir

I wonder why two subvolumes: one @home and one home.
Isn't this last one (home) unnecessary?

Last edited by gabx (2023-01-24 14:42:22)

seth · 2023-01-24 14:51:40

Some snapshot? Not sure how that would selectively impact only one user, though.

as no ssh is running

Well, run it?
If this is a visual thing only, remote access to the running "frozen" system might be very insightful.

Anyway to check?

Compare the "id" of your logged in user (before running gnome) with the ownership of files in your $HOME (particularily the gnome stuff, but the entire path - the fat DEs freak out when they can't write in $HOME)

Arch Linux

#1 2023-01-19 17:13:46

can't start gnome-shell session

#2 2023-01-19 22:39:54

Re: can't start gnome-shell session

#3 2023-01-20 16:14:06

Re: can't start gnome-shell session

#4 2023-01-20 16:35:42

Re: can't start gnome-shell session

#5 2023-01-24 13:17:00

Re: can't start gnome-shell session

#6 2023-01-24 14:08:25

Re: can't start gnome-shell session

#7 2023-01-24 14:51:40

Re: can't start gnome-shell session

Board footer