Dapper: ALT-F2 no longer brings up run dialog, ALT-F1 no longer selects Applications menu

Quite strange, it works on my computer (up-to-date dapper).

Didn't you redefine these shortcuts somewhere ?

I did not redefine these shortcuts anywhere. Where can I check?

system -> preferences -> keyboard shortcuts

have you installed a new window manager?

On Tue, 2006-05-16 at 11:55 +0000, sam tygier wrote:
> system -> preferences -> keyboard shortcuts
>
> have you installed a new window manager?

No new window manager. Look at the screenshot, the shortcuts are still
set...

screen of shortcuts

setting to gnome-panel, though it could be metacity.

On Tue, 2006-05-16 at 14:31 +0000, sam tygier wrote:
> setting to gnome-panel, though it could be metacity.
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => gnome-panel

tres weird man. All the other metacity key bindings work except for
alt-f[12]

The problem with this one (for some reason) is that my gtkrc-2.0 was using the Qt theme, obviously set by KDE.

The workaround is to remove this file...

Fixed as far as I am concerned I suppose... But it would be quite annoying for those that want to use the Qt theme in gnome. All 5 of them.

another bug of gtk-qt-engine probably, reassigning

Quite strange in fact since nobody else reported this...
If it was a gtk-qt-engine bug, we should have gotten dozens of complains about this...
sohail, I'd be interested to know if edgy version of gtk-qt-engine (0.70) reproduces the issue for you, since it is known to correct lots of issues.

Hi,

As of today, the problem still occurs. Here is my gtkrc-2.0 (I am working in gnome):

# This file was written by KDE
# You can edit it in the KDE control center, under "GTK Styles and Fonts"

include "/usr/share/themes/Qt/gtk-2.0/gtkrc"

style "user-font"
{
        font_name="Sans Serif 9"
}
widget_class "*" style "user-font"

gtk-theme-name="Qt"
gtk-font-name="Sans Serif 9"

I've verified that removing this file and logging in again fixes the problem..

Subscribing kubuntu-team.

Good evening,

I am wondering if this is a bug that we can close now that Dapper is no longer supported? Or are you still having problems with this?

Jonathan

Jonathan Jesse wrote:
> Good evening,
>
> I am wondering if this is a bug that we can close now that Dapper is no
> longer supported? Or are you still having problems with this?
>
> Jonathan
>

Hi Jon,

Please close it.

--
Sohail Somani
http://uint32t.blogspot.com

Marking this bug as fix released based on the comments of the last poster.

Jonathan