Am Mittwoch, den 16.01.2013, 11:33 +0100 schrieb Paul Menzel: > Control: found -1 3.4.2-5 > Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=691515 > Control: tags -1 upstream fixed-upstream > Control: affects -1 awesome xmonad
> Am Mittwoch, den 18.07.2012, 04:32 +0200 schrieb [email protected]: > > > I have been experiencing a confusing bug with GTK+3 menus since a big > > testing/sid dist-upgrade around late April / early May. > > > > GTK+3 menus, such as the top-right "personal" menu, or the GNOME > > Terminal right-click contextual menu, sometimes appear at seemingly > > random places, far away from the place where my mouse even triggered > > the menu display. And/or, such menus are sized much smaller than > > expected, e.g. with a height big enough only to hold the scroll-up and > > scroll-down buttons, and zero or one actual menu items out of the menu > > that should be displayed here. Additionally, when this bug arises, the > > behavior of the menus is, well, hard to describe, but rather > > surprising, and requires special ninja skills to handle with the > > mouse. I've personally given up, and now only interact (almost > > blindly) with these berserk menus using the keyboard arrows and the > > Enter key. I expect a bunch of Debian users to be slightly more > > worried than me by this outcome, hence the >normal severity. > > > > I'm running GNOME3 in fallback mode, with the Xmonad tiling window > > manager. I initially did not dare reporting this bug,thinking it > > could be due to some weird custom part of my setup, but thanks to > > DebConf, I learned that Stefano Zacchiroli and Philipp Kern are > > experiencing the same bug with GNOME3 in fallback mode too, but with > > the awesome and i3 window managers, so I eventually dare reporting it: > > as Philipp puts it, "it seems people are most confused about where > > they could report that so there is none". Feel free to reassign to > > whatever package seems more appropriate. > > > > It triggers reliably for Philipp with the following .xsession: > > > > | pkern@spike:~$ cat .xsession > > | export WINDOW_MANAGER=awesome > > | setxkbmap -option terminate:ctrl_alt_bksp > > | pulseaudio --daemonize > > | gpg-agent --daemon --enable-ssh-support \ > > | --write-env-file "${HOME}/.gpg-agent-info" > > | exec gnome-session-awesome > > | > > | pkern@spike:/opt$ cat /usr/local/bin/gnome-session-awesome > > | #!/bin/sh > > | exec gnome-session --session awesome "$@" > > I am also experiencing this problem with a normal awesome session > running GTK applications. I can reproduce it easily starting gedit. > > Short version, try if > > $ xprop -root -remove _NET_WORKAREA > > fixes this for you [1]. It fixed it for me. > Looking for commits in `gdk/x11/gdkscreen-x11.c` > > $ git log -p origin/master -- gdk/x11/gdkscreen-x11.c > > possibly fixing [2], I found the following commit [3] > > commit 2fcbe3a9b44491059170b71f75e07b3b24138c4a > Author: Geoff Reedy <[email protected]> > Date: Wed Jan 9 21:40:04 2013 -0700 > > x11: add missing checks that a hint is supported > > Before acting on any hint that is set by the window manager we > must > first check that the hint is supported by the current window > manager. > Checking that a property has a value is insufficient as it may > have > been set by a previous window manager which did support the hint. > > https://bugzilla.gnome.org/show_bug.cgi?id=691515 > > and looking at the bug report, this is supposed to fix our issue. > (Unfortunately the commit message, does not describe the problem and it > was not that clear. :() > > I am therefore adding that upstream report 691515 [4] as the upstream > one. > > > Cc'ing Julien Danjou, who, I'm told, is often eager to debug > > GNOME3 + awesome issues. > > > > Anything we can do to help debug that? > > Could you please try if building GTK with that patch solves this issue? I applied the patch to the upstream Git tag 3.6.2 and rebuild the package with the `debian/` folder. Everything seems to be fine now. Geoff, awesome work! Though I am still not understanding why checking for `None` was not sufficient as asked in the upstream report. Thanks, Paul > [1] https://bugzilla.gnome.org/show_bug.cgi?id=689030#c6 > [2] https://bugzilla.gnome.org/show_bug.cgi?id=691836 > [3] > http://git.gnome.org/browse/gtk+/commit/?id=2fcbe3a9b44491059170b71f75e07b3b24138c4a > [4] https://bugzilla.gnome.org/show_bug.cgi?id=691515
signature.asc
Description: This is a digitally signed message part
