[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#717911: marked as done (xfwm4: Window menu is not accessible using keyboard)

Your message dated Thu, 10 Nov 2022 18:52:50 +0500
with message-id <CANeoM1G4ZfrJNC3bNjd1JZcUT6Am0z6-9OEMK9bJp492WesrMw@mail.gmail.com>
and subject line Re: xfwm4: Window menu is not accessible using keyboard
has caused the Debian Bug report #717911,
regarding xfwm4: Window menu is not accessible using keyboard
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
717911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717911
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xfwm4
Version: 4.8.3-2
Severity: normal

Hello Debian patrons! :)

Some applications, for exaple Opera and Chromium, are able to operate in
mode when window borders are hidden.  While visually it can be appealing
and can save screen space, current problem is that in this mode Alt-Space,
which normally opens generic window menu, does not have any effect.

This makes it impossible to coontrol window via keyboard-only (Alt-Space
and menu commands) in conjunction with this mode.

What makes it a little bnit stranger is that Alt-Up shortcut which I have
set in Window Manager settings to "Maximize window vertically", works fine
in this mode, while Alt-Space, which is listed in the same settings does
not have any effect.  Is it that these two browsers specifically catch
this shortcut?  (I have no idea why would they do so...)

To turn on this mode in Opera, right-click areae with tab names and
disable "Show Border".  In Chromium, this mode is on by default.


-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xfwm4 depends on:
ii  libc6                     2.13-38
ii  libdbus-glib-1-2          0.100.2-1
ii  libgdk-pixbuf2.0-0        2.26.1-1
ii  libglib2.0-0              2.33.12+really2.32.4-5
ii  libgtk2.0-0               2.24.10-2
ii  libpango1.0-0             1.30.0-1
ii  libstartup-notification0  0.12-1
ii  libwnck22                 2.30.7-1
ii  libx11-6                  2:1.5.0-1+deb7u1
ii  libxcomposite1            1:0.4.3-2
ii  libxdamage1               1:1.1.3-2
ii  libxext6                  2:1.3.1-2+deb7u1
ii  libxfce4ui-1-0            4.8.1-1
ii  libxfce4util4             4.8.2-1
ii  libxfconf-0-2             4.8.1-1
ii  libxfixes3                1:5.0-4+deb7u1
ii  libxrandr2                2:1.3.2-2+deb7u1
ii  libxrender1               1:0.9.7-1+deb7u1

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.36.1-1
ii  xfwm4-themes     4.6.0-3

Versions of packages xfwm4 suggests:
ii  xfce4  4.8.0.3

-- no debconf information

--- End Message ---
--- Begin Message --- 
Source: xfwm4
Source-Version: 4.12.0-1

This most likely was a problem with GTK3 CSD windows. Support for it
was added in 4.12.0.

--- End Message ---
Reply to: