Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caja latest git produces xsession errors again #1757

Open
duck7000 opened this issue Dec 19, 2023 · 3 comments
Open

Caja latest git produces xsession errors again #1757

duck7000 opened this issue Dec 19, 2023 · 3 comments

Comments

@duck7000
Copy link

duck7000 commented Dec 19, 2023

Expected behaviour

No errors/warnings in xsession

Actual behaviour

There are multiple entrys of the same error/warning

Steps to reproduce the behaviour

Install the latest git version
start caja
open xsession with pluma
Those errors/warnings are displayed multiple times
(caja:810): Gtk-CRITICAL **: 22:31:01.127: _gtk_css_image_get_concrete_size: assertion 'default_width > 0' failed

(caja:810): Gtk-CRITICAL **: 22:31:01.127: _gtk_css_image_get_surface: assertion 'surface_height > 0' failed

Those criticials are also there for pluma, multiple times (i understand that this is not the place to mention that but you should know)

Next to above multiple errors/warnings there are more errors/warnings that happens once:
(caja:804): Gtk-WARNING **: 19:33:35.913: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client

(caja:804): GLib-GObject-CRITICAL **: 19:33:36.048: ../glib/gobject/gsignal.c:2522: signal 'middle_click' is invalid for instance '0x564a946a3d50' of type 'FMDesktopIconView'

MATE general version

1.26.2
Glibc version 2.38-7

Package version

latest git 19-12-2023

Linux Distribution

Manjaro mate

Link to bugreport of your Distribution (requirement)

latest git version is not available in Manjaro Mate, i installed it manually to get rit of previous xsession errors that you have fixed. so there is no point to make a bug report there

@lukefromdc
Copy link
Member

The first two warnngs I've never seen on my system, something must be different there.

(caja:804): Gtk-WARNING **: 19:33:35.913: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
looks like caja is trying to start a new instance rather than connect to the existing caja process at some point.

The last one I saw somehow coming up from mate-power-manager instead of caja (though the code in the warning is otherwise the same), no idea why.

@BioInfoChris
Copy link

Hi,
I have different errors but plenty of caja errors in my xsession-errors file, like:

** (caja:2800739): CRITICAL **: 17:59:13.336: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:13.337: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:13.337: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 17:59:14.431: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:14.431: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:14.431: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 17:59:23.318: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:23.318: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:23.318: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 17:59:27.988: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:27.988: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:27.989: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 17:59:30.113: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:30.113: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:30.114: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 17:59:35.227: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:35.227: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:35.228: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 17:59:36.466: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:36.467: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:36.467: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 17:59:38.119: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 17:59:38.119: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 17:59:38.119: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

** (caja:2800739): CRITICAL **: 18:05:57.906: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:2800739): GLib-GIO-CRITICAL **: 18:05:57.906: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:2800739): GLib-GObject-CRITICAL **: 18:05:57.906: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

The file takes up to 95 Go (not all caja related) so it starts to be annoying. Is it a verbosity issue?

Linux distribution : DEBIAN 12
Linux kernel : 6.1.0-16-amd64x86_64
MATE : 1.26
Caja : 1.26.1

We run in GUI using vncserver only.

@lukefromdc
Copy link
Member

That looks like caja isn't finding files (or is finding them late) over vncserver. Such sessions are entirely outside my experience so I will have to leave this for other members of the team with experience there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants