Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#65 Disabling menu access key has no effect

Not_ROXTerm
open
nobody
None
5
2014-01-13
2011-10-17
Anonymous
No

I disabled menu access key (F10).
The config file contains "disable_menu_access=1"

Still, pressing F10 pops-up the menu. This is very annoying when in wicd where F10 is the key for saving.

Versions:
roxterm 2.2.2-1
vte3 0.30.0-1
vte-common 0.30.0-1
gtk3 3.2.0-2

(all on both of my Arch Linux 64bit machines)

I notified atsutane, the package maintainer for roxterm in the arch linux repo and he got the same problem.
I had no time to look into the source code or check if any version downgrade of the mentioned packages helps to avoid this bug.

If you need more info or anything else I can do, just let me know.

Discussion


  • Anonymous
    2011-10-17

    Oh, I can log in using my Google account. Great.

     
    Last edit: Anonymous 2014-05-11
  • Tony Houghton
    Tony Houghton
    2011-10-17

    I can't reproduce the problem, but I'll look into it more deeply later. You should be able to work around it by keeping the menu bar hidden.

     

  • Anonymous
    2011-10-19

    Noticed this problem (also on an Arch x64 machine) too, having the same versions as Jan-Erik mentioned. Menu bar is hidden too.

    I tried the git version from AUR but it fails:
    /tmp/packerbuild-1000/roxterm-git/roxterm-git/src/roxterm-build/install-sh: ./Help/lib/roxterm_logo.png does not exist.

    That is probably a mistake by the packager in the AUR.

     

  • Anonymous
    2011-10-19

    With some tinkering I got the package compiled, but the problem persists. The about windows shows 2.2.2.1~g0fd4275 .

     

  • Anonymous
    2011-10-23

    Tried it. Still the same. The menu opens when I press F10, but it also prints "1~ " in my console.

     
  • Tony Houghton
    Tony Houghton
    2011-10-23

    Is the appearance of these characters new since I made the changes? And does wicd recognise it/them as F10? Please also try gnome-terminal. I'm doing this pretty much the same way that does. It could be a GTK+3 bug.

     

  • Anonymous
    2011-10-23

    Yes, the appearance of those characters is new.
    Yes, wicd recognizes it as F10.
    Yes, gnome-terminal has the same problem (even with the "1~" thingy)

    So in conclusion: Probably a gtk3 bug... dammit.

     
  • Tony Houghton
    Tony Houghton
    2011-10-23

    I think it's a GTK+3 issue then, but it might be worth checking the GTK+2 version of roxterm too. It could be one of three things:

    Something's changed between GTK 3.0 and 3.2 and neither I nor the gnome-terminal developers have kept abreast of that. I'm reluctant to upgrade to 3.2 until it enters Debian unstable, at the moment it's "experimental".

    A bug in GTK 3.2.

    A problem with an Arch patch for GTK3.

     
  • Tony Houghton
    Tony Houghton
    2012-02-12

    I'm seeing this problem now, but only in the GTK3 version. gnome-terminal has the same problem so I think it's a GTK3 bug. I'll post a report in GNOME's bugzilla.

     


Anonymous


Cancel   Add attachments