Created attachment 1784489 [details]
File: backtrace

Created attachment 1784490 [details]
File: core_backtrace

Created attachment 1784491 [details]
File: cpuinfo

Created attachment 1784492 [details]
File: dso_list

Created attachment 1784493 [details]
File: environ

Created attachment 1784494 [details]
File: limits

Created attachment 1784495 [details]
File: maps

Created attachment 1784496 [details]
File: mountinfo

Created attachment 1784497 [details]
File: open_fds

Created attachment 1784498 [details]
File: proc_pid_status

It seems the gsettings schema weren't recompiled after the package was installed. That should happen automatically, but under unknown circumstances, it seems not to work. Then gnome-terminal crashes when accessing the setting. g-t upstream would like to make sure this never happens by embedding the compiled schema, but is lacking API in glib [https://gitlab.gnome.org/GNOME/glib/-/issues/499] to do so.

The backtrace mentions a "context-info" GSettings key, but I don't see anything like that in the code. Is that just garbage because the schema wasn't compiled? Or something else?

Similar problem has been detected:

I right clicked in terminal window. This causes all open terminal windows to crash.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: g_settings_schema_get_value
executable:     /usr/libexec/gnome-terminal-server
journald_cursor: s=b823acbfa4e943268a55a6e6acfe54ee;i=2334;b=d97e68f90105401c9d79313d93a4848a;m=7d600e512;t=5c2a928b4fd9c;x=b045ad69c6ad8f8a
kernel:         5.11.19-300.fc34.x86_64
package:        gnome-terminal-3.38.3-1.fc34
reason:         gnome-terminal-server killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:


dnf upgrade -y

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-0.slice/user/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: g_settings_schema_get_value
executable:     /usr/libexec/gnome-terminal-server
journald_cursor: s=44dabe8563eb4addb8a9acc6dc81165b;i=7301;b=5bba45a66c714bc5bc1756066b696ca6;m=8c3df8ffc;t=5c2b1c4fe19dc;x=8e121f6d8779b63b
kernel:         5.11.20-300.fc34.x86_64
package:        gnome-terminal-3.38.3-1.fc34
reason:         gnome-terminal-server killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

*** Bug 1962898 has been marked as a duplicate of this bug. ***

Apologies for the duplicate report. I should note that I only noticed the issue after upgrading to 3.40.1-1. I have been unable to reproduce it since downgrading to 3.38.3-1 and then upgrading back to 3.40.1-1 (unsure if it's transient or fixed itself permanently).

I've just removed 3.38 and everything goes well.

https://ibb.co/HT3jq8P

Now context menu doesn't kill the window.

(In reply to Debarshi Ray from comment #12)
> The backtrace mentions a "context-info" GSettings key, but I don't see
> anything like that in the code. Is that just garbage because the schema
> wasn't compiled? Or something else?

That's an existing key:

org.gnome.Terminal.gschema.xml:    <key name="context-info" type="as">
terminal-schemas.h:#define TERMINAL_SETTING_CONTEXT_INFO_KEY               "context-info"

And yes, the problem is that somehow the upgrade failed to recompile the gsettings schemas.

(In reply to Christian Persch from comment #18)
> (In reply to Debarshi Ray from comment #12)
> > The backtrace mentions a "context-info" GSettings key, but I don't see
> > anything like that in the code. Is that just garbage because the schema
> > wasn't compiled? Or something else?
> 
> That's an existing key:
> 
> org.gnome.Terminal.gschema.xml:    <key name="context-info" type="as">
> terminal-schemas.h:#define TERMINAL_SETTING_CONTEXT_INFO_KEY              
> "context-info"

Ok, I see it now.

The thing is that the "context-info" GSettings key was only introduced in GNOME Terminal 3.40.x, while I see it in backtraces generated by GNOME Terminal 3.38.x (eg., this bug itself). Which is why I was looking at the gnome-3-38 branch.

> And yes, the problem is that somehow the upgrade failed to recompile the
> gsettings schemas.

I wonder if the version mismatch is a hint as to what might be going on? Could it be a case of online updates gone wrong? Maybe GNOME Terminal was started in the middle of a DNF operation and the right-click happened before the new schema got compiled?

Does the crash keep happening repeatedly? Or does it crash once, and then if you restart GNOME Terminal and use right-click to bring up the context menu, it doesn't crash anymore?

*** Bug 1963337 has been marked as a duplicate of this bug. ***

(In reply to Debarshi Ray from comment #20)
> Does the crash keep happening repeatedly? Or does it crash once, and then if
> you restart GNOME Terminal and use right-click to bring up the context menu,
> it doesn't crash anymore?

I'm afraid that I can't reproduce the bug since down/upgrading gnome-terminal, but I'm pretty sure that it crashed every time I re-opened and right-clicked on it before I did that, not just once.

*** Bug 1963961 has been marked as a duplicate of this bug. ***

*** Bug 1964046 has been marked as a duplicate of this bug. ***

(In reply to Debarshi Ray from comment #20)
> Does the crash keep happening repeatedly? Or does it crash once, and then if
> you restart GNOME Terminal and use right-click to bring up the context menu,
> it doesn't crash anymore?

I crashes repeatedly, every time on right-click. Restarting terminal, same issue again. (You do not need to type or call anything before rightclick.) And if right-clicking all terminals (at least from the same user) crash not only the current one.

This issue is also on https://retrace.fedoraproject.org/faf/reports/156482/ .

The issue occured
434 times with 0:3.40.1-1.fc34
328 times with 0:3.38.3-1.fc34
 15 times with 0:3.38.1-3.fc34

I do not understand what "related packages" mean, and why librsvg2.50 is showing up .

Created attachment 1786560 [details]
dnf list gnome-terminal

output of "dnf list gnome-terminal" it shows 3.38.3 AND 3.40.1 (sorry I can't right-click for copying, see this bug-description) ;-)

I solved the issue using

sudo dnf remove gnome-terminal-3.38* 

(3.40 was already installed)

*** Bug 1964056 has been marked as a duplicate of this bug. ***

(In reply to Johannes Kalliauer from comment #25)
> (In reply to Debarshi Ray from comment #20)
> > Does the crash keep happening repeatedly? Or does it crash once, and then if
> > you restart GNOME Terminal and use right-click to bring up the context menu,
> > it doesn't crash anymore?
> 
> I crashes repeatedly, every time on right-click. Restarting terminal, same
> issue again. (You do not need to type or call anything before rightclick.)
> And if right-clicking all terminals (at least from the same user) crash not
> only the current one.

Interesting.

(In reply to Johannes Kalliauer from comment #28)
> I solved the issue using
> 
> sudo dnf remove gnome-terminal-3.38* 
> 
> (3.40 was already installed)

You mean, you had both gnome-terminal-3.38.x and gnome-terminal-3.40.x RPMs installed at the same time? That's not supposed to happen under normal circumstances.

Do you remember doing something with DNF (say, an installation or an update) that failed midway?

> You mean, you had both gnome-terminal-3.38.x and gnome-terminal-3.40.x RPMs installed at the same time?
Yes see the screenshot: https://bugzilla.redhat.com/attachment.cgi?id=1786560 (copy&paste did not work because of this issue)

dnf list gnome-terminal returned
Installierte Packete [german for installe packages]
gnome-terminal.x86_64   3.38.3-1.fc34   @updates
gnome-terminal.x86_64   3.40.1-1.fc34   @updates

> Do you remember doing something with DNF (say, an installation or an update) that failed midway?

I can't remember. (I think I had a chrash somewhen in the last days, I do not know when nor why, might not be related to this issue.)

The bug occurred the first time on the 19.May I think in the Morning (~9:00CEST=07:00UTC) one day after the first big peak in https://retrace.fedoraproject.org/faf/reports/156482/

Commands which were typed in the terminal which crashed seems not to be saved in .bash_history (because some commands between 19.May and 24.May are missing)

The last dnf-commands in .bash_history are: (the 19.May should be around line 830: of .bash_history)
```
2:sudo dnf install python3-pillow-tk
14:sudo dnf install libvpx
15:sudo dnf install libvpx opus
33:sudo dnf install libvpx opus
34:sudo dnf list libvpx opus
49:sudo dnf install libvpx opus
104:sudo dnf upgrade
121:dnf list inkscape
217:sudo dnf list batik*
218:sudo dnf list librsvg*
219:sudo dnf list imag*
220:sudo dnf list google-noto-\*
221:sudo dnf install google-noto-\*
306:sudo dnf upgrade
310:sudo dnf upgrade
311:sudo dnf list wesnot*
312:sudo dnf remove wesnoth-data
313:sudo dnf upgrade
314:sudo dnf upgrade --refresh
316:sudo dnf install dnf-plugin-system-upgrade
317:sudo dnf install dnf-plugin-system-upgrade --best
318:dnf system-upgrade download --refresh --releasever=34
319:sudo dnf system-upgrade download --refresh --releasever=34
320:sudo dnf --refresh upgrade
321:sudo dnf system-upgrade download --refresh --releasever=34
322:sudo dnf --refresh upgrade
323:sudo dnf system-upgrade download --refresh --releasever=34 --best
324:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing
325:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing &> upgrade34.txt
327:sudo dnf upgrade --refresh
328:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing
329:dnf system-upgrade reboot
330:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing --best
331:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing --best --skip-broken
332:sudo dnf remove gwe
333:sudo dnf remove iptables
334:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing
335:sudo dnf list gwe iptables openjfx
336:sudo dnf list gwe iptables openjfx widelands
337:sudo dnf remove gwe iptables openjfx
338:sudo dnf remove iptables
339:sudo dnf remove openjfx
340:sudo dnf remove gwe openjfx
341:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing
342:sudo dnf list gwe iptables openjfx widelands
343:sudo dnf remove gwe widelands
344:sudo dnf system-upgrade download --refresh --releasever=34 --allowerasing
345:dnf system-upgrade reboot
346:sudo dnf system-upgrade reboot
347:sudo dnf list gwe iptables openjfx widelands
348:sudo dnf upgrade --refresh
349:sudo dnf upgrade --refresh --best --allowerasing
350:sudo dnf upgrade --refresh
396:sudo dnf upgrade
402:sudo dnf upgrade
403:sudo dnf upgrade
417:sudo dnf upgrade
428:sudo dnf upgrade
429:sudo dnf list widelands
430:sudo dnf remove widelands
431:sudo dnf list widelands
432:sudo dnf upgrade
433:sudo dnf install widelands
434:sudo dnf upgrade
435:dnf list gwe iptables openjfx widelands
436:sudo dnf install iptables
437:sudo dnf upgrade
438:sudo dnf uprade
439:sudo dnf upgrade
490:sudo dnf upgrade
491:sudo dnf upgrade#
492:sudo dnf upgrade
496:sudo dnf upgrade
577:dnf install libcroco
578:sudo dnf install libcroco
579:sudo dnf install mingw32-libcroco-static
580:sudo dnf list mingw64-libcroco-static-0.6.12-10.fc34.noarch
581:sudo dnf install mingw64-libcroco-static-0.6.12-10.fc34.noarch
583:dnf list librsvg
584:dnf list rsvg-convert
585:dnf list librsvg2
604:sudo dnf list libcroco*
605:sudo dnf list *libcroco*
606:sudo dnf list mingw64-libcroco
607:sudo dnf list mingw64-libcroco-static-0.6.12-10.fc34.noarch
608:sudo dnf list mingw64-libcroco-static
609:sudo dnf list *libcroco*
644:dnf list libcroco
650:sudo dnf upgrade --refresh
673:dnf list libcroco
679:dnf list libcroco
683:dnf list libcroco
801:sudo dnf install libresv*
802:sudo dnf install resv*
803:sudo dnf list *resvg*
804:sudo dnf list *res*
805:sudo dnf list *resv*
830:sudo dnf upgrade
837:sudo dnf upgrade
838:sudo dnf upgrade --refresh
861:sudo dnf upgrade
862:sudo dnf upgrade --refresh
865:sudo dnf install jitsi
866:sudo dnf install jitsi --skip-broken
867:sudo dnf install libjawt
868:sudo dnf install java-11-openjdk-*
874:sudo dnf install jitsi
875:sudo dnf install jitsi-meet
876:sudo dnf install jitsi-*
877:sudo dnf list jitsi-*
878:sudo dnf list jicofo
879:sudo dnf list jicgasi
880:sudo dnf list jigasi
881:sudo dnf list jibri
888:sudo dnf upgrade
889:sudo dnf upgrade --refresh
890:sudo dnf list libselinux-debuginfo
891:sudo dnf list *-debuginfo
892:sudo dnf list docker-ce*
893:sudo dnf list docker*
894:sudo dnf upgrade --refresh
895:sudo dnf upgrade
896:sudo dnf --help
897:sudo dnf upgrade --refresh --skip-broken
898:sudo dnf --help
899:sudo dnf upgrade --refresh --skip-broken --allowerasing
900:sudo dnf --help 
901:sudo dnf upgrade --refresh --skip-broken --allowerasing --best
902:sudo dnf upgrade --refresh --skip-broken --allowerasing --nobest
903:sudo dnf remove libxml2-devel
904:sudo dnf remove libxml2-devel.i686
905:sudo dnf upgrade --refresh --skip-broken --allowerasing
906:sudo dnf list freedesktop*
907:sudo dnf list *freedesktop*
908:sudo dnf list
909:sudo dnf list installed
910:sudo dnf list installed >> dnf.txt
911:sudo dnf upgrade --refresh --skip-broken --allowerasing
912:sudo dnf upgrade --refresh
914:sudo dnf list docker*
915:sudo dnf install docker-ce
916:sudo dnf install docker-ce --allowerasing
917:sudo dnf list docker-ce*
918:sudo dnf upgrade --refresh
919:sudo dnf list docker-ce*
920:sudo dnf upgrade --refresh --skip-broken --allowerasing
921:sudo dnf -y install dnf-plugins-core
922:sudo dnf config-manager     --add-repo     https://download.docker.com/linux/fedora/docker-ce.repo
923:sudo dnf upgrade --refresh --skip-broken --allowerasing
924:sudo dnf install docker-ce docker-ce-cli containerd.io
925:dnf list docker-ce  --showduplicates | sort -r
930:sudo dnf install lz4-libs-debuginfo
932:dnf debuginfo-install docker-ce
933:sudo dnf debuginfo-install docker-ce
934:sudo dnf debuginfo-install lz4-libs
935:sudo dnf list *-debuginfo*
936:sudo dnf list *-debuginfo
937:sudo dnf debuginfo-install *
938:sudo dnf debuginfo-install 
939:sudo dnf debuginfo-install l*
940:sudo dnf debuginfo-install *-*
941:dnf debuginfo-install *
942:sudo dnf debuginfo-install *
943:sudo dnf debuginfo-install * --allowerasing --skip-broken
944:sudo dnf debuginfo-install libX* --allowerasing --skip-broken
945:sudo dnf debuginfo-install libXext --allowerasing --skip-broken
946:sudo dnf debuginfo-install docker-ce --allowerasing --skip-broken
947:sudo dnf install libXext
948:sudo dnf install libXext*
949:sudo dnf list *-debuginfo
954:sudo dnf list gnome-terminal
955:dnf list gnome-terminal
958:sudo dnf install gnome-terminal
959:sudo dnf remove gnome-terminal-3.38
960:sudo dnf remove gnome-terminal-3.38*
961:dnf list gnome-terminal
963:sudo dnf install gnome-terminal*
984:dnf check-upgrade --refresh
992:dnf list automake autoconf libtool gettext make
993:sudo dnf upgrade
```

gnome-terminal 3.40.2 contains a mitigation for this.

*** Bug 1971242 has been marked as a duplicate of this bug. ***

FEDORA-2021-6d3f3aac2d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6d3f3aac2d

FEDORA-2021-6d3f3aac2d has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-6d3f3aac2d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6d3f3aac2d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-6d3f3aac2d has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.