Page MenuHomeAleph Objects Inc

collapsing setting categories sometimes makes them all disappear
Open, LowPublic

Description

While setting up prints, when collapsing an expanded settings category, sometimes all of the settings will be invisible with only the search bar.
The work-around is to put something in the search bar, delete it, and then all the settings re-appear.

Event Timeline

logan created this task.Jan 9 2019, 8:47 AM
logan updated the task description. (Show Details)
logan added a comment.Jan 9 2019, 8:50 AM

Happens on multiple versions of CuraLE; 3.2.32 (testing repo) 3.6.3 (local master build)
Workstation: Hillstar
Printer: All/Any

karrad added a subscriber: karrad.Jan 9 2019, 8:53 AM

@logan Can you grab a log? should be in /home/<username>/.local/share/cura-lulzbot/3.x/cura-lulzbot.log

karrad triaged this task as Low priority.Jan 9 2019, 8:53 AM
logan added a comment.Jan 9 2019, 8:55 AM

From 3.6.3:


From 3.2.32:

alexei changed the edit policy from "All Users" to "Cura LulzBot Edition (Project)".Jan 9 2019, 1:34 PM
alexei added a subscriber: alexei.Jan 9 2019, 2:20 PM

@logan ,

This is relevant:

2019-01-09 07:39:59,438 - WARNING - [(140507555476864)-MainThread] LocalContainerProvider.LocalContainerProvider._saveCachedDefinition [243]: The definition cache for definition fdmprinter failed to pickle.

The problem you are hitting here is that you'll need to clear cache every time you are switching from 3.2 to 3.6 and back, because in 3.6 some CuraEngine options were removed and some were added.

logan added a comment.Jan 9 2019, 2:23 PM

So I cannot use the CuraLE installed on my workstation via the testing repo if I am using a local build for testing?

alexei added a comment.Jan 9 2019, 2:39 PM

@logan, You can use them, just make sure you have a single instance of CuraLE running and also that you are clearing cache when switching versions.

logan added a comment.Jan 9 2019, 2:41 PM

Hm, alright. I will keep an eye on this next time I have time to export WIP profiles, clear cache, update, and re-import.

karrad closed this task as Wontfix.Jan 10 2019, 2:27 PM
karrad claimed this task.
alexei reopened this task as Open.Feb 4 2019, 1:24 PM
logan added a comment.Feb 4 2019, 2:32 PM

Happened again today, have 3.6.3 build, no other versions opened since last rebuild and cache clear

logan added a comment.Feb 6 2019, 9:54 AM

Again today, fresh build of 3.6.4 generated yesterday running from a freshly cleared cache

@logan There was this exception:

2019-02-05 11:37:04,710 - ERROR - [(140221144360704)-Thread-13] UM.Logger.logException [82]: Exception: Job <CuraEngineBackend.StartSliceJob.StartSliceJob object at 0x5584a1fabe08> caused an exception
2019-02-05 11:37:04,712 - ERROR - [(140221144360704)-Thread-13] UM.Logger.logException [86]: Traceback (most recent call last):
2019-02-05 11:37:04,713 - ERROR - [(140221144360704)-Thread-13] UM.Logger.logException [86]:   File "/home/aleph/Projects/cura/build-master/build/inst/lib/python3/dist-packages/UM/JobQueue.py", line 125, in run
2019-02-05 11:37:04,714 - ERROR - [(140221144360704)-Thread-13] UM.Logger.logException [86]:     job.run()
2019-02-05 11:37:04,714 - ERROR - [(140221144360704)-Thread-13] UM.Logger.logException [86]:   File "/home/aleph/Projects/cura/build-master/build/dist/plugins/plugins/CuraEngineBackend/StartSliceJob.py", line 216, in run
2019-02-05 11:37:04,717 - ERROR - [(140221144360704)-Thread-13] UM.Logger.logException [86]:     if group[0].getParent().callDecoration("isGroup"):
2019-02-05 11:37:04,718 - ERROR - [(140221144360704)-Thread-13] UM.Logger.logException [86]: AttributeError: 'NoneType' object has no attribute 'callDecoration'

QML binding loop:

2019-02-05 11:52:46,183 - WARNING - [(140335887660416)-MainThread] UM.Qt.QtApplication.__onQmlWarning [274]: file:///home/aleph/Projects/cura/build-master/build/dist/plugins/plugins/Tools/ScaleTool/ScaleTool.qml:9:1: QML ScaleTool: Binding loop detected for property "width"

Another QML error:

2019-02-05 11:58:00,934 - WARNING - [(139947667604864)-MainThread] UM.Qt.QtApplication.__onQmlWarning [274]: file:///home/aleph/Projects/cura/build-master/build/dist/resources/qml/Sidebar.qml:337:9: QML Label: Cannot anchor to an item that isn't a parent or sibling.
logan added a comment.Feb 6 2019, 11:58 AM

@alexei What does that mean?
At least now I know it is a bug and nothing that I'm doing.

And another QML error:

2019-02-05 13:03:08,020 - WARNING - [(139947667604864)-MainThread] UM.Qt.QtApplication.__onQmlWarning [274]: file:///home/aleph/Projects/cura/build-master/build/dist/resources/qml/Preferences/ProfilesPage.qml:217:27: Unable to assign [undefined] to QString

@logan , Will need to see where exactly these errors are coming from.

logan added a comment.Feb 11 2019, 2:42 PM

Here's a log from today, more occurrences


I'll go ahead and rebuild and clear cache

logan added a comment.Feb 27 2019, 9:45 AM

Still happening often, do you have enough logs or should I continue to post them?

Just to keep up to date:


Local build 3.6.6 generated today 3/26 running from freshly cleared cache

anolen added a subscriber: anolen.EditedMay 16 2019, 10:34 AM

I have been experiencing this also, it used to happen very infrequently but has been getting steadily worse. my quick fix I am using for now is selecting "Recommended" and then re selecting "Custom".
My build was made yesterday after the revert of 3.6.10, however, I have seen this on all builds in the past at least once.

@anolen I just type a character in the search bar and then tap the x on the right of the search bar, makes them all reappear

@anolen Does this ever happen in a view aside from layer view?