Debug information not generated upon crash. #111720

New Issue

Thomas Kaldahl · 2023-08-31T04:46:06+02:00

Thomas Kaldahl commented

2023-08-31 04:46:06 +02:00

System Information
Operating system: Arch Linux 6.4.12-arch1-1
Graphics card: AMD ATI Radeon 680M

Blender Version
Broken: 3.6.2
Worked: Could not determine (tried up to 3.5.1, which does not work without a full system downgrade)

Short description of error
Blender crashes immediately upon launch.

Launching from the command line, I get this:

Writing: /tmp/blender.crash.txt
Segmentation fault (core dumped)

The contents of /tmp/blender.crash.txt are this:

# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e

# backtrace

# Python backtrace

Passing the --debug-all flag, I get no errors. I attached the output of this command as a text file.

While Blender crashing on startup is not in and of itself an issue worthy of reporting, the lack of any debug information immediately makes the problem impossible to tackle independently. I have no idea what my next steps should be here.

Exact steps for others to reproduce the error
Launch blender.

**System Information** Operating system: Arch Linux 6.4.12-arch1-1 Graphics card: AMD ATI Radeon 680M **Blender Version** Broken: 3.6.2 Worked: Could not determine (tried up to 3.5.1, which does not work without a full system downgrade) **Short description of error** Blender crashes immediately upon launch. Launching from the command line, I get this: ``` Writing: /tmp/blender.crash.txt Segmentation fault (core dumped) ``` The contents of /tmp/blender.crash.txt are this: ``` # Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e # backtrace # Python backtrace ``` Passing the --debug-all flag, I get no errors. I attached the output of this command as a text file. While Blender crashing on startup is not in and of itself an issue worthy of reporting, the lack of any debug information immediately makes the problem impossible to tackle independently. I have no idea what my next steps should be here. **Exact steps for others to reproduce the error** Launch blender.

tmp.txt

1.8 KiB

Thomas Kaldahl added the

labels 2023-08-31 04:46:07 +02:00

Pratik Borhade commented

2023-08-31 06:49:46 +02:00

Hi, thanks for the report. Could it be due to some add-on? Earlier AMD pro render add-on had resulted in similar problem.
Could you try with factory settings?: File > Defaults > Load Factory Settings

Hi, thanks for the report. Could it be due to some add-on? Earlier AMD pro render add-on had resulted in similar problem. Could you try with factory settings?: `File > Defaults > Load Factory Settings`

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-08-31 06:49:55 +02:00

Thomas Kaldahl commented

2023-08-31 07:49:51 +02:00

Not possible. As stated, Blender crashes upon startup. The GUI never appears.

I deleted the config files and tried again, to no avail.

Not possible. As stated, Blender crashes upon startup. The GUI never appears. I deleted the config files and tried again, to no avail.

Pratik Borhade commented

2023-08-31 07:54:26 +02:00

I deleted the config files and tried again, to no avail.

and scripts folder? Because add-on sits there.
You can use --factory-startup argument instead of deleting folders.

> I deleted the config files and tried again, to no avail. and scripts folder? Because add-on sits there. You can use `--factory-startup` argument instead of deleting folders.

Neightro commented

2023-09-11 07:27:04 +02:00

To anyone else experiencing this issue, it seems that the current version of Blender in Arch's repos is broken.

Per this r/archlinux thread, run sudo downgrade --ala-only blender and select version 17:3.6.2-5. This isn't in the repos at the moment—it's the current version in the extra-staging repo—though it worked just fine for me.

That leaves the mystery of the empty crash reporting unsolved. All I can offer is that on my machine, it prints Read prefs: "/home/[username]/.config/blender/3.6/config/userpref.blend" and then hangs; no 'segmentation fault' message.

Is there a way to induce a crash during startup? I'm curious to test the behavior of the newer package, to see if it's reproducible outside that one broken build.

To anyone else experiencing this issue, it seems that the current version of Blender in Arch's repos is broken. Per [this r/archlinux thread](https://www.reddit.com/r/archlinux/comments/16e2jwo/blender_seems_to_be_broken_in_its_current_version/), run `sudo downgrade --ala-only blender` and select version 17:3.6.2-5. This isn't in the repos at the moment—it's the current version in the extra-staging repo—though it worked just fine for me. --- That leaves the mystery of the empty crash reporting unsolved. All I can offer is that on my machine, it prints `Read prefs: "/home/`[username]`/.config/blender/3.6/config/userpref.blend"` and then hangs; no 'segmentation fault' message. Is there a way to induce a crash during startup? I'm curious to test the behavior of the newer package, to see if it's reproducible outside that one broken build.

Pratik Borhade commented

2023-10-23 08:54:46 +02:00

Closing if this is a problem in arch repo.

Pratik Borhade closed this issue

2023-10-23 08:54:49 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-10-23 08:54:50 +02:00