Linux 7.1.0.4414: settings UI becomes read-only after clean install (filament/process/printer)

[ricksouzaa]

Problem summary

On Ubuntu 24.04, in Creality Print 7.1.0.4414 (Ubuntu2404 AppImage), settings inputs become read-only and cannot be edited reliably.

Affected areas:

• Filament settings
• Process/Slicing settings
• Printer settings

This is reproducible in 7.1.0.4414 and does not occur with 7.0.1.4212 on the same machine/workflow.

Environment

• OS: Ubuntu 24.04 (Linux)
• Problem build: CrealityPrint_ubuntu2404-V7.1.0.4414-x86_64-Release.AppImage
• Comparison build: CrealityPrint_Ubuntu2404-V7.0.1.4212-x86_64-Release.AppImage

What was tested before reporting

A full cleanup was performed before retesting 7.1.0.4414:

• removed ~/.config/Creality/Creality Print
• removed ~/.local/share/CrealityPrint
• removed ~/.cache/CrealityPrint
• removed ~/.Creality
• removed temporary Creality folders in /tmp

After that, 7.1.0.4414 was installed again and tested from a clean state.

Reproduction steps

1. Open Creality Print 7.1.0.4414 on Linux.
2. Select/add printer profile.
3. Create a new filament profile from scratch.
4. Try to edit parameters in filament/process/printer tabs.

Actual result

Inputs behave as locked/read-only and edits cannot be applied normally.

Expected result

Inputs should remain editable and values should be saved, as in 7.0.1.4212.

Technical hypotheses from source comparison (v7.0.1 -> v7.1.0)

Large delta between tags (349 files changed). Possible regression area in GUI state/preset editability flow:

• src/slic3r/GUI/ParamsPanel.cpp
• src/slic3r/GUI/Tab.cpp
• src/slic3r/GUI/SyncUserPresets.cpp
• src/libslic3r/Preset.cpp

A likely candidate is active-tab state handling around ParamsPanel::set_active_tab(nullptr) in 7.1.0 path, potentially leaving stale UI state and causing fields to be treated as system/default (read-only). This is a hypothesis from code diff and symptom matching.

Request

Please confirm as a Linux regression in 7.1.0.4414 and advise workaround or planned patch.

[yevhen-vynohradov]

Have the same issue (((

[pjJedi]

Same here, also can't edit anything, and whenever i close the program it opens again and wants to send an error report

[ricksouzaa]

@hemiao2023 Could you change this issue adding bug label?

[Arm4g3ddon]

Confirming this also affects Arch Linux.

Same read-only behavior in Creality Print 7.x — when editing a preset, the Cooling tab (and other settings) are greyed out / not editable. Removing the config dirs (~/.config/Creality, ~/.local/share/CrealityPrint, ~/.cache/CrealityPrint, ~/.Creality) did not help here either. Downgrading to 7.0.1.4212 is the only workaround so far. +1 for a fix.

[ricksouzaa]

Still reproducible in 7.2.0.5226 stable (July 2026). Follow-up: #576

This regression was never fixed across 7.1.0 → 7.1.1 → 7.2.0. Linux preset editing remains broken. Please merge these reports and assign a fix.

[Arm4g3ddon]

@ricksouzaa I opened PR #572 a month ago that fixes exactly this — the wxWindowDisabler that makes the GTK dialog insensitive so all inputs read as locked — plus the clean-profile startup crash and the libLerc link error. Still no response from Creality.

If you (or anyone else in this thread) just need a working build in the meantime, I've published a prebuilt AppImage with these fixes on my fork:
https://github.com/Arm4g3ddon/CrealityPrint/releases/tag/v7.1.2

Settings are editable again there. Happy to rebase onto a newer release once the maintainers pick the PR up.

[Arm4g3ddon]

Update: as promised, I rebased the fixes onto Creality's brand-new 7.2.0 release (which still ships this bug — see #576). New prebuilt AppImage here:

https://github.com/Arm4g3ddon/CrealityPrint/releases/tag/v7.2.1

Settings are editable again, and I also fixed a separate Linux crash-on-exit (static GLModel destructors hitting a dead GL context). The v7.1.2 build linked above still works too if you're staying on 7.1.x. Fix is still pending upstream as PR #572.

[hemiao2023]

Thanks for the feedback. I'll take care of some GitHub issues this month. This is a temporary build for the issue in question. https://github.com/CrealityOfficial/CrealityPrint/releases/download/v7.2.0/CrealityPrint-ubuntu2404-V7.2.0.5251-x86_64-Release.AppImage

[Arm4g3ddon]

@hemiao2023 thanks for the quick response and the temporary build. Confirmed on Arch Linux: V7.2.0.5251 fixes the read-only preset editing — filament/process/printer fields (cooling, temperatures, etc.) are editable again. 👍

One heads-up while you're looking at the Linux builds: there is a separate crash on exit that 5251 still has. It's unrelated to the read-only issue — the app segfaults on shutdown every time. I traced it: GUI_App::OnExit() calls std::exit(0), which runs the C++ global/static destructors; a static GLModel is then destroyed and calls GLModel::RenderData::release() -> glDeleteBuffers() after the GL context is already gone, dereferencing a stale entry point. breakpad's handler then double-faults on top (it throws boost::filesystem from inside the signal handler).

I still reproduce the SIGSEGV coredump on exit with your 5251 build (sha256 572f8cfd…).

There's a ready fix for both parts in PR #577 (Linux terminates via std::_Exit(0) after state is already saved; breakpad dumpCallback made exception-safe). Windows/macOS unchanged. Would be great to get it in alongside the read-only fix.