Caja crash in folder that i rsync over from old ubuntu mate 22.04

Support & Help Requests
,
#1

This is a pretty new fresh install. I feel like the problems are related:
Let me describe.

The problem only occur in the 2 folders I moved over originally started from old computer.
I would open the location through Caja. And Caja would crash (close without warning).

I found this thread. Caja 1.26.0 -- frequent crashing on UbuntuMATE 22.04 - #2 by ricmarques
And I installed folder-color and restarted. thinking it's fixed

I could still cp files in and out of these folder.

The files in these folder included some jpeg images. So I tried opening them by double clicking. Crash. I tried command line eom file.jpg crashed.

.xsession-error file

RuntimeError: object at 0x7ae3aa254600 of type FolderColorMenu is not initialized

** (caja:2521): CRITICAL **: 23:33:24.678: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2521): GLib-GIO-CRITICAL **: 23:33:24.678: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(mate-power-preferences:3463): PowerManager-WARNING **: 23:33:51.468: Failed to get session for pid 3463: The name org.freedesktop.ConsoleKit was not provided by any .service files
[3631:0416/233556.240202:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
[3631:0416/233558.390908:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[3631:0416/233558.434535:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[3631:0416/233558.792011:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[3631:0416/233558.792093:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[3631:0416/233558.792121:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[3631:0416/233558.792143:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[3631:0416/233558.801070:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[3631:0416/233558.827437:ERROR:check.cc(297)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[main 2024-04-17T06:36:00.831Z] [UtilityProcess id: 1, type: fileWatcher, pid: 3785]: crashed with code 15 and reason 'killed'
Warning: terminator_CreateInstance: Failed to CreateInstance in ICD 0.  Skipping ICD.

Where have I screw things up? Please help :slight_smile:

1 Like
#2

Welcome @mateuser99940 to the community!

#3

It went away for a while and it came back. I looked at dmesg

[Apr20 18:36] caja[73858]: segfault at 7fff99bbbff8 ip 000072346bcdfbaa sp 00007fff99bbc000 error 6 in libgio-2.0.so.0.7200.4[72346bbd6000+111000] likely on CPU 7 (core 3, socket 0)
[  +0.000011] Code: c3 0f 1f 80 00 00 00 00 48 83 c4 48 31 c0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 b8 01 00 00 00 eb d2 f3 0f 1e fa 41 57 41 56 41 55 <41> 54 55 53 48 83 ec 18 4c 8b 25 3f 5a 09 00 49 8b 04 24 48 85 c0
[Apr20 18:40] caja[91255]: segfault at 7ffed3ec6ff8 ip 00007c2b3b1e6c2d sp 00007ffed3ec7000 error 6 in libgio-2.0.so.0.7200.4[7c2b3b0dd000+111000] likely on CPU 4 (core 2, socket 0)
[  +0.000012] Code: 8d 75 ff 41 39 de 7c 34 8b 44 24 04 46 8d 2c 33 48 89 ee 41 d1 fd 46 8d 24 e8 41 8d 44 24 04 41 8b 3c 07 0f cf 89 ff 4c 01 ff <e8> ee 9d ef ff 85 c0 79 ca 41 8d 5d 01 41 39 de 7d cc 48 83 44 24

Not particularly helpful kernel error messages.

** (caja:73858): CRITICAL **: 16:45:16.673: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:73858): GLib-GIO-CRITICAL **: 16:45:16.673: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(caja:91255): Gtk-WARNING **: 16:45:27.837: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
RuntimeError: object at 0x7c2b3402c540 of type FolderColorMenu is not initialized
RuntimeError: object at 0x7c2b3402c540 of type FolderColorMenu is not initialized
RuntimeError: object at 0x7c2b3402c540 of type FolderColorMenu is not initialized

** (caja:91255): CRITICAL **: 16:48:50.595: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:91255): GLib-GIO-CRITICAL **: 16:48:50.595: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(caja:91496): Gtk-WARNING **: 16:48:58.182: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
RuntimeError: object at 0x7c6b5c16a6c0 of type FolderColorMenu is not initialized
RuntimeError: object at 0x7c6b5c16a6c0 of type FolderColorMenu is not initialized
RuntimeError: object at 0x7c6b5c16a6c0 of type FolderColorMenu is not initialized

** (caja:91496): CRITICAL **: 16:52:15.367: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:91496): GLib-GIO-CRITICAL **: 16:52:15.367: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(caja:91818): Gtk-WARNING **: 16:52:32.406: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
RuntimeError: object at 0x7b4e898e0dc0 of type FolderColorMenu is not initialized
RuntimeError: object at 0x7b4e898e0dc0 of type FolderColorMenu is not initialized
RuntimeError: object at 0x7b4e898e0dc0 of type FolderColorMenu is not initialized

** (caja:91818): CRITICAL **: 16:53:28.219: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:91818): GLib-GIO-CRITICAL **: 16:53:28.219: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(caja:91919): Gtk-WARNING **: 16:53:35.984: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
RuntimeError: object at 0x740c052c9b40 of type FolderColorMenu is not initialized
RuntimeError: object at 0x740c052c9b40 of type FolderColorMenu is not initialized
RuntimeError: object at 0x740c052c9b40 of type FolderColorMenu is not initialized

** (caja:91919): CRITICAL **: 16:54:32.888: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:91919): GLib-GIO-CRITICAL **: 16:54:32.888: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(caja:92035): Gtk-WARNING **: 16:54:38.521: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
RuntimeError: object at 0x7fe1625d5e00 of type FolderColorMenu is not initialized

Does anyone have any suggestions for me?

1 Like
#4

Hi, @mateuser99940 :slight_smile:

(Usual disclaimer: please note that I'm just another Forum user here. I'm NOT a Ubuntu or Ubuntu MATE developer).

Besides all the the troubleshooting that you correctly have already done regarding "Caja" (MATE Desktop's native File Manager / File Browser), I would also look at the /var/crash directory.

Do you have any files with extension .crash in that /var/crash folder? If so, what are their filenames? I also suggest that you open those ".crash" files (with a text editor) and see their content. Usually, the more informative lines (at least for me) in those .crash files are the lines that begin with:

  • ProblemType: (usually that line says ProblemType: Crash)
  • ExecutablePath: (which has the full path for the program that crashed)
  • ProcCmdline: (which has the line that was was used to start that program)
  • Title: (a very informative line when it exists but, unfortunately, in some ".crash" files that "Title:" line does not exist)
  • Package: (the name and version of the package of the program that crashed)

If you're interested, you may also want to take a look at the "StacktraceTop:", "Stacktrace:", "ThreadStacktrace:", "XsessionErrors:" and "JournalErrors:" sections also in that ".crash" file, but please be aware that some of those sections may contain a LOT of information and that some of that information, in some cases, you may NOT want to disclose in a public forum.

I hope this helps. :slight_smile:

2 Likes