Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#79024 - [godot] 4.1-1 Systematic hang of application, requires kill
Attached to Project:
Arch Linux
Opened by c (grinness) - Sunday, 09 July 2023, 10:46 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 12 July 2023, 07:45 GMT
Opened by c (grinness) - Sunday, 09 July 2023, 10:46 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 12 July 2023, 07:45 GMT
|
DetailsDescription:
godot 4.1-1 systematically hangs after start as soon as one of the menu (top left) is clicked (Scene, Project, Debug, Editor, Help) Requires KILL to close Same behaviour when: - opening an old project - downloading an opening a project from godot repos (via godot interface) - creating a new project No error is shown in jounrnalctl, dmesg or terminal (if godot run from terminal) Additional info: * package version(s) godot 4.1-1 * config and/or log files etc. My System: Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.4.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6800 * link to upstream bug report, if any NONE Steps to reproduce: open godot, create new project, click on any of the top-left menu (Scene, Project, Debug, Editor, Help) |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 12 July 2023, 07:45 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
Wednesday, 12 July 2023, 07:45 GMT
Reason for closing: Upstream
Additional comments about closing: See comments
I've notified the PM just in case...but please visit the Arch support channels (Forum/IRC/Mailing Lists/Reddit/etc) to see if anyone can repro or help track it down.
Apologies for re-opening, just for your info:
* I run godot 4.1-1 under valgrind, I get the same behaviour: application freeze, no error shown on output and need to kill it
* aur package godot 4.2.r1.e4be11b-1 works no problem -- maybe it is an upstream bug, definitely nothing to do with my system
If you want to close again, please do
Thanks
I'm failing to see how that is relevant. i.e. I still can't repro. Maybe it only happens on AMD GPU? My VM uses an Nvidia card.
> aur package godot 4.2.r1.e4be11b-1 works no problem
Again, failing to see how that helps. The PKGBUILD for godot-git looks completely different and it also depends on *how* you build the AUR pkg because official Arch pkgs are are built in a pristine chroot with tightly controlled *FLAGS etc.
Or are you testing under Wayland?
I am under Wayland (+ all AMD open-source stack)
With regards to AUR compilation, my *FLAGS (in /etc/makepkg.conf) are all standard except for:
* I am using -march=native -O2
* I have 24 thread compilation: -j24
Extract relevant makepkg.conf below:
#
CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"
#-- Compiler and Linker Flags
#CPPFLAGS=""
CFLAGS="-march=native -O2 -pipe -fno-plt -fexceptions \
-Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security \
-fstack-clash-protection -fcf-protection"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
LTOFLAGS="-flto=auto"
#RUSTFLAGS="-C opt-level=2"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j24"
#-- Debugging flags
DEBUG_CFLAGS="-g"
DEBUG_CXXFLAGS="$DEBUG_CFLAGS"
#DEBUG_RUSTFLAGS="-C debuginfo=2"
I tested official release from https://godotengine.org/:
* Godot 4.1 Official Release shows the same issue
* Godot 4.0.3 Official Release works fine
Below link to 4.0.3 -- using linux 64 bit:
https://downloads.tuxfamily.org/godotengine/4.0.3/
It seems to be an upstream bug
Yes [1]. It should be fixed when 4.1.1 gets released.
[1] https://github.com/godotengine/godot/issues/78487