[Bug 259058] mate update to 1.26 left system inoperable.

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 11 Oct 2021 03:21:15 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259058

            Bug ID: 259058
           Summary: mate update to 1.26 left system inoperable.
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: gnome@FreeBSD.org
          Reporter: rkoberman@gmail.com
             Flags: maintainer-feedback?(gnome@FreeBSD.org)
          Assignee: gnome@FreeBSD.org

Created attachment 228574
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=228574&action=edit
Message log output from mate upgrade

NOTE: this is not a problem with x11/mate as the metaport was unchanged. The
ports that x11/mate and x11/mate-base depend on were updated to 1.26. This
causes confusion and prevents my entering this as a problem with any specific
port. I have been unable to pin this down to a specific port. The install was
done with portmaster.

First, while installing the update to x11-fm/caja, mate-terminal crashed and
killed the upgrade at that point. The log showed caja deinstalled but the new
version was not installed. 

After that, I move to work in a vty and re-installed caja and re-installed caja
and the remaining ports. After restarting X, the panel did not appear and the
desktop was jumping 24 pixels up and down, though nothing was ever rendered in
the panel space. I tried switching to a vty, but nothing happened for a while.
Then after 10-15 seconds, it flipped to vty0. I switched back to X. mate-panel
had stopped restarting and the display had stabilized, but no panel. After a
few minutes the display froze. I logged in remotely and rebooted the system.
When I started X (startx), the same thing repeated.

After two attempts, I backed off the upgrades to 1.24 and the system returned
to normal.

-- 
You are receiving this mail because:
You are the assignee for the bug.