Spacebardoesnotworkafterupgradetoedgy

Shift+space_does_insert_a_space_as_expected.

Running:

 $ X &
 $ DISPLAY=:0.0 xterm

allows [space] to work normally. It appears to be related to something loaded later. The same applies to 'gdm'; the problem is presumbly something in GNOME; eg. the keyboard utilities.

  $ sudo /etc/init.d/gdm stop
  $ rm -r ~/.gnome*
  $ pkill -u $USER

does not fix it.

gnome-desktop is the "About GNOME" dialog a .desktop parsing library. The GNOME keyboard utilities use gconf settings and apply to the user session, not to gdm. Probably an xorg issue, reassigning

After a couple of hundred loops of 'killall5 -9' and re-login, the following got my space bar back:

--- ~/.gconf/%gconf-tree.xml~ 2006-09-15 17:26:47.000000000 +0100
+++ ~/.gconf/%gconf-tree.xml 2006-09-16 00:22:57.000000000 +0100
@@ -833,13 +833,10 @@
     <dir name="metacity">
       <dir name="global_keybindings">
             <entry name="switch_to_workspace_3" mtime="1147794841" type="string">
               <stringvalue>disabled</stringvalue>
             </entry>
             <entry name="switch_to_workspace_2" mtime="1147794842" type="string">
               <stringvalue>disabled</stringvalue>
             </entry>
- <entry name="switch_to_workspace_1" mtime="1147878577" type="string">
- <stringvalue>0x41</stringvalue>
- </entry>
           </dir>

It had been set of the access-key for switching to the first virtual desktop in metacity...

I do not recall having performed his change manually.

That modification time comes out as:

  >>> time.ctime(1147878577)
  'Wed May 17 16:09:37 2006'

*boggle*.

Are you sure you have not played with gnome-keybinding-properties or gconf-editor and might have changed that value? Nobody else mentionned a such issue and it's weird that the window manager would have go and do that change itself

If I had, it's certainly a bug that my space-bar hadn't stopped working 4 months earlier...

That might be a bug fixed now then. If you or something else get the issue again or figure what to do we might be able to do something about it, but without any other information than the window manager respecting an user setting to gconf there is not a lot to do

Sounds good. Closing for now.