Date: Tue, 14 Mar 2023 15:17:44 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 270210] cad/openscad segfault, possibly wrong version Message-ID: <bug-270210-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270210 Bug ID: 270210 Summary: cad/openscad segfault, possibly wrong version Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: mr@FreeBSD.org Reporter: phryk-ports@wzff.de Assignee: mr@FreeBSD.org Flags: maintainer-feedback?(mr@FreeBSD.org) I'm on 13.1-RELEASE and OpenSCAD started always segfaulting when trying to start after updating the package. Additionally, `openscad -v` (which doesn't segfault, I assume it's a GUI-specific problem) gives me `OpenSCAD version 2023.03.02`, even tho the package version is `2021.01.01.20221206`, so I have the suspicion that the wrong upstream commit is getting built. I get the same issue with the `openscad-devel` pkg, but there I'd at least assume a 2023.x version to be the right thing. I think this might be a Qt problem. Initially I was able to defer the segfault to after the initial dialog that lets you choose recently opened files by unsetting `QT_QPA_PLATFORMTHEME` in my env, which usually contains `qt5ct`. But after installing openscad from a custom poudriere pkg repo (that package had the same segfault issue) and going back to only the official repo, including running `pkg upgrade -f`, I can't reproduce that behavior anymore. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-270210-7788>