This site is currently in read-only mode during migration to a new platform.
You cannot post questions, answers or comments, as they would be lost during the migration otherwise.
0 votes

Since some days, no matter what project I use, godot just crashes my ARCH Linux right down to power off state after various time periods which are unpredictable and more short (some minutes) than long...

At first I thought there was something wrong with my project but no matter which project I choose it just happens anyway...

I tried using LTS kernel but the same behavior occurs...

I deleted all godot configurations from my user home directory, behavior is the same...

I created a new user but same thing, godot crashes like described above...

There is nothing reported in journalctl in the previous boot context.

If I start godot -v -d > godotlog.log there is nothing in that log besides expected output...(like engine version, which gles, etc...)...

Before this happened for the first time I could work perfectly well with godot versions since 3.0 up to 3.2.1 on this machine with no trouble at all...

Since ARCH is a rolling release distro I can not spot the update since when this strange behaviour occurred...

Everything else is working fine on this particular machine.

Any ideas / directions / thoughts on how to investigate further into this issue are highly appreciated.

Godot Version

[un@asus-ux31e ~]$ godot --version
3.2.1.stable.official
[un@asus-ux31e ~]$ 

OS / Device info

[un@asus-ux31e ~]$ uname -a
Linux asus-ux31e 5.7.3-arch1-1 #1 SMP PREEMPT Wed, 17 Jun 2020 19:42:12 +0000 x86_64 GNU/Linux
[un@asus-ux31e ~]$ lspci -v
...
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
    Subsystem: ASUSTeK Computer Inc. Device 1427
    Flags: bus master, fast devsel, latency 0, IRQ 36
    Memory at ddc00000 (64-bit, non-prefetchable) [size=4M]
    Memory at c0000000 (64-bit, prefetchable) [size=256M]
    I/O ports at e000 [size=64]
    Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
    Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
    Capabilities: [d0] Power Management version 2
    Capabilities: [a4] PCI Advanced Features
    Kernel driver in use: i915
    Kernel modules: i915
...
in Engine by (31 points)

I'm using Archlinux too, and I had some issues in the past after updating my packages. Here some examples:
https://github.com/godotengine/godot/issues/37499
https://github.com/godotengine/godot/issues/36226

Is your PC only crashing when using Godot?
Is it crashing when using the Editor or Running/Debugging a game?

Version 3.2.2 nearly finished. Maybe try that:
https://godotengine.org/article/release-candidate-godot-3-2-2-rc-2

Thank you for your thoughts...

I think the issue 37499 is not similar to this since it is specifically 3D related, this issue is not at all related to any specific graphical mode...

I think issue 36226 is not related ether since it refers MONO/C# issues which I do not use and as far as I understand need another binary...

Is your PC only crashing when using Godot?

Yes, otherwise it is perfectly stable...

Is it crashing when using the Editor or Running/Debugging a game?

As far as I checked this out it crashes when...

  • ...I use the editor for anything... (editing, creating something new, whatever, ...) ...
  • ...I run a game from the editor...

As soon as 3.2.2 stable is available I will give it a try for sure...

Anyways, if that won't fix the issue, the main question persists, how can one debug the editor to gather any information...???

THX and Cheers

Please log in or register to answer this question.

Welcome to Godot Engine Q&A, where you can ask questions and receive answers from other members of the community.

Please make sure to read Frequently asked questions and How to use this Q&A? before posting your first questions.
Social login is currently unavailable. If you've previously logged in with a Facebook or GitHub account, use the I forgot my password link in the login box to set a password for your account. If you still can't access your account, send an email to [email protected] with your username.