Launchpad has imported 11 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=474635.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-12-04T18:23:03+00:00 Christopher wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/0 ------------------------------------------------------------------------ On 2008-12-22T17:30:58+00:00 Tom wrote: Annoyingly, I also get this with the "up" arrow on my Lenovo T60. metacity-2.25.55-1.fc11.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/12 ------------------------------------------------------------------------ On 2008-12-22T19:56:04+00:00 Tom wrote: (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. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/13 ------------------------------------------------------------------------ On 2008-12-22T23:13:22+00:00 John wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/14 ------------------------------------------------------------------------ On 2008-12-23T03:09:27+00:00 Tom wrote: (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. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/15 ------------------------------------------------------------------------ On 2008-12-23T03:55:24+00:00 John wrote: 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" Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/16 ------------------------------------------------------------------------ On 2008-12-23T03:57:57+00:00 John wrote: My arrow keys are being recognized normally by bash in a ctrl-alt-2 console. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/17 ------------------------------------------------------------------------ On 2008-12-24T15:24:27+00:00 John wrote: 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? Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/18 ------------------------------------------------------------------------ On 2008-12-24T15:44:55+00:00 Yanko wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/19 ------------------------------------------------------------------------ On 2009-06-09T10:07:35+00:00 Bug wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/25 ------------------------------------------------------------------------ On 2009-09-10T12:29:48+00:00 Yanko wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/305695/comments/26 ** Changed in: metacity (Fedora) Status: Fix Released => Won't Fix ** Changed in: metacity (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/305695 Title: Jaunty doesnt allow screenshots getting "No command 33 has been defined" error with printscreen Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Status in metacity package in Fedora: Won't Fix Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/305695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
