GNOME Bugzilla – Bug 649451
network-manager left-click menu doesn't always show in multi-head setup
Last modified: 2018-05-02 15:05:55 UTC
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/713922 gtk is version 2.20.1-0ubuntu2, I run an uptodate Ubuntu lucid system I've made a best effort at guessing which component and product to file this under but I'm sure I've got it wrong. I kindly ask somebody more knowledgeable than me to put it in the right category. Let me also state that I would have liked to try this with a more recent version of gtk, but natty and beyond does not use Ubuntu Netbook Edition as the Window Manager any longer but has replaced it with unity. I think unity is sufficiently different to make it impossible to draw many conclusions from it that are applicable to my situation. For what it's worth, the problem is not reproducible with Unity. That being said, I'm upstreaming this from https://bugs.launchpad.net/bugs/713922 as I was told to. My netbook is connected to an external display at times. I run lucid Ubuntu netbook edition as my window manager. A left-click on the network-manager applet does not produce a visible menu under the following conditions. 1) dual-head and internal display below external display 2) long list of entries make the menu overflow I get a long list of entries for example when I have wifi, ethernet and GSM active at the same time. When the list in the network-manager applet becomes long enough to hit the lower edge of the screen it apparently overflows incorrectly in such a way that the whole menu becomes invisible (except for a bar of about 1 pixel height just above the applet). The same long list works fine when the internal display is on top of the external display, for what it's worth.
Can you still reproduce this? If network-manager does not exhibit it, we would need to create a test case.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/359.