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 "Restricted Project (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?

@karrad, I have had it happen in both the solid view and the layer view.

bmh added a subscriber: bmh.Jul 2 2019, 12:09 PM

This has happened to me all the time in 3.2.x and 3.6.x, at least up to 3.6.10. The description says putting something in the search bar fixes - switching between to the Monitor tab and back to Prepare tab also "fixes" it.

For me at least, once is starts occurring it seems to get worse and it seems the more times you open/collapse a settings bar the higher the chances of it starting to occur.

I am so excited to see this reported - it can be quite annoying :-) :-).

karrad added a comment.EditedJul 2 2019, 12:10 PM

@bmh Thank you for the additional report! We have had a really hard time duplicating this, as it appears to happen randomly.

Would you be able to attach the cura-lulzbot log for review? We would like to see if there is any insight there.

EDIT: missed log*

bmh added a comment.EditedJul 2 2019, 1:06 PM

@bmh Thank you for the additional report! We have had a really hard time duplicating this, as it appears to happen randomly.

Would you be able to attach the cura-lulzbot log for review? We would like to see if there is any insight there.

EDIT: missed log*

LOL, I was confused until you said log :-). Please point me to the location of the log and yes I will send to you. I will also try to see if I can get it to happen in a repeatable fashion. I do know that the more times you open/collapse a settings bar is when it starts happening. Maybe try alternating between two bars and keep open/collapsing them and I'll bet it starts happening fairly soon.

I'll send the log when I get home.

EDIT: Nevermind, I see at the top of this thread about the log location :)

bmh added a comment.EditedJul 2 2019, 2:39 PM

Cura 3.6.10

My Cura had been sitting open for probably a week without use, but TAZ Pro was off. Turned TAZ Pro on - did not tell it to connect. There was an xyz cube stl loaded at the time.

Open/closed "Quality" settings bar 10 times. Then open/closed "Shell" and things started disappearing on either the first or second open/close.

Closed Cura, re-opened, could not get it to repeat the issue and clicked around like a madman trying to get it to occur.

Other things noticed in the past ...

Sometimes the arrow indicating whether settings bar is opened or closed gets confused and points the wrong direction.

Sometimes not everything disappears - sometimes only some of the bars disappear.

Not sure if this lends anything, but maybe a memory leak of some sort - in my case I have a habit of leaving Cura open all the time, even after turning off the TAZ Pro. Only time I close it usually is if the PC needs rebooted for an update or if Cura had crashed.

My log file is attached - it was around 16:15 or somewhere close to that (today, 7/2) that I did this most recent test when it failed the first time (but again, could not get it to repeat yet today after the first failure).

EDIT: One more item I remembered ... at one point I played around with Cura 4.0 (or maybe it was 4.1) ... it's a hot piece of garage :-), but that aside, the bar disappearing issue occurred a couple times for me in that version too. I realize that's a different development line, but still info I guess.

bmh added a comment.Jul 3 2019, 11:16 AM

So last night after installing and playing with Cura 3.6.13 (~4pm), I left it open overnight and could not get the settings bar to disappear. But now today (~1pm) - again it was left open overnight - it happens about every other time I open/collapse a bar. Just more info I guess, maybe related to leaving it open, dunno for sure.

karrad reassigned this task from karrad to TKostennov.Jul 3 2019, 12:52 PM
karrad added a subscriber: TKostennov.

@bmh Thank you for the additional feedback, we will see if we can dig anything up.

@TKostennov Can you look into the disappearing settings please? Let us know if you need any other info or details.

karrad moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jul 3 2019, 12:53 PM
anolen added a comment.Jul 3 2019, 3:19 PM

This is also still happening to me on the most recent build 3.6.14.

karrad added a comment.Jul 3 2019, 3:40 PM

@logan @anolen We got that out a few days ago, have you restarted Cura since then?

logan added a comment.Jul 3 2019, 3:47 PM

I updated my local build per the wiki instructions, including clearing the cache yesterday afternoon. I have had this happen multiple times today while setting up a single print, TAZ 6 Dual v3 in this case.

karrad added a comment.Jul 3 2019, 3:52 PM

@logan Clear cache, and don't use the local build. I would like to test to see if any conflicts of differing versions are occurring.

Clear cache and launch from graphics folder, you have 3.6.13 installed on the workstation.

logan added a comment.Jul 3 2019, 3:57 PM

@karrad That has already been ruled out I think. For quite some time, per @alexei's suggestion above, I ran only one version with nothing from any other versions present in the .local directory and it was still happening regularly.
@alexei noted above some errors that are suspect, perhaps looking at the causes of those would be more effective troubleshooting?

logan added a comment.Jul 3 2019, 4:00 PM

I'm in the middle of printing things on the v3 Dual (of course I have to use custom profiles or it wont work) so I can't clear my cache right now. Maybe sometime next week.

@karrad @logan Still can't reproduce it on my side. Can we get more info about OS and computers configuration, please?

logan added a subscriber: kaleb.EditedJul 11 2019, 11:00 AM

Myself I have seen it on my workstation (hillstar) which is running debian, and my home computer which is running Ubuntu 18.10 (cosmic)
@alexei or @kaleb may be able to elaborate further on our workstation configurations.

anolen added a subscriber: Steven.Jul 11 2019, 11:33 AM

I have this happen at least a handful of times a day, no matter the machine or material or version #. Currently running 3.6.15.

My workstation is named PRION. I do not know what kind of info is needed or what that info for my station would be. @Steven can probably tell you more about my workstation, Ill check around in RandD and see if anyone else is also seeing it and we can get their workstation info too.

bmh added a comment.Jul 11 2019, 12:34 PM

I might be repeating part of what I said in an earlier comment, but for me it has happened on all versions from 3.2.32 all the way up to 3.6.14. I am running Windows 10.

Also would like to note that at one point about a month ago I downloaded Cura 4.1 to see what it was all about - for the record it seriously SUCKS - that aside, in the short couple hours I played with it, the disappearing settings bar issue appears there too.

So given it's in all versions from early to latest it certainly seems to be some systemic issue. The only other data I previously noted is I leave Cura LE open all the time and the longer it's open the more frequently it starts to happen; if I close/open Cura LE it takes a while before I start seeing the issue again (which feels memory-leakish).

In addition to someone else noting you can "resolve" it by putting something in search bar then erasing, you can also "resolve" it by switching to the Monitor tab then back to the Prepare tab.