Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Apr 2022 11:01:59 -0600
From:      Pavel Timofeev <timp87@gmail.com>
To:        Neel Chauhan <nc@freebsd.org>
Cc:        ports-list freebsd <freebsd-ports@freebsd.org>
Subject:   Re: Recent quarterly GNOME upgrade broke my desktop
Message-ID:  <CAAoTqfs2c=9PU0q3T3qjewvTFg8kDae1gE1ke4=LCtB2%2BhVrxw@mail.gmail.com>
In-Reply-To: <CAAoTqfvkNAs%2BtB=Ab9_VSvXHiZi=VqRXajsscPwCMsqtR5XXyw@mail.gmail.com>
References:  <CAAoTqfvz_v5iCJ_O%2B3CxcWr7O3nm3YVajiGfpvavP8NXHwWeqg@mail.gmail.com> <32a2b55f48165989226f729c72152400@FreeBSD.org> <CAAoTqfvkNAs%2BtB=Ab9_VSvXHiZi=VqRXajsscPwCMsqtR5XXyw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--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 <timp87@gmail.com>:

>
>
> On Fri, Apr 8, 2022, 22:32 Neel Chauhan <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
>> > 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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">=D1=81=D0=B1, 9 =D0=B0=D0=BF=D1=80. 2=
022 =D0=B3. =D0=B2 07:34, Pavel Timofeev &lt;<a href=3D"mailto:timp87@gmail=
.com">timp87@gmail.com</a>&gt;:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Fri, Apr 8, 2022, 22:32 Neel Chauha=
n &lt;<a href=3D"mailto:nc@freebsd.org" target=3D"_blank">nc@freebsd.org</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,=
<br>
<br>
On 2022-04-07 16:28, Pavel Timofeev wrote:<br>
&gt; Hello, dear community<br>
&gt; <br>
&gt; I&#39;ve got non-working gnome-shell with the recent GNOME upgrade in =
the <br>
&gt; new 2022Q2 quarterly port branch.<br>
&gt; My laptop:<br>
&gt; [pavel.timofeev@carbon ~]$ freebsd-version -ku<br>
&gt; 13.1-RC1<br>
&gt; 13.1-RC1<br>
<br>
I help maintain GNOME on FreeBSD. I&#39;m sorry if it broke for you.<br>
<br>
&gt; I don&#39;t mention drm-fbsd13-kmod breakage due ABI changes (?) as I =
was <br>
&gt; able to recompile it against 13.1-RC1 locally and make it work (with <=
br>
&gt; some visual artefacts for some reason)<br>
<br>
I have no issues with GNOME 42, on both 14-CURRENT and 13.1-RC2, but <br>
then I&#39;m using the latest branch.<br>
<br>
&gt; But I can&#39;t make that new GNOME work and switched to XFCE for now.=
<br>
&gt; GDM starts fine, but once I login I get &quot;oops, something went wro=
ng&quot; <br>
&gt; message from gnome-shell.<br>
&gt; I disabled GDM autostart and got this in my .xinitrc:<br>
&gt; exec gnome-session --debug &gt; .xsession-errors 2&gt;&amp;1<br>
&gt; Then I started X with startx. The error file is attached.<br>
<br>
The errors I noticed:<br>
<br>
(gnome-shell:15744): Gjs-CRITICAL **: 09:23:03.928: JS ERROR: TypeError: <b=
r>
method GLib.TimeZone.get_offset: At least 1 argument required, but only <br=
>
0 passed<br>
_clocksChanged/&lt;@resource:///org/gnome/shell/ui/dateMenu.js:343:46<br>
_clocksChanged@resource:///org/gnome/shell/ui/dateMenu.js:342:25<br>
_init@resource:///org/gnome/shell/ui/dateMenu.js:309:14<br>
...<br>
<br>
=C2=A0 were something I fixed a while back.<br>
<br>
A few questions:<br>
<br>
1. Are you using x11/gnome-shell 41.4_2 (note the `_2` in the version)? <br=
>
This version fixes the GNOME shell.<br>
<br>
&gt; Found something similar on debian mail list, where they suggested <br>
&gt; upgrading to gnome-shell 42.<br>
&gt; <a href=3D"https://www.mail-archive.com/debian-bugs-dist@lists.debian.=
org/msg1849602.html" rel=3D"noreferrer noreferrer" target=3D"_blank">https:=
//www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1849602.html</a=
><br>
&gt; The reporter says it helped.<br>
&gt; Not sure if I get the same error.<br>
&gt; <br>
&gt; Am I the only one who experiences this issue with GNOME?<br>
<br>
You could try updating packages again, or switching to &quot;latest&quot;. =
It&#39;s <br>
only very recently that GNOME packages unbroke.<br>
<br>
I am using 13.1-RC2 on my laptop with GNOME 42 (really a 41/42 hybrid as <b=
r>
of now).<br>
<br>
-Neel (nc@)<br></blockquote></div></div><div dir=3D"auto"><br></div><div di=
r=3D"auto"><br></div><div dir=3D"auto">Yes, I have gnome-shell-41.4_2 insta=
lled on my system.</div><div dir=3D"auto">Switching to latest doesn&#39;t s=
how any gnome-related pkg to upgrade.</div></div></blockquote><div><br></di=
v><div><br></div><div>Finally, I have got working GNOME today. There has be=
en gnome-related package update in the latest pkg branch where gnome-shell =
upgraded to version 42.</div></div></div>

--000000000000ecd7a205dd412f7d--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAoTqfs2c=9PU0q3T3qjewvTFg8kDae1gE1ke4=LCtB2%2BhVrxw>