In previous versions of Gnome I assigned the left super key (windows button) to the "run terminal" command via the System → Preferences → Keyboard Shortcuts application. This seems not to work properly. The default shortcuts work correctly, but defining a shortcut for one of the disabled ones gives a "The text was empty (or contained only whitespaces)" error. Assigning the super key to run_command in gconf editor and defining the run_command as gnome-terminal works, though. Reproducible: Always Steps to Reproduce: 1.Open System → Preferences → Keyboard Shortcuts 2.Assign a shortcut to any of the disabled commands (e.g. run terminal) 3.Try the shortcut Actual Results: You'll get a dialog telling you "Text was empty (or contained only whitespaces." Expected Results: Startup Gnome-terminal Happened after upgrading Gnome to the stable 2.24 version that is in portage. Still happens after libxklavier 3.8 was replaced by 3.6
Just guessing here, but it could be the X server's fault. We could revisit this once people are using Xorg 1.5.3. Christian, in the mean time, it'd be great if you could head over to bug #251832 and upgrade your whole Xorg stack to what will eventually be stable in a week or two? That would definitely help us see which package we should blame. Thanks
(In reply to comment #1) > Just guessing here, but it could be the X server's fault. We could revisit this > once people are using Xorg 1.5.3. > > Christian, in the mean time, it'd be great if you could head over to bug > #251832 and upgrade your whole Xorg stack to what will eventually be stable in > a week or two? That would definitely help us see which package we should blame. > > Thanks Good guess, that solved it. Upgraded to xorg 1.5.3. now without any issues. Thanks >
Thanks for the follow up, Xorg 1.5.3 is going stable as we speak, so indeed we can close this bug. Cheers
