also added to TODO here: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Scripting
Will have look again if time permits

regarding the xml error: I pushed rBA8d3301f66c77e7b5a1f310 now.
Closing the whole report as resolved then.

@stephen leger (stephen_leger): ok, I have a fix, will push tomorrow...

Confirming it's caused by above mentioned commit. @Campbell Barton (campbellbarton): feel free to assign to me and I'll try my luck :)

Still dont think this is a bug (as this is working as designed), but I feel your pain and leave this open so it doesnt get lost..., assigning @Julian Eisel (Severin) here to have a final word.

Even though the first issue seems fixed I can confirm the second ('xml is not defined')

This is not an official blender version, right? (seeing that it is distributed by Chaos Group)

not sure it's the best place, but also added to TODO here

Dont have issues in your provided .blend
Think there are two issues to solve here:

Hi there,

Hi @Troy Sobotka (sobotka), noticed this has been unanswered for quit some time.
Issue adds up to already existing T41287.

Afaik, blenders alembic exporter does not support particle dupli objects and only exports points. (see the manual)
For mesh objects you can use a particle instance modifier [that will export OK], but unfortunately this is not available for metaballs.

Blender actually imports the geometry as well, but has trouble updating the mesh.

We need a .blend file to reproduce [please also post the picture here directly as you have to be logged into BA to see it]

Please always attach a .blend, so we can reproduce

Hi, while we love to hear these ideas, this is not the right place for them. This website is mainly used to track bug reports and not feature requests. But luckly, there are some other nice solutions you can take, so please use one of the other forms of communication listed below:

Can confirm this, this is an issue in undo.
When bmain->is_memfile_undo_written is false (happens when going into fullscreen) then a new "MemFile Internal" UndoStep is pushed to the stack as well as step_init on the stack gets null.
If thats the case -- plus the name thats passed to BKE_undosys_step_push_with_type() is null (which can happen, but thats not always harmful) the crash happens in BLI_strncpy.

I can only get it to fail with new depsgraph.

I believe this is caused by an extreme value for bump (causing the normals to point in all kinds of directions). Or I'll quote @Brecht Van Lommel (brecht) from T54498:

Could you please also upload the .lwo?

You have a couple of UVs with undefined positions (NANs) in "UVMap" ("UV1" doesnt have these and exports fine)
Can be checked with this script:

Confirmed, having a closer look now...

confirmed on first sight, studying bridge_loop_pair now.

can confirm descibed behaviour (even though this might be a known limitation)
first note: ui_apply_but() is called twice when over the 'X'

The particular value of 4.875 is dependent on the setting of your ColorManagement Display device
This has been reported before in T40131
I'll merge this into T41287 as well and do some more reading up on this matter.

(btw, this seems to already been fixed in current 2.8 branch)

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.

thx for the report, afaict, this is already fixed by rBfb3528d08870, thx @Campbell Barton (campbellbarton)!

afaict, this is also fixed by rBfb3528d08870, thx @Campbell Barton (campbellbarton)!

afaict, this is also fixed by rBfb3528d08870, thx @Campbell Barton (campbellbarton) !

as @Bastien Montagne (mont29) said, we will archive this then as 'known bug, won't fix in 2.7x, will be fixed in 2.8'

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

Since @Manish Tyagi (megantus) didnt report back here and @Roy (Royov) reported an issue resolved, I'll close this as resolved

OK, if I assign to you then?

OK, thanx for checking back. Agree with your analysis (was just pointing out that this has nothing to do with rBAdc6704ab4 and reverting rBA8ca82b7d would actually fix this report -- but of course reintroduce other issues).
We'll just let this open then see how to fix both Global/Local AND view layers when time comes... OK?

Can confirm this, issue in undo. This can probably be merged into T54578, T54553?

@nBurn (nBurn) : thats actually caused by rBA8ca82b7d [not rBAdc6704ab4], mind having a look?

actually this has to do with this fellow

@Campbell Barton (campbellbarton) : is that something to be investigated further?

Checked a bit on this, but probably have to pass this on to @Sergey Sharybin (sergey)

This is true for any pointer property afaics [changing any of these wont register in undo on first sight], so nothing particular to the Node editor.
This might be a known limitation, or a design decission, needs further clarification...

I made a change here in rBAdc6704ab4 but also cannot reproduce, could you provide a simple .blend file and exact steps to reproduce the issue?

Hi @Rob Hughes (RevDr) and thx for the report,
as a first note: I can confirm the issue and also that your code fixes it (I tested without stroke->brush_init -- but needs more research...)

I think this is intended behaviour.

Similar to T54553 (py API doesnt set TextUndoBuf), similar thing as D3139 will fix the crash here, too:

caused by rBad1ea9a427e3543a43ca2589f87f0c94b9be03ca

Cursor X-Value can only be seen (is reflected in the green line) when the Graph Editor editor is in Drivers mode, otherwise (F-Curve mode) the green line is hocked up to frame_current.

@Brecht Van Lommel (brecht) : I think we can close this then?

sorry for coming back late on this, since some new information is given, I'll re-check in a bit...

since some new information is given, I'll re-check this in a bit...

Sorry for getting back late at this, but could you upload a simple.blend file demonstrating the issue [also upload the font in question, please].
Or maybe just show a screenshot of what errors exactly you are seeing?

since some new information is given: will reset to "Needs Triage" and check again in a bit

since some new information is given, I'll reset to "Needs triage", will check in a bit

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

Hm, it's running against the stack size limit, see here

forgot to claim this for the time being, will pass on if I cannot find a solution within reasonable time...

Just a first note: can confirm this.

please dont claim the task youself, this will most likely prevent others from looking at it

@Gottfried Hofmann (gottfried) : could you check official 2.79b release? (seems like it's fixed / cant get it to freeze there)
can confirm the freeze in 2.79a, havent looked further though

@alexis echemendia (aluba) : this is current master, right? [2.79b official release wont crash here...]

I'm afraid such a thing is not implemented (yet) for each menu, closest thing is the Repeat Last as you already mentioned.
Of course this could be implemented [without checking in depth I would even say as an addon], just hasnt been done afaik.

Confirmed [wont happen in e.g. the DopeSheet though...]
Will look into it tomorrow

I can confirm only with loop_slide option enabled (seems like without that option behaviour didnt change?)

OK, thanx for reporting back, closing then

Working fine here.
Does this happen when you start Blender in factory settings (--factory-startup commandline option or do File > Load Factory Settings)?
(this will ensure whether this is a userpref or addon issue or not)

OK, actually group indices seem to update/change on save then reload...
Hm, apparently that has always been the case [checked back to 2.74]

possibly related T53628 (but that needs reconfirmation once a solution is found here)

Can confirm this, looking a little further now, but if that gets a timesink, I might need @Bastien Montagne (mont29) to have a look here

Sorry, didnt notice the Material was still linked with data.

OK, I think we can close this then

Just noticed me using the wrong emoticon here, sorry. This wasnt meant to read "I'm annoyed that I dont have commit rights", it's more like "sorry to bother you, I'm afraid I dont have commit rights". Note to myself: dont use those emojis anymore...
Has changed though today, can push tomorrow...

Unpack textures with method original location. You will get an error.

In case of the HDRI, this is the main error we have to investigate here

@Thomas Dinges (dingto): if no doubts remain: could you commit maybe? (dont have commit rights :/)

Can confirm this. I guess D3138 will do it, but kindly asking @Thomas Dinges (dingto) to doublecheck... (as I am not 100% sure this wont have other consequences - could not really find any on first sight though)

Glad to hear this, and thx for your testing!
I will close this then. You can still keep us posted with updates or reopen if you found a bug (e.g. with bundled addons) causing this. [I'm also interested in what might have caused this]

You can remove the invalid paths in the dopesheet (the ones underlined in red). Note I did this manually for all of them, but you can write a script as well... @Joshua Leung (aligorith) : wasnt there even an operator for this? (cant find it right now though)

Hi there,

Sorry, wasnt aware that its not just the legs but the whole character that needs to be separated from eyes/mouth, so it's more like: