Version: 2.76
Symptoms: Blender crashes when one types in a unicode character in an object name.
How to recreate: Load the default scene, start renaming an object, and in the middle of it type "é". Crashes consistently for me.
Description
Description
Event Timeline
Comment Actions
This did not reappear in my environment.
my environment:
blender v2.76 (sub11)
windows 10 pro 64bits
GeForce GTX 960+GeForce GT 730
Comment Actions
Can't redo this, however its possible that somehow your keyboard is entering a different character then the one which is added from copy-pasting from the web browser.
- What is the exact name you type?
- What operating system are you running?
- Does this happen with 2.77 test builds? (http://download.blender.org/release/Blender2.77/)
Could you do some more tests?
- Does this happen when copy-pasting the character (from this report for example).
- Does this happen in any text field. (file selector (save as) / render-output-path / metadata-note... for eg).
- Does this happen when naming an object from the Python Console fullscreen?: Shift-F4, Ctrl-Up and enter... C.object.name = "AéA"
- If changing the name from a fullscreen PyConsole works, try UnMaximize the PyConsole (Ctrl-Up again). An check if this crashes showing the button in the Properties editor.
Comment Actions
Interesting.. I did some more testing. It happens 100% of the time when I run blender normally - that is, through optirun (my driver is Nvidia/Bumblebee, so one uses "optirun <programname>" when they want 3d accel). But when I run it without optirun (aka, no 3d acceleration), it doesn't crash on unicode characters, ever. I can't imagine what the connection between 3d acceleration and unicode would be (blender is otherwise quite stable), but it's 100% consistent. And it would explain why you're not seeing the problem, because you're probably not using Bumblebee.
When I optirun other programs, they don't have problems with unicode - only blender.
I ran optirun blender through a console and there's an error when blender crashes:
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 101 (X_GetKeyboardMapping) Value in failed request: 0x0 Serial number of failed request: 459 Current serial number in output stream: 459
op^C
As for the questions above:
- The exact name is irrelevant, it happens with any name. But for example, renaming "Cube" to "Cubé"
- My environment:
Linux version 4.3.4-200.fc22.x86_64 (mockbuild@bkernel02.phx2.fedoraproject.org) (gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC) ) #1 SMP Mon Jan 25 13:37:15 UTC 2016
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)
bumblebee-nvidia-352.63-2.fc22.x86_64
- I haven't tried any test builds
- No, it does not happen if the letter is copy-pasted. Rather strange, that!
- Yes, it crashes in save-as as well
- Yes, it crashes when I type a "é" in the python console as well
Comment Actions
This makes sense then, however I can't redo the error,
Tried to redo the bug by sending bad key-stroke events to Blender using http://www.doctort.org/adam/nerd-notes/x11-fake-keypress-event.html (and swapping out XKeysymToKeycode args, as well as commenting it and testing various invalid values).
All I could get was an error:
Bad keycode lookup. Keysym 0x0 Status: XLookupNone '' 0x7ff29d50a780 0x7ff29d6bacc0
As far as I can see this is a bug in Bumblebee since theres no reason it should be adjusting your keyboard config, best report the error there.
Closing.