Is there an existing issue for this problem?
Snapmaker_Orca Version
2.4.3
Operating System (OS)
Linux
OS Version
OS: Ubuntu 25.04
Additional system information
No response
Printer
Snapmaker U1
How to reproduce
Start the AppImage on Linux.
Log in to Snapmaker cloud successfully.
Use the app normally.
Close the app normally.
Reopen the app.
Observe that the cloud login is gone
Relevant log evidence
On startup after restart, the logs show:
_getDeviceInfo: loginUser: {nickname: , email: , account: , status: offline, icon: , avatar: , token: , token_type: Bearer, userid: , uid: , id: , cellphone: }
eventId:logoutDeleLocalClouldDevice
The embedded web/cloud layer also reports:
FormatException SyntaxError JSON Parse error
Error running JavaScript: Unsupported result type
Persistence/storage investigation
I checked the app’s config and local storage behavior:
~/.config/Snapmaker_Orca/Snapmaker_Orca.conf is rewritten during app use, but it does not contain obvious auth/session fields; grep only found:
sync_user_preset
user_mode
The Snapmaker-specific web storage exists here:
~/.local/share/snapmaker-orca/localstorage/https_id.snapmaker.com_0.localstorage
with matching -shm and -wal files.
However, the SQLite localstorage DB contains only:
redirect|
redirectURL|h
username|e
from|o
There is no obvious token/session/auth payload stored there.
What I suspect
It looks like the visible login flow completes, but the actual authenticated session is not persisted, or the persisted data is not restored correctly on startup. The JS/JSON errors in the embedded web layer may be related.
Additional notes
I also saw one run with:
Not primary owner of DBus name - probably another SnapmakerOrca instance is running
But the blank-token startup behavior and web errors also occur in runs without relying on that specific DBus warning as the primary explanation.
Attachments
Debug logs from affected runs
Output showing localstorage contents
File/path investigation results per Linux config/local-share storage layout
Small edits before posting
Replace these placeholders before you submit:
Exact app version from Help -> About
Your distro/version
Whether you launched via AppImage directly or through a desktop entry
Actual results
After restart, the app behaves as logged out. In the debug logs, loginUser is restored with empty values including an empty token, and logout-related device update events are emitted.
Expected results
After a successful cloud login, the session should persist across normal app restarts.
Project file & Debug log uploads
debug_Fri_Apr_03_17_0.zip
Checklist of files to include
Anything else?
No response
Is there an existing issue for this problem?
Snapmaker_Orca Version
2.4.3
Operating System (OS)
Linux
OS Version
OS: Ubuntu 25.04
Additional system information
No response
Printer
Snapmaker U1
How to reproduce
Start the AppImage on Linux.
Log in to Snapmaker cloud successfully.
Use the app normally.
Close the app normally.
Reopen the app.
Observe that the cloud login is gone
Relevant log evidence
On startup after restart, the logs show:
_getDeviceInfo: loginUser: {nickname: , email: , account: , status: offline, icon: , avatar: , token: , token_type: Bearer, userid: , uid: , id: , cellphone: }
eventId:logoutDeleLocalClouldDevice
The embedded web/cloud layer also reports:
FormatException SyntaxError JSON Parse error
Error running JavaScript: Unsupported result type
Persistence/storage investigation
I checked the app’s config and local storage behavior:
~/.config/Snapmaker_Orca/Snapmaker_Orca.conf is rewritten during app use, but it does not contain obvious auth/session fields; grep only found:
sync_user_preset
user_mode
The Snapmaker-specific web storage exists here:
~/.local/share/snapmaker-orca/localstorage/https_id.snapmaker.com_0.localstorage
with matching -shm and -wal files.
However, the SQLite localstorage DB contains only:
redirect|
redirectURL|h
username|e
from|o
There is no obvious token/session/auth payload stored there.
What I suspect
It looks like the visible login flow completes, but the actual authenticated session is not persisted, or the persisted data is not restored correctly on startup. The JS/JSON errors in the embedded web layer may be related.
Additional notes
I also saw one run with:
Not primary owner of DBus name - probably another SnapmakerOrca instance is running
But the blank-token startup behavior and web errors also occur in runs without relying on that specific DBus warning as the primary explanation.
Attachments
Debug logs from affected runs
Output showing localstorage contents
File/path investigation results per Linux config/local-share storage layout
Small edits before posting
Replace these placeholders before you submit:
Exact app version from Help -> About
Your distro/version
Whether you launched via AppImage directly or through a desktop entry
Actual results
After restart, the app behaves as logged out. In the debug logs, loginUser is restored with empty values including an empty token, and logout-related device update events are emitted.
Expected results
After a successful cloud login, the session should persist across normal app restarts.
Project file & Debug log uploads
debug_Fri_Apr_03_17_0.zip
Checklist of files to include
Anything else?
No response