Bug 241339

Summary: audio/audacity: Crashes at startup: Gtk-ERROR **: 12:54:47.905: GTK+ 2.x symbols detected
Product: Ports & Packages Reporter: Emanuel Haupt <ehaupt>
Component: Individual Port(s)Assignee: Emanuel Haupt <ehaupt>
Status: Closed Not A Bug    
Severity: Affects Only Me CC: xxjack12xx
Priority: --- Keywords: needs-patch, needs-qa
Version: LatestFlags: tobik: maintainer-feedback+
koobs: merge-quarterly?
Hardware: Any   
OS: Any   
See Also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236512
Attachments:
Description Flags
Mark port broken. koobs: maintainer-approval-

Description Emanuel Haupt freebsd_committer 2019-10-19 11:00:42 UTC
Created attachment 208417 [details]
Mark port broken.

audio/audacity dumps core on a vanilla 12.0-RELEASE amd64 all package system:

$ audacity 

(Audacity:27716): Gtk-ERROR **: 12:54:47.905: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported
Trace/BPT trap (core dumped)

Mark port broken.
Comment 1 Jack 2019-10-19 11:08:13 UTC
The port isn't broken, a dependency is causing the breakage but I haven't been able to track down which one it is. When compiled from ports, it does not experience this problem.
Comment 2 Tobias Kortkamp freebsd_committer 2019-10-19 11:38:11 UTC
Can confirm.  It works just fine on 13.0-CURRENT with my own self built packages.
Please do not mark it as broken.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2019-10-19 12:15:13 UTC
^Triage: Reporter is committer, assign accordingly
Comment 4 Jack 2019-10-20 03:18:54 UTC
I'm currently installing 12.1 RC2 amd64 to see if I can find the issue with a package installation only.
Comment 5 Jack 2019-10-20 04:41:17 UTC
Fresh install of 12.1 RC2 amd64 from packages and only audacity+deps installed works fine
Comment 6 Emanuel Haupt freebsd_committer 2019-10-20 19:35:02 UTC
There must be some conflict with another package. I installed a vanilla 12.0-RELEASE with only audacity and xorg and it runs perfectly fine.

I am trying to narrow down the conflicting port.
Comment 7 Emanuel Haupt freebsd_committer 2019-10-21 18:14:08 UTC
If it's fine with you, I suggest we close this PR and track the conflicting port issue in 236512.
Comment 8 Jack 2019-10-21 18:40:51 UTC
yes please.