Bug 1168905 - Gnome does not obey /etc/group when reinlogging
Gnome does not obey /etc/group when reinlogging
Status: CONFIRMED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: GNOME
Current
x86-64 SUSE Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-04-07 18:44 UTC by Andreas Nordal
Modified: 2020-04-09 18:13 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Nordal 2020-04-07 18:44:16 UTC
I have added myself to a few groups in /etc/group. This works in KDE and the Linux console, but not in GNOME.

A quick search points to uncommenting pam_kwallet.so needing from /etc/pam.d/xdm, but I don't have it there, and I don't have the package pam_kwallet installed.
Comment 1 Neil Rickert 2020-04-08 03:40:56 UTC
It is working fine here:

% groups
users root systemd-journal wheel support rickert

I get that output with both Gnome-terminal and xterm.  I'm logged into Gnome (Wayland) under Tumbleweed in a KVM virtual machine to test that.

I am using GDM as display manager (login screen).  And commands seem to work as they should according to those groups.  For example, I can read "/var/log/messages" (yes, I have rsyslog installed for managing logs).

Perhaps you should indicate:
 Whether Gnome-wayland or Gnome X11
 Which display manager (login screen) are you using
 How are you testing this.
Comment 2 Andreas Nordal 2020-04-09 16:44:06 UTC
More specifically, GNOME doesn't obey /etc/group when logging out and in again.

So the test is to add yourself to one more group, log out, and in again. This works in KDE but not GNOME.
Comment 3 Andreas Nordal 2020-04-09 16:56:40 UTC
Forgot to say: I tested with SDDM, GNOME on Wayland and KDE on Wayland.

(I verified that both desktops could run weston-terminal, to be sure they were using Wayland.)

(SDDM appears to be the default if choosing KDE when installing Tumbleweed.)
Comment 4 Neil Rickert 2020-04-09 18:13:23 UTC
Okay, I am able to confirm this.  So I will mark the bug as confirmed.

I am not at all sure that this counts as a bug.  If it were up to me, I would probably call it a feature.

ANALYSIS:

When you login, "systemd" starts a systemd user process.  I think this is the "logind" service.  That process is persistent.  If you logout, the process still remains.

When using Gnome, then entire Gnome session is a child or descendant of that persistent logind process.  And since that process is persistent, it retains the groups that were set when that process started (your first login).

When using KDE, by contrast, a completely new session is started.  So your KDE desktop session is not a descendant of the persistent logind process.  Instead, it goes through the initialization of groups afresh and does pick up changes to "/etc/group".

If you were to reboot after changing "/etc/group", then your next Gnome login would pickup the new group (TESTED).

If you were to logout from Gnome, login at a terminal (virtual console) and kill that logind persistent session, then the next Gnome login should re-initialize the groups (NOT TESTED).