Bug 267841 - graphics/gimp-app, devel/glib20: glib-2.74.0,2 cause crash in gimp-2.10.32,2 -> script-fu: gimp_wire_read(): error
Summary: graphics/gimp-app, devel/glib20: glib-2.74.0,2 cause crash in gimp-2.10.32,2 ...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-gnome (Nobody)
URL: https://www.freshports.org/graphics/g...
Keywords: crash, needs-qa
Depends on:
Blocks: 267254 267556 267577
  Show dependency tree / graph
 
Reported: 2022-11-18 06:34 UTC by José Maldonado
Modified: 2022-11-19 17:42 UTC (History)
4 users (show)

See Also:
jbeich: maintainer-feedback+
jbeich: merge-quarterly+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description José Maldonado 2022-11-18 06:34:23 UTC 
Hi,

The GLIB-2.74.0,2 cause a crash in GIMP-2.10.32,2. The bug is detected for GIMP developers in this issue.

https://gitlab.gnome.org/GNOME/gimp/-/issues/8286#note_1560805

More info in this link:

https://gitlab.gnome.org/GNOME/gimp/-/issues/8576


Info from my system:

OS: 13.1-RELEASE-p3
AMD Ryzen 7 3800X
Radeon RX 570 (DRM-KMOD from pkg binary) 
Only binary packages installed from quarterly repo

Triggering bug:

1.- Open Gimp
2.- Create a Text object and write anything
3.- Change property for text object 
4.- Crash 

Debug info from GIMP:

```
GNU Image Manipulation Program version 2.10.32
git-describe: GIMP_2_10_32
Build: unknown rev 0 for other
# C compiler #
	FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
	Target: x86_64-unknown-freebsd13.1
	Thread model: posix
	InstalledDir: /usr/bin

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.96)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.74.0 (compiled against version 2.74.0)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.9 (compiled against version 1.50.9)
using Fontconfig version 2.14.0 (compiled against version 2.14.0)
using Cairo version 1.17.4 (compiled against version 1.17.4)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 89027 - Thread 117411 #

(lldb) process attach --pid 89027

```
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2022-11-19 01:57:57 UTC 
Thanks. 

<https://gitlab.gnome.org/GNOME/gimp/-/issues/8576#note_1562130> (2022-09-27): 

> Make that 2.74.1: this is exactly the sort of regression that 
> stable-branch point releases are for.

Via <https://www.freshports.org/devel/glib20/#history>: 

<https://github.com/freebsd/freebsd-ports/commit/4c90553fa54204d5dd5bd2d6b5064f73f2e29e9a> (main, 2022-10-26)

> devel/glib20: update to 2.74.1

jbeich@ please, should we have a merge of 4c90553fa54204d5dd5bd2d6b5064f73f2e29e9a to quarterly?

(I'm glancing, not in detail, at some of the other reports for graphics/gimp-app with keyword crash.)
Comment 2 commit-hook freebsd_committer freebsd_triage 2022-11-19 08:58:41 UTC 
A commit in branch 2022Q4 references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=eb557422ff07713c529d2082ad53346b76954501

commit eb557422ff07713c529d2082ad53346b76954501
Author:     Jan Beich <jbeich@FreeBSD.org>
AuthorDate: 2022-10-25 12:53:22 +0000
Commit:     Jan Beich <jbeich@FreeBSD.org>
CommitDate: 2022-11-19 08:57:03 +0000

    devel/glib20: update to 2.74.1

    Changes:        https://gitlab.gnome.org/GNOME/glib/-/releases/2.74.1
    PR:             267841
    Reported by:    GitLab (notify releases), grahamperrin

    (cherry picked from commit 4c90553fa54204d5dd5bd2d6b5064f73f2e29e9a)

 devel/glib20/Makefile | 4 ++--
 devel/glib20/distinfo | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)
Comment 3 Jan Beich freebsd_committer freebsd_triage 2022-11-19 09:12:37 UTC 
(In reply to Graham Perrin from comment #1)
> jbeich@ please, should we have a merge of
> 4c90553fa54204d5dd5bd2d6b5064f73f2e29e9a to quarterly?

I did plan to (after checking pkg-status for new fallout) but forgot. Patch-level updates (X.Y.Z -> X.Y.Z+1) are usually safe to merge.