We do not handle user support on this tracker, only bug reports. User forums like blenderartists.org or blender.stackexchange.com should be used for that matter.

Hehe, has been done since ages…

This has been fixed I think (at least, cannot reproduce the crash anymore).

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

@Lukas Stockner (lukasstockner97) can you check that one? Thanks.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Indeed…
We do not handle user support on this tracker, only bug reports. User forums like blenderartists.org or blender.stackexchange.com should be used for that matter.

Confirmed, looks like differential changes get re-applied every time…

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).

On the other hand, it allows to extend selection… not sure what is really expected here, but that is more UX design than bug to me, and since we have brand new keymap for 2.8 anyway… @Campbell Barton (campbellbarton) will let you decide here whether this is actually a bug or not.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).

@Sybren A. Stüvel (sybren) care to check? Thanks.

Thanks for the report, but unfortunately that’s most certainly GPU driver issues, we cannot do much here. Besides trying latest and/or older drivers, some hints:

• Try the latest build from our buildbot.
• Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
• Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
• Try to place this dll next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not).

Well, yes, they should, as long as 'Alpha' setting just below blend mode is enabled… Disabling it will lock the alpha channel. Thanks for the report, but no bug here.

Can confirm the issue, but not so sure we can do much about that, this looks to me very similar to the terminator problem in rendering… @Campbell Barton (campbellbarton) or @Brecht Van Lommel (brecht) may know better?

Hmmmpfff… those logs unfortunately do not tell us more… Still cannot reproduce, I really have no clue what’s happening here (besides hinting on recent bleeding-edge distro having changed something in their keyboard handling), guess we’ll have to wait for a dev to be able to reproduce :(

@Clément Foucault (fclem) tagging you here just in case, but imho that’s clearly driver issue, we cannot really keep hundreds of tasks opened on things we cannot do anything about, so will archive. Thanks for the report anyway.

We do not accept bug reports about third-party add-ons not distributed with Blender, those shall be reported to the add-on's author(s).

@Arto Kitula (akitula) not sure what is an 5k IMac… is it even supposed to support Blender? :P

Am sorry but we cannot do much about those issues, they are generally drivers/GPU problems. You can check the following points:

• Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
• Try the latest build from our buildbot.
• Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
• Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
• Launch Blender from the command line with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment).
• Try to place this dll next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not).

That’s not going to help us am afraid… we need to be able to reproduce an issue to investigate and fix it. Also, we require at least OpenGL 3.1 iirc… that whole chromebook is really a bit limited for modern 3D software.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).

Please check existing reports!

Ah actually, we already have that reported…

Change caused by rB18888b7b0c3556d. So would say that is expected behavior, will let @Campbell Barton (campbellbarton) make final decision here though.

Not sure how much of a bug that is… @Campbell Barton (campbellbarton), @Pablo Vazquez (venomgfx) sounds more like an interaction conflict/design issue?

Cannot confirm that here on linux, @Arto Kitula (akitula) maybe you can try it on osx?

Cool, closing then. :)

Still helps to start from last-working-point… Issue is likely in convert-to-curve operation, will check. Also, has nothing to do with cycles, happens with BI materials too.

Ah, yes, it is indeed impossible for Blender to load packed PSD (because underlying library OIIO does not allow reading images from memory, only from files…). You probably loose your images after some undo/redo action.
Thanks for the report, but unfortunately there is not much we can do here, PSD is not an open format, so it’s not really easy to fully support.

Confirmed, @Brecht Van Lommel (brecht) not sure if that’s known limitation or actual bug?

Cannot confirm that here, seems to work OK for me? Hit play, changed some settings in Colorize effect, and it updated immediately in 3DView…

Please try the latest build from our buildbot, think that issue has already been fixed.

Please:

• Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template!
• Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
• Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
• Try to tweak OGL settings in UserPreferences, System tab.
• Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
• Attach as text file here the report generated by Help -> System Info (do not paste it directly in comment).
• Launch Blender from the command line with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment).

Thanks, confirmed.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Cannot confirm that, please:

• Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template!
• Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
• Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
• Try to tweak OGL settings in UserPreferences, System tab.
• Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
• Attach as text file here the report generated by Help -> System Info (do not paste it directly in comment).
• Launch Blender from the command line with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment).
• Try to start in software OpenGL mode (use the blender-softwaregl distributed with official blender, will be slow, but will show whether this is a driver issue or not).

@Brecht Van Lommel (brecht) after CUDA issues, OpenCL one…

Can confirm axis locking is broken indeed, shift-click seems to work OK for me too though.

@Brecht Van Lommel (brecht) I guess that one is for you? ;)

@Campbell Barton (campbellbarton) uh, this is actually again the infamous 'operator started from toolbar has no View3D context info' issue… we already had that bug in other cases, but never actually saw how that was fixed. ;)

Grrr… already fixed that crash once, wonder why it came back… :/

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Crash happens in OIIO library itself, not much we can do here (bsides updating the lib, which is currently ongoing process).

Indeed, something looks wrong in the checker logic, will investigate.

Cannot reproduce here on linux with latest branch. Please add .blend file as already requested!