Re: Recent quarterly GNOME upgrade broke my desktop

сб, 9 апр. 2022 г. в 07:34, Pavel Timofeev <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/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@)
>>
>
>
> 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.