Mate 1.26

burdi01 · 08-08-2021, 11:56 AM

Slackware Current64 XFCE with MATE:Caja and friends.

With mate 1.26 from http://slackware.uk/msb/current/1.26/x86_64/ I see a *LOT* of these messages:

Code:

** caja(nnnn): CRITICAL **: hh:mm:ss:sss: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed
caja(nnnn): GLIB-GIO-CRITICAL **: hh:mm:ss:sss: g_file_get_url: assertion 'G_IS_FILE (file)' failed
caja(nnnn): GLIB-GObject-CRITICAL **: hh:mm:ss:sss: g_object-unref: assertion 'G_IS_OBJECT (object)' failed

I am not absolutely sure these failed assertions are harmless, but before diving deeper I would like to know whether or not I am the only one seeing them.

kgha · 08-08-2021, 12:45 PM

I'm on the MATE desktop and a fully upgraded -current (MATE-1.26 included).
I rarely use caja, but when running caja from terminal I get no messages/assertions whatsoever.

Daedra · 08-08-2021, 03:23 PM

I also upgraded to mate-1.26 on an up to date -current and I am not seeing any errors like that on my system. I didn't use the binaries I built the packages from source. It is still pretty brand new though, I just installed the packages yesterday. I am also experimenting with compiz-0.9.14.1 instead of the compiz-0.8 branch.

willysr · 08-08-2021, 10:09 PM

I'm having issue with MATE 1.26 with power management. When my monitor is idle, it stays showing blank screen, but everything else works fine. I don't know if anyone else having this issue as well

Skaendo · 08-09-2021, 12:45 AM

Building my own and running it all day. I haven't had any problems. Only thing is that I don't have any reboot/shutdown options for some reason.

kgha · 08-09-2021, 03:22 AM

Quote:

Originally Posted by willysr

I'm having issue with MATE 1.26 with power management. When my monitor is idle, it stays showing blank screen, but everything else works fine. I don't know if anyone else having this issue as well

Don't know if it's related, but after upgrading the MATE packages I encountered a locked screen after the screensaver had kicked in. Turned out that XFCEs power manager (and the hplip systray application) had been reactivated in MATE's startup applications preferences and apparently it takes precedence over the MATE power manager. Unchecked it, back to normal behaviour.

Skaendo · 08-09-2021, 03:29 AM

Quote:

Originally Posted by kgha

Don't know if it's related, but after upgrading the MATE packages I encountered a locked screen after the screensaver had kicked in. Turned out that XFCEs power manager (and the hplip systray application) had been reactivated in MATE's startup applications preferences and apparently it takes precedence over the MATE power manager. Unchecked it, back to normal behaviour.

Probably why I didn't have this issue. I remove Xfce after installing MATE/Cinnamon/whatever, and don't even install KDE. I keep HPLIP stock though.

burdi01 · 08-09-2021, 05:08 AM

Some more details:

The assertion messages this issue is about are given for each opening of a directory.

I boot my Slackware instances in level 3. After logging in I issue a "startx" command. The XFCE session is configured to come up with a caja and an xfce4-terminal window. After doing some work in caja I log out of the XFCE session. Back on the level 3 screen I then see a lot of messages. I know the messages I thus see with mate 1.24 are harmless because I have seen them for years while not experiencing any abnormalities. The assertion messages however are new with mate 1.26.

With the following test I can see the assertions in an xterm:
-- In the xterm verify that all caja instances are closed;
-- Issue a "caja" command;
-- In caja open a directory by double clicking on it: the assertion messages appear in the xterm;
-- Close the caja window.

Code:

burdi01@riposo:~/works$ ps -ef | grep -i caja
burdi01   3998  3854  0 10:42 pts/1    00:00:00 grep -i caja
burdi01@riposo:~/works$ caja &
[1] 4003
burdi01@riposo:~/works$ 
** (caja:4003): CRITICAL **: 10:43:34.579: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:4003): GLib-GIO-CRITICAL **: 10:43:34.579: g_file_get_uri: assertion 'G_IS_FILE (file)' failed

(caja:4003): GLib-GObject-CRITICAL **: 10:43:34.579: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

[1]+  Done                    caja
burdi01@riposo:~/works$

This test gives the same results for a non-root user as well as root.

I run XFCE for historical reasons, but I run caja because thunar does not support opening subdirectories in the same window.

willysr · 08-09-2021, 06:55 AM

Quote:

Originally Posted by kgha

Don't know if it's related, but after upgrading the MATE packages I encountered a locked screen after the screensaver had kicked in. Turned out that XFCEs power manager (and the hplip systray application) had been reactivated in MATE's startup applications preferences and apparently it takes precedence over the MATE power manager. Unchecked it, back to normal behaviour.

thanks, i will test this later

burdi01 · 08-09-2021, 11:33 AM

To dig deeper I downloaded and installed Alien's latest mate ISO (https://slackware.uk/people/alien-slacklive/latest/). As expected its mate 1.24 did not give the assertion messages.
I then applied my 12 1.26 packages: the assertion messages still occurred.
I then downloaded and applied all 52 mate 1.26 packages: the assertion messages no longer occur.
Researching ...

Jeebizz · 08-09-2021, 04:02 PM

Am I missing something though? The mate-desktop.org site still only shows 1.24 as the most current.

Skaendo · 08-09-2021, 04:20 PM

Quote:

Originally Posted by Jeebizz

Am I missing something though? The mate-desktop.org site still only shows 1.24 as the most current.

They just haven't announced yet. Probably testing still.

Jeebizz · 08-09-2021, 04:24 PM

Quote:

Originally Posted by Skaendo

They just haven't announced yet. Probably testing still.

Ah ok.

Skaendo · 08-09-2021, 07:53 PM

So I fixed my issue. Needed to take out consolekit stuff and add elogind stuff.

I might just make MATE my daily driver.

Skaendo · 08-10-2021, 01:21 AM

I tried to launch gparted from the menu with no results, so i tried from a terminal and got:

Code:

bash-5.1$ gparted
Error executing command as another user: Not authorized

then with pkexec:

Code:

bash-5.1$ pkexec gparted
==== AUTHENTICATING FOR org.gnome.gparted ====
Authentication is required to run the GParted Partition Editor as root
Authenticating as: root
Password: 
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized

Anyone know how to fix this? I'm pretty sure that it has to do with mate-polkit. Just not sure why. My own build ends up the exact same as Willy's with all the same files going in all the same places.