App freezes completely when attempting to save a new file

block36underscore commented 4 weeks ago

What are you trying to do, and what do you expect to happen?

I am trying to save a file. The file explorer menu should close once the location is selected and the app should continue working as normal. The file should also save.

What happens instead?

The file is not saved, and the app does not respond to any inputs.

I have tried this on both the deb installation, the flatpak installation, and the appimage. All of them act the same. I was seeing some weird messages from AppArmor in dmesg, but they were inconsistent, and unrelated to file saving. No messages show up in the electron console, or the one running the app.

Model format in which the issue occurs

I have tested generic and images, but it probably happens to all of them.

Blockbench variant

Program

Blockbench version

4.10.2

Operating System

Linux (Debian based)

Installed Blockbench plugins

none

block36underscore commented 4 weeks ago

Restarting my computer resolved this issue

block36underscore commented 4 weeks ago

I spoke too soon. I reinstalled the deb version and this issue is back again. I'll be investigating some more

block36underscore commented 4 weeks ago

After some testing I have found that saving works as normal, but file creation (or overwriting a file) is linked with the freeze

It may or may not be relevant, but I'm getting the weird AppArmor message again.

[   35.913174] audit: type=1400 audit(1717091973.756:229): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=4214 comm="blockbench" requested="userns_create" target="unprivileged_userns"
[   35.913928] audit: type=1400 audit(1717091973.757:230): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=4216 comm="blockbench" capability=21  capname="sys_admin"
[   37.249371] i915 0000:00:02.0: Using 39-bit DMA addresses
[   82.090824] audit: type=1400 audit(1717092019.744:231): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=4500 comm="blockbench" requested="userns_create" target="unprivileged_userns"
[   82.091539] audit: type=1400 audit(1717092019.744:232): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=4502 comm="blockbench" capability=21  capname="sys_admin"

boot2big commented 4 weeks ago

Same issue here, unsure of any way to remedy this on my end either. Behaves similarly in that I'm unable to create files, whether new or as an overwrite of existing ones.

Edit with additional system information: Debian distribution, KDE Plasma 5.27.11 (KDEF 5.115.0, QT 5.15.13, kernal 6.8.0-31 64-bit)

YTFrost commented 4 weeks ago

Same issue on EndeavourOS (Arch-based). Getting the same errors.

AlexTMjugador commented 4 weeks ago

Happens over here on Debian Sid too, downgrading to 4.10.1 fixed my problem. I had no MAC kernel security module (AppArmor, SELinux) running. I had no plugins installed. ~~Reopening the app after forcibly killing its process to stop the freeze may at times reset the Blockbench configuration.~~ (Maybe the configuration thing is #2365?)

block36underscore commented 4 weeks ago

Downgrading to 4.10.1 also worked for me.

boot2big commented 4 weeks ago

Seems that's what I'll have to do in the meantime as well, though I'd much rather be able to run the latest stable version of BB for modeling.

OrdinaryCloverOC commented 3 weeks ago

same with flatpak/rpm on fedora

Vetpetmon commented 3 weeks ago

App also freezes on my system. Pop!_OS distro, deb package. 4.10.2

Attempted with generic model. forcing it to close resets all user preferences and plugins

Thankfully, it keeps a backup of the project, but the app is unusable otherwise.

Please fix ASAP, I reproduced this error 6 times in under 10 minutes.

AlexTMjugador commented 3 weeks ago

I couldn't reproduce the issue when building Blockbench from source via npm ci && npm run dist with the latest master branch code (commit 3b3bf65). That's another possible workaround, for people comfortable with building Node projects.

halotroop2288 commented 2 days ago

Built from source (ae59908f986df984fa1b8b4c8fa42a476ee703d9) just to confirm that this is still not fixed. 👎🏻

Arch 6.9.6 + Plasma 6.1.0

AlexTMjugador commented 1 day ago

Built from source (22e6b9c) just to confirm that this is still not fixed. 👎🏻

The next branch the commit you mentioned belongs to doesn't contain commit bdf0043, which is only available on master. next is a different codeline that I don't consider necessarily comparable to master in this regard.

halotroop2288 commented 20 hours ago

Yes, the master branch does contain that commit.

That is exactly the branch I cloned to build from source. The next branch has nothing to do with this.

AlexTMjugador commented 20 hours ago

Okay... It looks like the v4.10.3 release didn't fix this issue for you then? On my end, it was fixed after updating to v4.10.3.

halotroop2288 commented 20 hours ago

4.10.3 is the only version I ever installed on my Linux system. I don't have the choice to go back, because downgrading packages tends to break Arch.

JannisX11 commented 20 hours ago

You won't receive the fix if you are trying to build from source using the regular npm scripts. Linux uses an older electron version does doesn't have the issue yet and it's switched out in the CI script. If you are still having the issue, try downloading Blockbench from the website since third party builds may not contain the fix in some cases.

halotroop2288 commented 19 hours ago

try downloading Blockbench from the website

That checks out. Now it's fixed.

third party builds may not contain the fix in some cases.

Then can you please provide an official AUR package? I do not like installing apps outside of the official package manager.

JannisX11 / blockbench