Bug #60472 reported by Paul Sladen on 2006-09-14
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Ubuntu Desktop Bugs

Bug Description


FocusOut event, serial 29, synthetic NO, window 0x3000001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 29, synthetic NO, window 0x3000001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 29, synthetic NO, window 0x3000001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 29, synthetic NO, window 0x0,
    keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0


Paul Sladen (sladen) wrote :


Paul Sladen (sladen) wrote :


 $ 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.

Paul Sladen (sladen) wrote :

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

does not fix it.

Sebastien Bacher (seb128) wrote :

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

Paul Sladen (sladen) wrote :

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">
             <entry name="switch_to_workspace_2" mtime="1147794842" type="string">
- <entry name="switch_to_workspace_1" mtime="1147878577" type="string">
- <stringvalue>0x41</stringvalue>
- </entry>

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.

Paul Sladen (sladen) wrote :

That modification time comes out as:

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


Sebastien Bacher (seb128) wrote :

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

Changed in metacity:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Paul Sladen (sladen) wrote :

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

Sebastien Bacher (seb128) wrote :

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

Paul Sladen (sladen) wrote :

Sounds good. Closing for now.

Changed in metacity:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers