From nobody Fri Apr 22 17:01:59 2022 X-Original-To: freebsd-ports@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 A73DC1989F0C for ; Fri, 22 Apr 2022 17:02:12 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KlLLC5tH5z4lwH; Fri, 22 Apr 2022 17:02:11 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by mail-ej1-x633.google.com with SMTP id l7so17626048ejn.2; Fri, 22 Apr 2022 10:02:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q3kx/fCLdHerpGrBSa7xlCjX0uzHPEfGv0yGPJRh3m0=; b=H1EcEGTc3ii6u9iu6q8Izqo3oHTWD7y9cqEU2oVV2oK3Kyi2TUE0wRgQMiqV62uQZ3 +KMf6KD+AQIoxZpj7RGw99c0sFp/heCEkya6Z1VmAlLVFD4Fll3Bt5/vi8DjAle4AK/n teTnHifqFQ8fFLC9BHAElL1k2ywKGzyCcgYU0MV6QgU781pQ889Gbhs04ipjcFgLvrEE PI9Ib9F1LqO9ja5IsDgjVJnnq6e5xQIhGnnFlaG9wIpREgXig1obeEDxpWyhB3BzCqoE jWe58zx6WpJVPYjCt0vow4UDIlA3CS8BRBzQU9GM2ewNrIBmBx28Vv0HkGnJNRH0cDsM PoIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q3kx/fCLdHerpGrBSa7xlCjX0uzHPEfGv0yGPJRh3m0=; b=qQna7myMiEm+BuWWA17zeRYg3jaOznZ3sV2K3E+6kl5xWl6/MPxk60NEbjogS79uAI cfbpgK6ByazDslIG88ZL+8PAnWo5pupy+0ORUfoVEEqJrNWn0GYJLZuaqtwEVMCk1r+2 qmazoCABht49pYUdV3n6kKlNf4mBFi1ZEtoH8NcM1zuGTvhrSjKmSe2qhOhSTcig4BDb mjSCeR/bCNQLEeZA6njvzs8BnWaOqBtPIbDQyxfgzyDTyr2Ov6kCMPgpcUJntuL3OnnX cjdmV58xJF5ZbmOw6PQ4Yp9SoUHiSEAQUGMKFE6UBTUp3tdWrbWp+hk2HT1y1wchDYsk BkBQ== X-Gm-Message-State: AOAM530jr8cMdbguaAShY5kCWTZbY8VfGl0f+gsvpjBGaMHog0sX50si MDTeZWpgmIEXmQpacztUCW/QsHTj1wTvq1+9MUN8fG5Z X-Google-Smtp-Source: ABdhPJwZX+S2Zth3EOEcnpJPoIMOyNFcJkboTNF2E2esCKCJmNuFuWwFYmUSaRkZAN8evIw8r2rY9BixRlbj2acWazY= X-Received: by 2002:a17:907:3e27:b0:6f3:6a35:ee58 with SMTP id hp39-20020a1709073e2700b006f36a35ee58mr1243191ejc.480.1650646930212; Fri, 22 Apr 2022 10:02:10 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <32a2b55f48165989226f729c72152400@FreeBSD.org> In-Reply-To: From: Pavel Timofeev Date: Fri, 22 Apr 2022 11:01:59 -0600 Message-ID: Subject: Re: Recent quarterly GNOME upgrade broke my desktop To: Neel Chauhan Cc: ports-list freebsd Content-Type: multipart/alternative; boundary="000000000000ecd7a205dd412f7d" X-Rspamd-Queue-Id: 4KlLLC5tH5z4lwH X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=H1EcEGTc; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of timp87@gmail.com designates 2a00:1450:4864:20::633 as permitted sender) smtp.mailfrom=timp87@gmail.com X-Spamd-Result: default: False [0.01 / 15.00]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.991]; NEURAL_SPAM_MEDIUM(1.00)[0.999]; NEURAL_SPAM_SHORT(1.00)[1.000]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::633:from]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MLMMJ_DEST(0.00)[freebsd-ports]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N --000000000000ecd7a205dd412f7d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =D1=81=D0=B1, 9 =D0=B0=D0=BF=D1=80. 2022 =D0=B3. =D0=B2 07:34, Pavel Timofe= ev : > > > On Fri, Apr 8, 2022, 22:32 Neel Chauhan wrote: > >> Hi, >> >> On 2022-04-07 16:28, Pavel Timofeev wrote: >> > Hello, dear community >> > >> > I've got non-working gnome-shell with the recent GNOME upgrade in the >> > new 2022Q2 quarterly port branch. >> > My laptop: >> > [pavel.timofeev@carbon ~]$ freebsd-version -ku >> > 13.1-RC1 >> > 13.1-RC1 >> >> I help maintain GNOME on FreeBSD. I'm sorry if it broke for you. >> >> > I don't mention drm-fbsd13-kmod breakage due ABI changes (?) as I was >> > able to recompile it against 13.1-RC1 locally and make it work (with >> > some visual artefacts for some reason) >> >> I have no issues with GNOME 42, on both 14-CURRENT and 13.1-RC2, but >> then I'm using the latest branch. >> >> > But I can't make that new GNOME work and switched to XFCE for now. >> > GDM starts fine, but once I login I get "oops, something went wrong" >> > message from gnome-shell. >> > I disabled GDM autostart and got this in my .xinitrc: >> > exec gnome-session --debug > .xsession-errors 2>&1 >> > Then I started X with startx. The error file is attached. >> >> The errors I noticed: >> >> (gnome-shell:15744): Gjs-CRITICAL **: 09:23:03.928: JS ERROR: TypeError: >> method GLib.TimeZone.get_offset: At least 1 argument required, but only >> 0 passed >> _clocksChanged/<@resource:///org/gnome/shell/ui/dateMenu.js:343:46 >> _clocksChanged@resource:///org/gnome/shell/ui/dateMenu.js:342:25 >> _init@resource:///org/gnome/shell/ui/dateMenu.js:309:14 >> ... >> >> were something I fixed a while back. >> >> A few questions: >> >> 1. Are you using x11/gnome-shell 41.4_2 (note the `_2` in the version)? >> This version fixes the GNOME shell. >> >> > Found something similar on debian mail list, where they suggested >> > upgrading to gnome-shell 42. >> > >> https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg184960= 2.html >> > The reporter says it helped. >> > Not sure if I get the same error. >> > >> > Am I the only one who experiences this issue with GNOME? >> >> You could try updating packages again, or switching to "latest". It's >> only very recently that GNOME packages unbroke. >> >> I am using 13.1-RC2 on my laptop with GNOME 42 (really a 41/42 hybrid as >> of now). >> >> -Neel (nc@) >> > > > Yes, I have gnome-shell-41.4_2 installed on my system. > Switching to latest doesn't show any gnome-related pkg to upgrade. > Finally, I have got working GNOME today. There has been gnome-related package update in the latest pkg branch where gnome-shell upgraded to version 42. --000000000000ecd7a205dd412f7d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
=D1=81=D0=B1, 9 =D0=B0=D0=BF=D1=80. 2= 022 =D0=B3. =D0=B2 07:34, Pavel Timofeev <timp87@gmail.com>:


<= div dir=3D"ltr" class=3D"gmail_attr">On Fri, Apr 8, 2022, 22:32 Neel Chauha= n <nc@freebsd.org> wrote:
Hi,=

On 2022-04-07 16:28, Pavel Timofeev wrote:
> Hello, dear community
>
> I've got non-working gnome-shell with the recent GNOME upgrade in = the
> new 2022Q2 quarterly port branch.
> My laptop:
> [pavel.timofeev@carbon ~]$ freebsd-version -ku
> 13.1-RC1
> 13.1-RC1

I help maintain GNOME on FreeBSD. I'm sorry if it broke for you.

> I don't mention drm-fbsd13-kmod breakage due ABI changes (?) as I = was
> able to recompile it against 13.1-RC1 locally and make it work (with <= br> > some visual artefacts for some reason)

I have no issues with GNOME 42, on both 14-CURRENT and 13.1-RC2, but
then I'm using the latest branch.

> But I can't make that new GNOME work and switched to XFCE for now.=
> GDM starts fine, but once I login I get "oops, something went wro= ng"
> message from gnome-shell.
> I disabled GDM autostart and got this in my .xinitrc:
> exec gnome-session --debug > .xsession-errors 2>&1
> Then I started X with startx. The error file is attached.

The errors I noticed:

(gnome-shell:15744): Gjs-CRITICAL **: 09:23:03.928: JS ERROR: TypeError: method GLib.TimeZone.get_offset: At least 1 argument required, but only 0 passed
_clocksChanged/<@resource:///org/gnome/shell/ui/dateMenu.js:343:46
_clocksChanged@resource:///org/gnome/shell/ui/dateMenu.js:342:25
_init@resource:///org/gnome/shell/ui/dateMenu.js:309:14
...

=C2=A0 were something I fixed a while back.

A few questions:

1. Are you using x11/gnome-shell 41.4_2 (note the `_2` in the version)? This version fixes the GNOME shell.

> Found something similar on debian mail list, where they suggested
> upgrading to gnome-shell 42.
> https:= //www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1849602.html
> The reporter says it helped.
> Not sure if I get the same error.
>
> Am I the only one who experiences this issue with GNOME?

You could try updating packages again, or switching to "latest". = It's
only very recently that GNOME packages unbroke.

I am using 13.1-RC2 on my laptop with GNOME 42 (really a 41/42 hybrid as of now).

-Neel (nc@)


--000000000000ecd7a205dd412f7d--