Version: 4.0.0 (using KDE 4.4.2) OS: Linux I press f11 and says 'The key sequence 'F11' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered.' -- I resolve the ambiguity, but somehow in about a minute it forgets about it, and again, f11 gets ambiguous again. Reproducible: Didn't try OS: Linux (i686) release 2.6.32-22-generic Compiler: Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
I wonder what we're doing wrong to trigger this. The reset is done when switching to another document. Also F12 is not ambigous, its bound to a kdev-action only.
I was able to reproduce this with: f9 (show folding markers vs debug launch) f10 (dynamic word wrap vs step over) f11 (show line number vs step into) I solved the ambiguity by assigning the shortcuts to the debug related actions, but however, they happened to be ambiguous (even in the same debug sessions)
Works fine for me.