[SOLVED] Cannot run mutter on GNOME

Inu_Tokisaki · 2024-06-17 17:51:10

Hello,
after Arch install, one of the things I did was that I installed and ran rkhunter, it addressed mutter-x11-frames as a potential rootkit because it shared too much memory segments (it had the size of 16MB while configured size allowed was 1MB). When I ran the second scan the issue was not there, however, after some time I tried to check mutter and it is not even running, I can't even start it since I get

libmutter-Message: 19:46:51.917: Running Mutter (using mutter 46.2) as a Wayland display server
Failed to setup: Could not take control: GDBus.Error:System.Error.EBUSY: Device or resource busy

or

Failed to configure: Unsupported session type

when I run it as sudo. I installed gnome-tweaks and dash-to-dock extension from github since, it is possible that those two replaced mutter with something else? My GNOME session works as expected though.

Last edited by Inu_Tokisaki (2024-07-25 05:43:16)

seth · 2024-06-17 20:34:49

mutter /is/ gnome - the wayland compositor, the window manager and the shell is implemented into it as well.
mutter-x11-frames is a separate mutter process for xwayland clients and you cannot (explicitly) run mutter inside gnome because it's already running. You're looking at it.

Inu_Tokisaki · 2024-06-18 08:12:44

My point is that mutter-x11-frames was running, I saw it in htop and now there's no mutter. Also you said that mutter-x11-frames is for Xwayland, but I use Xorg, therefore I don't know why it was running in the first place

seth · 2024-06-18 15:43:15

My point is that mutter-x11-frames was running, I saw it in htop and now there's no mutter.

Please post the session status

loginctl session-status

Edit: don't copy and paste that out of the pager, redirect it into a file or pastebin service.ä

Last edited by seth (2024-06-18 15:43:46)

Inu_Tokisaki · 2024-06-19 05:50:34

seth wrote:

Please post the session status
loginctl session-status

3 - user (1000)
  Since: Wed 2024-06-19 07:43:59 CEST; 32s ago
  State: active
 Leader: 990 (gdm-session-wor)
   Seat: seat0; vc2
    TTY: tty2
 Remote: no
Service: gdm-password
   Type: wayland
  Class: user
   Idle: no
   Unit: session-3.scope
         ├─ 990 "gdm-session-worker [pam/gdm-password]"
         ├─1044 /usr/lib/gdm-wayland-session /usr/bin/gnome-session
         └─1049 /usr/lib/gnome-session-binary

Jun 19 07:44:00 arch systemd[1]: Started Session 3 of User user.

seth · 2024-06-19 08:04:35

but I use Xorg

Type: wayland

Is there otherwise still an open question?

Inu_Tokisaki · 2024-06-19 09:20:15

Okay, seems I don't understand it that well, but when I installed my DE I definitely installed Xorg, anyways, still the thing that bothers me is fact that the mutter-x11-frames was running before and now there is no process named "mutter" => was that just a temporary thing? And is the case of mutter-x11-frames being detected by rkhunter as potential rootkit just a normal false positive?

seth · 2024-06-19 14:11:18

"I definitely installed Xorg" has no meaning wrt what you're runngin - gnome defaults to wayland since some years.
Try to run "xterm" in your gnome-wayland session, the mutter-x11-frames will likely re-appear.

Arch Linux

#1 2024-06-17 17:51:10

[SOLVED] Cannot run mutter on GNOME

#2 2024-06-17 20:34:49

Re: [SOLVED] Cannot run mutter on GNOME

#3 2024-06-18 08:12:44

Re: [SOLVED] Cannot run mutter on GNOME

#4 2024-06-18 15:43:15

Re: [SOLVED] Cannot run mutter on GNOME

#5 2024-06-19 05:50:34

Re: [SOLVED] Cannot run mutter on GNOME

#6 2024-06-19 08:04:35

Re: [SOLVED] Cannot run mutter on GNOME

#7 2024-06-19 09:20:15

Re: [SOLVED] Cannot run mutter on GNOME

#8 2024-06-19 14:11:18

Re: [SOLVED] Cannot run mutter on GNOME

Board footer