Keyboard problems in Blender

Bug #1248899 reported by Vaclav Cermak
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Unity
Confirmed
Undecided
Unassigned
unity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After upgrade to 13.10 I have problems with keyboard in Blender.

Sometimes keyboard is not working for Blender at all (but works outside Blender).

Sometimes I cannot switch layers with number keys.

And pressing somw keys twice in a short time (for example yy when I wan't to lock local y coord) does not work as in 13.04.

I'am unable to track when all theese things happen, however (besides the last one, which happens everytimes).

Tags: bot-comment
Revision history for this message
Maris (raptor59) wrote :

13.10, 64bit here.

This might be something to do with Unity, since if you switch to Gnome this issue is no more affecting me.

In Blender it is reproducable like this:
1) create a cube and select it in object mode;
2) now hit on keyboard G (for moving) and Z Z (yes, two Z's in a row without pausing in between)

What should happen at this point is you should be able to move a cube along its local Z axis, however you will notice that after hitting Z two times it shows the local Z axis only for fraction of a second and then cancels it allowing you to move object freely.

The only way to get around is make a pause in between these double Z keys. Like one second or something like that. Then it works.

Same story about all other shortcuts where you are required to hit one key two times in a row.

Things that didn't help: reinstalling unity, messing in all possible ways with keyboard settings, universal access bounce option on/off. So basically I've ran out of ideas.

Can confirm that nothing like that happens in 13.04, 64bit.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1248899/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Vaclav Cermak (disnel) wrote :

Chaged target to project Unity because it seems to be Unity related.

affects: ubuntu → unity
Changed in unity (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.