From nobody Mon Oct 11 03:21:15 2021 X-Original-To: gnome@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 280F917DF6D2 for ; Mon, 11 Oct 2021 03:21:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HSPG40WS1z4SMg for ; Mon, 11 Oct 2021 03:21:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E66AA19E1D for ; Mon, 11 Oct 2021 03:21:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 19B3LFIG062253 for ; Mon, 11 Oct 2021 03:21:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 19B3LFnr062252 for gnome@FreeBSD.org; Mon, 11 Oct 2021 03:21:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: maintainer-feedback requested: [Bug 259058] mate update to 1.26 left system inoperable. Date: Mon, 11 Oct 2021 03:21:15 +0000 X-Bugzilla-Type: request X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gnome@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: GNOME for FreeBSD -- porting and maintaining List-Archive: https://lists.freebsd.org/archives/freebsd-gnome List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-gnome@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N Bugzilla Automation has asked freebsd-gnome (Nobody) 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.