Jaunty doesnt allow screenshots getting "No command 33 has been defined" error with printscreen

[Luca Falavigna]

Binary package hint: metacity

If I press STAMP key to grab a screenshot of my desktop (or ALT+STAMP for the current window), a Metacity popup appears saying "No command 33 has been defined." (for STAMP) or "No command 34 has been defined." (for ALT+STAMP). I'm running Jaunty, metacity version 1:2.25.13-0ubuntu2.

This effects the latest Ubuntu Release Jaunty

On regular PC's, the PrintScreen key is similarly affected. System->Preferences->Keyboard Shortcuts shows "Take a screenshot" linked to the "Print" shortcut.

[Note: Enough people have confirmed this already - please indicate it's affecting you via the "This does not affect me (Change)" link rather than placing a comment, so we can focus discussion towards attaining a fix.]

[Workaround]
Applications->Accessories->Take a Screenshot
-or-
gnome-screenshot --interactive

[Christopher (christopher-redhat-bugs)]

Description of problem: Hitting the 'Print Screen' key on my keyboard results in a Metacity popup box that says "No command 33 has been defined."

Version-Release number of selected component (if applicable):
metacity-2.25.34-1.fc11
also occurs in metacity-2.25.8-4.fc11

How reproducible:
every time

Actual results:
pop up box with warning

Expected results:
should take me to the screen shot window

[Marnanel Thurman (marnanel)]

Thank you for reporting this bug. Can you paste the output of typing

dpkg -L metacity-common

into a terminal, please?

[Luca Falavigna (dktrkranz)]

Here it is.

[Kyle M Weller (kylew)]

I confirm this bug in Jaunty Jackalope, I am unable to take screenshots :(

[Marnanel Thurman (marnanel)]

Thank you. What does

gconftool -g /apps/metacity/keybinding_commands/command_screenshot

show you?

[Luca Falavigna (dktrkranz)]

It returns me: No value set for `/apps/metacity/keybinding_commands/command_screenshot'

[Marnanel Thurman (marnanel)]

Can you look in the file /usr/share/gconf/schemas/metacity.schemas and tell me the default value for that key? I just built the jaunty package from source and I have

    <schema>
      <key>/schemas/apps/metacity/global_keybindings/run_command_screenshot</key>
      <applyto>/apps/metacity/global_keybindings/run_command_screenshot</applyto>
      <owner>metacity</owner>
      <type>string</type>
      <default>Print</default>
...

[Luca Falavigna (dktrkranz)]

    <schema>
      <key>/schemas/apps/metacity/global_keybindings/run_command_screenshot</key>
      <applyto>/apps/metacity/global_keybindings/run_command_screenshot</applyto>
      <owner>metacity</owner>
      <type>string</type>
      <default>Print</default>
      <locale name="C">
        <short>Take a screenshot</short>
        <long>The format looks like &quot;&lt;Control&gt;a&quot; or &lt;Shift&gt;&lt;Alt&gt;F1&quot;.

[Krzysztof Z (zboralski-k)]

Confirmed - I also have the same error when I press PrtScr button on JJ 9.04 :\

[Claudio Moretti (flyingstar16)]

Confirmed.
Alt+F2 - "gnome-screenshot --interactive" is the only way I can display the "stamp-related" window. It works, but not with the Stamp key, even if it is defined in System - Preferences - Keyboard shortcuts

[Vedran Rodic (vrodic)]

I can also confirm this,

In addition, probably because i use a usb attached keyboard (on a Cypress USB2PS2 converter), the screenshot functionality is invoked many times, and my PC dies from the heavy swapping (tested on livecd 20081218.1).

[Tom (tom-redhat-bugs)]

Annoyingly, I also get this with the "up" arrow on my Lenovo T60.

metacity-2.25.55-1.fc11.x86_64

[Tom (tom-redhat-bugs)]

(In reply to comment #1)
> Annoyingly, I also get this with the "up" arrow on my Lenovo T60.
>
> metacity-2.25.55-1.fc11.x86_64

Reverting to metacity-2.25.34-1.fc11 fixes it.

[John (john-redhat-bugs)]

Reverting to metacity-2.25.34-1.fc11.x86_64 didn't work for me.

All my "inverted T" arrow keys are broken, but just "Up" opens the "No command 33 ..." message.

[Tom (tom-redhat-bugs)]

(In reply to comment #3)
> Reverting to metacity-2.25.34-1.fc11.x86_64 didn't work for me.
>
>
> All my "inverted T" arrow keys are broken, but just "Up" opens the "No command
> 33 ..." message.

I had to kill the running metacity process after doing the rpm downgrade, to start the old one.

[John (john-redhat-bugs)]

Weird. I tried again: After downgrading the rpm and leaving X I looked for any running metacity processes, there weren't any. To be sure, I rebooted, but
metacity-2.25.34-1.fc11.x86_64 still gives me "No command 33...." for "Up" arrow.
As does metacity-2.25.55-1.fc11.x86_64.

I have a Logitech USB keyboard which is being recognized as a "BTC USB Multimedia Keyboard" Does that sound right?

(II) XINPUT: Adding extended input device "BTC USB Multimedia Keyboard" (type: K
EYBOARD)
(**) Option "xkb_rules" "evdev"
(**) BTC USB Multimedia Keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "pc105+inet"

[John (john-redhat-bugs)]

My arrow keys are being recognized normally by bash in a ctrl-alt-2 console.

[John (john-redhat-bugs)]

Seems to be fixed today!?! Still using metacity-2.25.55-1.fc11.x86_64
Perhaps this was fixed by the Xorg-x11-server updates?

[Yanko (yanko-redhat-bugs)]

Created attachment 327820
Re-add some missing defaults

The xorg update would have fixed the up arrow problem. I don't think the command 33 issue here is related. I think this patch will fix it, at least temporarily until upstream figures what to do about it.

[Alexia Death (alexiade)]

Also present here.

[damip (damipator)]

I can also confirm the bug.

[Bryce Harrington (bryce)]

I think there's enough confirms now (I am seeing it myself). Please instead use the "Affects me too" link to mark yourself affected.

[Bryce Harrington (bryce)]

I tested the workaround on the redhat bug, but couldn't get it to work.

crevette suggested the bug is not present in the newer metacity, which he's packaged here, if anyone would like to test:
https://bugs.edge.launchpad.net/ubuntu/+source/metacity/+bug/312522
https://edge.launchpad.net/~bmillemathias/+archive/

[Launchpad Janitor (janitor)]

This bug was fixed in the package metacity - 1:2.25.89-0ubuntu1

---------------
metacity (1:2.25.89-0ubuntu1) jaunty; urgency=low

  * New upstream version (LP: #312522)
    - The maximisation key is a toggle.
    - "Unmaximise" is now called "restore".
    - New thread handling call for gconf
    - Add screenshot commands back which had been removed (LP: #305695)
    - move_to_corner_se keybinding fixed
    - Windows on other workspaces which attempt to present themselves are
    marked as needing attention
    - End the grab op when the user clicks the titlebar
  * patches/011_gnome_482354_attachment_104591.patch:
    - dropped, applied upstream
  * debian/patches/013_drop_Werror.patch
    - updated patch

 -- Baptiste Mille-Mathias <email address hidden> Tue, 30 Dec 2008 21:20:24 +0100

[Bug (bug-redhat-bugs)]

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Yanko (yanko-redhat-bugs)]

The missing defaults bug that was the problem here was fixed sometime between 2.25.55 and 2.25.89. that is before the Fedora 11 release which has 2.26.0. Closing.