"Caja" does not start when compositor is enabled

radax05 · 25 April 2025 10:31

Surprise, surprise... I had this morning when starting the Ubuntu 24.04.2 (all updates!).

Tried to start caja

as simple user => caja does not open at all!
using sudo caja in a Terminal => caja starts (but as "super user")

LogViewer shows a lot of Kernel error messages (like below).

2025-04-25T06:34:09.407335+02:00 MRSPC9 kernel: traps: caja[15851] general protection fault ip:59b56f461766 sp:7ffc57cbf0c0 error:0 in caja[59b56f414000+12d000]
2025-04-25T06:34:10.839347+02:00 MRSPC9 kernel: traps: caja[15867] general protection fault ip:5e3abce5d766 sp:7ffcb5d1d6a0 error:0 in caja[5e3abce10000+12d000]
2025-04-25T06:34:12.293342+02:00 MRSPC9 kernel: traps: caja[15886] general protection fault ip:5c33f7bdb766 sp:7ffd686d4c50 error:0 in caja[5c33f7b8e000+12d000]
2025-04-25T06:34:13.715337+02:00 MRSPC9 kernel: traps: caja[15901] general protection fault ip:631bf9a7a766 sp:7ffed82dc160 error:0 in caja[631bf9a2d000+12d000]
2025-04-25T06:34:15.164352+02:00 MRSPC9 kernel: traps: caja[15918] general protection fault ip:63a059e7c766 sp:7ffd585ec650 error:0 in caja[63a059e2f000+12d000]
2025-04-25T06:34:16.565359+02:00 MRSPC9 kernel: traps: caja[15934] general protection fault ip:5a1056aa7766 sp:7ffd224be3d0 error:0 in caja[5a1056a5a000+12d000]
2025-04-25T06:34:17.991360+02:00 MRSPC9 kernel: traps: caja[15950] general protection fault ip:5958e04b8766 sp:7ffdcc9d9ac0 error:0 in caja[5958e046b000+12d000]
2025-04-25T06:34:19.403409+02:00 MRSPC9 kernel: traps: caja[15966] general protection fault ip:64623a4a2766 sp:7ffe8195af00 error:0 in caja[64623a455000+12d000]
2025-04-25T06:34:20.859346+02:00 MRSPC9 kernel: traps: caja[15982] general protection fault ip:5739394ab766 sp:7ffede00f060 error:0 in caja[57393945e000+12d000]
2025-04-25T06:34:22.294340+02:00 MRSPC9 kernel: traps: caja[15998] general protection fault ip:57c2a6134766 sp:7ffc1f02c340 error:0 in caja[57c2a60e7000+12d000]

Log out and log in => does not help
Restart PC => does not help

Searching the Ubuntu MATE forum => cannot find anything related to this issue
Searching the Internet => suggestion to change the Window Manager

MATE Tweak => Windows => Window Manager to "Marco (No compositor)" (previously: "Marco: XPresent")

And yes, it works now.

What I did afterwards (it may be useless!):

sudo apt-get install --reinstall untuntu-mate-desktop

(according to what was shown in Terminal, there were not changes)

Afterwards, I did not restart / log in again, nor change anything else in configs.

Note: I usually leave some "File Explorer" (caja) windows open when shutting down my PC. And the "caja" windows usually start as expected when starting the PC.
But, at some times during the last months I was surprised that the "caja" windows were not restored when starting the PC. Did not worry because I could always start Caja... TODAY it was not possible at all, until the workaround.

Don't know if I should report this issue or not. After workaround, it works as expected.

lah7 · 25 April 2025 13:03

What graphics card / stack do you use?

Since the traps only happen when the compositor is enabled, I wonder if a kernel update caused the regression, if it's something like Intel onboard graphics.

The old kernel should still be around to check, you should be able to hold SHIFT while booting to bring up the GRUB boot menu, and choosing the older version in "Advanced options". You might need to change GRUB's configuration in /etc/default/grub to show the menu or increase the timeout if it does not appear (see the bottom of this answer)

If you want to go deeper for "what" caused it, you could check /var/log/apt/history.log and post here what packages were updated (before the ubuntu-mate-desktop reinstall command was issued)

radax05 · 25 April 2025 13:25

Thank you so much for replying

mihai@MRSPC9:~$ inxi -ACDMNSG
System:
  Host: MRSPC9 Kernel: 6.8.0-58-generic arch: x86_64 bits: 64
  Desktop: MATE v: 1.26.2 Distro: Ubuntu MATE 24.04.2 LTS (Noble Numbat)
Machine:
  Type: Desktop Mobo: Acer model: Aspire XC-1760 v: 1.0
    serial: <superuser required> UEFI: American Megatrends v: R01-B0
    date: 05/06/2022
CPU:
  Info: 6-core model: 12th Gen Intel Core i5-12400 bits: 64 type: MT MCP
    cache: L2: 7.5 MiB
  Speed (MHz): avg: 1269 min/max: 800/4400 cores: 1: 800 2: 802 3: 1569
    4: 1413 5: 1600 6: 1600 7: 801 8: 800 9: 1700 10: 1651 11: 1700 12: 801
Graphics:
  Device-1: Intel Alder Lake-S GT1 [UHD Graphics 730] driver: i915 v: kernel
  Device-2: Generic AIRHUG 11 driver: snd-usb-audio,uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
    resolution: 3840x2160~60Hz
  API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa
    v: 24.2.8-1ubuntu1~24.04.1 renderer: Mesa Intel UHD Graphics 730 (ADL-S GT1)

From "/var/log/apt/history.log" (went back to the 11th of April, 2025):

Start-Date: 2025-04-11  21:48:45
Commandline: aptdaemon role='role-commit-packages' sender=':1.110'
Upgrade: libsnmp-base:amd64 (5.9.4+dfsg-1.1ubuntu3, 5.9.4+dfsg-1.1ubuntu3.1), mutter-common-bin:amd64 (46.2-1ubuntu0.24.04.6, 46.2-1ubuntu0.24.04.7), libsnmp40t64:amd64 (5.9.4+dfsg-1.1ubuntu3, 5.9.4+dfsg-1.1ubuntu3.1), libsnmp40t64:i386 (5.9.4+dfsg-1.1ubuntu3, 5.9.4+dfsg-1.1ubuntu3.1), libmutter-14-0:amd64 (46.2-1ubuntu0.24.04.6, 46.2-1ubuntu0.24.04.7), software-properties-common:amd64 (0.99.49.1, 0.99.49.2), pci.ids:amd64 (0.0~2024.03.31-1, 0.0~2024.03.31-1ubuntu0.1), python3-software-properties:amd64 (0.99.49.1, 0.99.49.2), mutter-common:amd64 (46.2-1ubuntu0.24.04.6, 46.2-1ubuntu0.24.04.7), libsoup2.4-common:amd64 (2.74.3-6ubuntu1.1, 2.74.3-6ubuntu1.2), libsoup-2.4-1:amd64 (2.74.3-6ubuntu1.1, 2.74.3-6ubuntu1.2), libsoup-3.0-0:amd64 (3.4.4-5ubuntu0.1, 3.4.4-5ubuntu0.2), gir1.2-mutter-14:amd64 (46.2-1ubuntu0.24.04.6, 46.2-1ubuntu0.24.04.7), software-properties-gtk:amd64 (0.99.49.1, 0.99.49.2), brave-browser:amd64 (1.77.95, 1.77.97), libsoup-3.0-common:amd64 (3.4.4-5ubuntu0.1, 3.4.4-5ubuntu0.2), gir1.2-soup-3.0:amd64 (3.4.4-5ubuntu0.1, 3.4.4-5ubuntu0.2), microsoft-edge-stable:amd64 (135.0.3179.54-1, 135.0.3179.73-1)
End-Date: 2025-04-11  21:49:07

Start-Date: 2025-04-15  15:38:12
Commandline: aptdaemon role='role-commit-packages' sender=':1.115'
Upgrade: perl:amd64 (5.38.2-3.2build2.1, 5.38.2-3.2ubuntu0.1), libjavascriptcoregtk-4.1-0:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), gir1.2-javascriptcoregtk-4.1:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), gir1.2-javascriptcoregtk-6.0:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), gir1.2-webkit2-4.1:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), libjavascriptcoregtk-6.0-1:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), libprotobuf-lite32t64:amd64 (3.21.12-8.2build1, 3.21.12-8.2ubuntu0.1), libwebkit2gtk-4.1-0:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), libprotobuf32t64:amd64 (3.21.12-8.2build1, 3.21.12-8.2ubuntu0.1), perl-base:amd64 (5.38.2-3.2build2.1, 5.38.2-3.2ubuntu0.1), gir1.2-webkit-6.0:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), perl-modules-5.38:amd64 (5.38.2-3.2build2.1, 5.38.2-3.2ubuntu0.1), libwebkitgtk-6.0-4:amd64 (2.48.0-0ubuntu0.24.04.1, 2.48.1-0ubuntu0.24.04.1), libperl5.38t64:amd64 (5.38.2-3.2build2.1, 5.38.2-3.2ubuntu0.1), libperl5.38t64:i386 (5.38.2-3.2build2.1, 5.38.2-3.2ubuntu0.1)
End-Date: 2025-04-15  15:38:16

Start-Date: 2025-04-16  13:58:56
Commandline: aptdaemon role='role-commit-packages' sender=':1.221'
Upgrade: gir1.2-gtk-3.0:amd64 (3.24.41-4ubuntu1.2, 3.24.41-4ubuntu1.3), gtk-update-icon-cache:amd64 (3.24.41-4ubuntu1.2, 3.24.41-4ubuntu1.3), 7zip:amd64 (23.01+dfsg-11, 23.01+dfsg-11ubuntu0.1~esm1)
End-Date: 2025-04-16  13:58:58

Start-Date: 2025-04-17  07:46:51
Commandline: aptdaemon role='role-commit-packages' sender=':1.169'
Install: linux-image-6.8.0-58-generic:amd64 (6.8.0-58.60+1, automatic), linux-headers-6.8.0-58-generic:amd64 (6.8.0-58.60, automatic), linux-modules-6.8.0-58-generic:amd64 (6.8.0-58.60, automatic), linux-tools-6.8.0-58:amd64 (6.8.0-58.60, automatic), linux-headers-6.8.0-58:amd64 (6.8.0-58.60, automatic), linux-tools-6.8.0-58-generic:amd64 (6.8.0-58.60, automatic), linux-modules-extra-6.8.0-58-generic:amd64 (6.8.0-58.60, automatic)
Upgrade: linux-tools-common:amd64 (6.8.0-57.59, 6.8.0-58.60), linux-headers-generic:amd64 (6.8.0-57.59, 6.8.0-58.60), libgail-3-0t64:amd64 (3.24.41-4ubuntu1.2, 3.24.41-4ubuntu1.3), linux-generic:amd64 (6.8.0-57.59, 6.8.0-58.60), linux-image-generic:amd64 (6.8.0-57.59, 6.8.0-58.60), linux-tools-generic:amd64 (6.8.0-57.59, 6.8.0-58.60), brave-browser:amd64 (1.77.97, 1.77.100), libgtk-3-common:amd64 (3.24.41-4ubuntu1.2, 3.24.41-4ubuntu1.3), libgtk-3-bin:amd64 (3.24.41-4ubuntu1.2, 3.24.41-4ubuntu1.3), vivaldi-stable:amd64 (7.3.3635.9-1, 7.3.3635.11-1), libgtk-3-0t64:amd64 (3.24.41-4ubuntu1.2, 3.24.41-4ubuntu1.3), libgtk-3-0t64:i386 (3.24.41-4ubuntu1.2, 3.24.41-4ubuntu1.3), linux-libc-dev:amd64 (6.8.0-57.59, 6.8.0-58.60)
End-Date: 2025-04-17  07:47:44

Start-Date: 2025-04-17  11:27:50
Commandline: apt autoremove
Requested-By: mihai (1000)
Remove: linux-headers-6.8.0-56-generic:amd64 (6.8.0-56.58), linux-modules-6.8.0-56-generic:amd64 (6.8.0-56.58), linux-image-6.8.0-56-generic:amd64 (6.8.0-56.58+1), linux-tools-6.8.0-56:amd64 (6.8.0-56.58), linux-headers-6.8.0-56:amd64 (6.8.0-56.58), linux-tools-6.8.0-56-generic:amd64 (6.8.0-56.58), linux-modules-extra-6.8.0-56-generic:amd64 (6.8.0-56.58)
End-Date: 2025-04-17  11:28:01

Start-Date: 2025-04-19  02:45:32
Commandline: aptdaemon role='role-commit-packages' sender=':1.116'
Upgrade: docker-compose-plugin:amd64 (2.34.0-1~ubuntu.24.04~noble, 2.35.1-1~ubuntu.24.04~noble), docker-ce-cli:amd64 (5:28.0.4-1~ubuntu.24.04~noble, 5:28.1.1-1~ubuntu.24.04~noble), docker-buildx-plugin:amd64 (0.22.0-1~ubuntu.24.04~noble, 0.23.0-1~ubuntu.24.04~noble), docker-ce:amd64 (5:28.0.4-1~ubuntu.24.04~noble, 5:28.1.1-1~ubuntu.24.04~noble), docker-ce-rootless-extras:amd64 (5:28.0.4-1~ubuntu.24.04~noble, 5:28.1.1-1~ubuntu.24.04~noble), microsoft-edge-stable:amd64 (135.0.3179.73-1, 135.0.3179.85-1)
End-Date: 2025-04-19  02:46:00

Start-Date: 2025-04-24  09:39:21
Commandline: aptdaemon role='role-commit-packages' sender=':1.174'
Upgrade: yelp-xsl:amd64 (42.1-2, 42.1-2ubuntu0.24.04.1), libarchive13t64:amd64 (3.7.2-2ubuntu0.3, 3.7.2-2ubuntu0.4), brave-browser:amd64 (1.77.100, 1.77.101), libyelp0:amd64 (42.2-1build2, 42.2-1ubuntu0.24.04.1), yelp:amd64 (42.2-1build2, 42.2-1ubuntu0.24.04.1)
End-Date: 2025-04-24  09:39:31

Start-Date: 2025-04-25  06:30:46
Commandline: aptdaemon role='role-commit-packages' sender=':1.115'
Upgrade: netplan-generator:amd64 (1.1.1-1~ubuntu24.04.1, 1.1.2-2~ubuntu24.04.1), openssh-client:amd64 (1:9.6p1-3ubuntu13.9, 1:9.6p1-3ubuntu13.11), python3-netplan:amd64 (1.1.1-1~ubuntu24.04.1, 1.1.2-2~ubuntu24.04.1), netplan.io:amd64 (1.1.1-1~ubuntu24.04.1, 1.1.2-2~ubuntu24.04.1), libnetplan1:amd64 (1.1.1-1~ubuntu24.04.1, 1.1.2-2~ubuntu24.04.1), microsoft-edge-stable:amd64 (135.0.3179.85-1, 135.0.3179.98-1)
End-Date: 2025-04-25  06:30:59

Start-Date: 2025-04-25  08:14:34
Commandline: apt reinstall ubuntu-mate-desktop
Requested-By: <my_user> (1000)
Reinstall: ubuntu-mate-desktop:amd64 (1.296)
End-Date: 2025-04-25  08:14:35

I'll do a test by loading an older kernel later today and I'll report related to "Marco" with compositor - may take some time as the issue may or may not occur - as stated before:

But, at some times during the last months I was surprised that the "caja" windows were not restored when starting the PC.

stephematician · 25 April 2025 23:40

Is it just me, or is it weird to see Xwayland come up in the output of inxi on an Ubuntu MATE desktop? This isn't the first time I've seen this on the forum lately, so there must be something that users are (often) doing that is causing wayland to be used as part of the display stack?

ugnvs · 26 April 2025 08:44

UM 24.04 upgraded from previous versions in place

...
  Display: x11 server: X.Org v: 21.1.11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1600x900~60Hz
...

and no sign of wayland. Ergo:

users are doing something
fresh install from CD/USB media includes wayland vs online version upgrade

stephematician · 26 April 2025 11:52

I don't think that a fresh install would have Wayland - Live USB/ISO doesn't have it, neither when I install it to a VM (and neither does 25.04). It must be something else.

ugnvs · 26 April 2025 12:35

Quick Internet search says that wayland is the default display server since upstream Ubuntu 22.04. It looks like some users have upstream Ubuntu with Mate desktop.

radax05 · 26 April 2025 12:49

PC was installed back in April 2024 with UM 24.04(.0) - see this link. Since then only updated.

I recall installing Compiz last year and removed after some tests.

I was surprised to see the option "Ubuntu on Wayland" on the login screen (where you can change the desktop environment) some months ago. And yes, I was curious and started it.

It did not really work and I did not spend time in trying to find out how to make it work (I want to work with UM not with Ubuntu GNOME, therefor no need for it).

radax05 · 26 April 2025 13:06

I've started the PC with the only older kernel available 6.8.0-57-generic.
Now, with both kernel versions 6.8.0.57 and 6.8.0.58: "caja" starts correctly even with re-enabled "Marco" with compositor (build in:Xpresent).

lah7 · 26 April 2025 13:49

I noticed that too. Looks like this text only appears if the xwayland package is installed.

-  Display: x11 server: X.Org v: 21.1.11 driver: X: loaded: vmware
+  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:

To know for sure if it's running under an X11 session:

env | grep XDG_SESSION_TYPE

should output: XDG_SESSION_TYPE=x11

Strange. Not sure what's going on there. Best monitor and see if it crashes again.

As a guess, I wonder if some configuration/cache is corrupted in the home folder. Since you say log out/login and restarting does not help, but running as sudo & changing compositor works, maybe try creating a new user and log into that to try when/if it happens again?

Maybe try clearing the ~/.cache folder? (In case it's something like Mesa cache)

radax05 · 26 April 2025 13:51

mihai@MRSPC9:~$ env | grep XDG_SESSION_TYPE
XDG_SESSION_TYPE=x11

I'll delete the 2 mesa* folders in the ~/.cache folder once the issue occurs again.

Thank you all for your support.