Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Oct 2021 03:21:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        gnome@FreeBSD.org
Subject:   maintainer-feedback requested: [Bug 259058] mate update to 1.26 left system inoperable.
Message-ID:  <bug-259058-6497-G9V8LUEBjv@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-259058-6497@https.bugs.freebsd.org/bugzilla/>
References:  <bug-259058-6497@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-gnome (Nobody)
<gnome@FreeBSD.org> for maintainer-feedback:
Bug 259058: mate update to 1.26 left system inoperable.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259058



--- Description ---
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 specif=
ic
port. I have been unable to pin this down to a specific port. The install w=
as
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 n=
ew
version was not installed.=20

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 t=
he
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 whi=
le.
Then after 10-15 seconds, it flipped to vty0. I switched back to X. mate-pa=
nel
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 return=
ed
to normal.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259058-6497-G9V8LUEBjv>