Updating D6462: fix T72605 MacOS user permissions: Blender works only in one user account

See T66998

Thanks for the feedback. Closing the ticket.

Can you reproduce it with the wacom unattached or even after uninstalling the driver ?

Do you happen to have a Wacom Intuos attached, or its driver installed?

@Kent Davis (mac4kent) this is a bug tracker, not a discussion forum. I do not have anything to add to this topic.
@Gaia Clary (gaiaclary) please close this ticket, if you think this issue is solved.

Ah gosh - you actually need to go to https://blender.chat first and then select the support channel. Always nice to find a new unrelated bug :-).

@MICHAEL JEAN BAPTISTE (fhqgroup) please stay on topic. if you cannot find the collada import in blender, please ask on https://blender.chat/channel/support or file a separate ticket on the bugtracker.

I think this is a OSX specific bug. Using Instruments.app I can see the function SCCompileShader using all the cpu resources. I tried to track it down to a specific setup or shader, but I was not yet able to get to the bottom of it. The problem could be the same as to point 5 on https://blog.jimmymakesstuff.com/2017/02/a-very-peculiar-osx-opengl-sdl2-bug.html . Maybe someone can give me a hint how to get to the bottom of it.

This has been reported before, see T72015: Crash on startup (TBB related).

Then juste paste the "pastenumber" here, like that: P1195

sorry I meant "Can you start one after the other, replicate the error,...". Do all four of them give the same debug_log ? (after each run you need to save it somewhere)

in the Blender folder should be 4 different *.cmd files. Can you start one of the other, replicate the error, paste debug_logs to https://developer.blender.org/paste/ and link them to this ticket ?

Not sure this is a bug. Can you upload a picture of what you mean ?

Thank you for the feedback.

Can you reproduce it with the latest version from https://builder.blender.org/download/ ?

*update, just re-tried mapping settings within the wacom settings and it's working now.

This report does not contain all the requested information, which are required for us to investigate the issue.

yes, please https://developer.blender.org/paste/ the crash report and link to this ticket.

Ok. You can then mention it here like that: P1193

can you please provide the info I asked above and also https://developer.blender.org/paste/ the output of ls -al /Applications/Blender* ?

Hi, can you https://developer.blender.org/paste/ the error you get ?

Hi, can you start blender from command line and see what the error is ?
Maybe https://developer.blender.org/paste/ the log from your admin and non admin account.

There was a fix lately. Can you reproduce it with the latest from https://builder.blender.org/download/ ?
On a side note: please use the Help>Report a Bug Menu when you file a bug. This adds a lot of useful info for triaging.

Moi, can you https://developer.blender.org/paste/ the backtrace ?

Thank you for the feedback. Closing the ticket.

I can not reproduce this on osx 10.14.6. Can you reproduce it with the latest blender from https://builder.blender.org/download ?

Just rename ~/Library/Application Support/Blender/2.81 to ~/Library/Application Support/Blender/2.81_backup, start Blender (do not import the previous configuration) and see if you still can reproduce the error. Afterwards reverse the rename and you'll get your custom configuration and installed addons back.

I can not reproduce it on osx 10.14.6.
Can you reproduce it after renaming ~/Library/Application Support/Blender/2.81 and making sure there are no custom shortcuts in apples system preferences ?

convert all gl_FragColor variables to FragColor

Not sure why this won't show up here: D6424

the name of the commit should be:
fix T72331: File Output Node in compositing, all socket inputs have the same name in Python

Closing it for now.

Gosh. Your right. Sorry for the noise.

Thank you for the feedback. Closing the ticket.

@Clément Foucault (fclem) I can still reproduce it with this file:

the fix for that is waiting for a code revision: D5076 . @William Reynish (billreynish) can you give it a look?

Can you reproduce it with 2.81a and/or latest from https://builder.blender.org/download/ ?

Can you reproduce it with 2.81a and/or latest from https://builder.blender.org/download/ ?

I guess you are running on an almost 9 year old laptop. If you have a second better graphic card, try enabling it in the preferences when you work in blender.

If the function keys in preferences is gone I guess this bug is resolved. Please reopen the ticket if you can reproduce the problem with the latest blender and please give exact step by step instructions, how to reproduce the problem.

please see T71330

Please see T72209 . I close this for now as I do not think blender can fix this issue. Check the Wacom forums for solutions. If you can reproduce the issue without the wacom driver, just reopen this ticket.

I close this for now as I do not think blender can fix this issue. Check the Wacom forums for solutions.

maybe related to T71635

My bet is you have a wacom driver installed. Can you reproduce the bug with the wacom driver uninstalled ?

If you uninstall the wacom driver, can you still reproduce the error ? I've seen a few hick ups like that due to wacom driver bugs. In other words I do not think this is a blender bug.

Thank you for the feedback. Blender 2.82a works, so I'd suggest to leave this ticket closed for now.

thank you for the report, but that sounds like you are pushing hard to find an edgecase. Feel free to reopen if you think it's a bug.

Can you still reproduce this bug with the latest blender from https://builder.blender.org/download ? If yes, can you update the step by step guide so I can reproduce it ?

Can you reproduce this bug with the latest blender from https://builder.blender.org/download ?

Can you reproduce this bug with the latest blender from https://builder.blender.org/download ?

Merging this into T68577.

This is very hard to reproduce. Closing it for now.

If you reproduce this bug with the latest blender from https://builder.blender.org/download, please reopen this task and paste the text from the crash report to https://developer.blender.org/paste and link the paste here.

I cannot reproduce this bug with:
System Information
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20

I believe this is not a blender problem. Please try with the latest blender from https://builder.blender.org/download and reopen this ticket if this problem still occurs.

Closing because of inactivity. Please try with the latest blender from https://builder.blender.org/download and reopen the ticket if you can reproduce the problem.

Can you commit?

please test with latest blender from https://builder.blender.org/download/ and if you still have this error, reopen this task.

rather duplicate of T71774

duplicate of T71774. Please test your file and if it still fails to import, reopen this task.

duplicate of T71845

@Brecht Van Lommel (brecht) ping

In order to test the patch, make sure to add a weight of 1.0 to all vertices for the "softMod_base" vertex group of the grease pencil object "Suzanne" in the file F7781157 linked in the original bug report T70378. In that way it matches the weights of the bmesh object "Suzanne.001" and should deform accordingly.

I cannot reproduce it. Can you still reproduce it, even with the latest blender version from https://builder.blender.org/download/ ?

It seems this bug solved itself. Please reopen, if the bug appears again.

I can reproduce with:
System Information
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20

maybe related to T70445

Thanks for the report. It's a known limitation. See T68908

I can confirm this bug with version: 2.82 (sub 3), branch: master, commit date: 2019-11-30 17:33, hash: rBf1ac64921b49

Please reopen this ticket, if you encounter the same issue again.

the crashlog is blender specific. So not exactly the same. And yes, the pro render addon could cause these issues. I suggest you start blender with --factory-startup and --debug-gpu-force-workarounds.

According to https://docs.blender.org/manual/en/latest/video_editing/sequencer/properties/proxy_cache.html proxies are encoded as jpeg. jpegs do not have alpha channel.

And please also try 2.82a from https://builder.blender.org/download/ . There were some amd/mac related fixes lately.

Your file works well on my OSX 10.14.6.

@Filip (Filemoner) try 2.82 alpha from https://builder.blender.org/download/
as @Clément Foucault (fclem) said, it's possible 2.81a will be released soon....

This doesn't give much information. If you are familiar with the terminal, please run blender form the terminal and it should give you a crashlog file. If you are not familiar with the terminal, please ask for help on https://blender.chat/channel/support .

can you add a simple step by step info how to crash blender ? maybe add a blend file ?
and can you paste (https://developer.blender.org/paste/) the crash report and link it here ?

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

Can you reproduce with the latest release ? And please add a stop by step instruction how to reproduce.

I can reproduce. See backtrace P1173 and crashlog P1174