Closed
Bug 409852
Opened 18 years ago
Closed 15 years ago
Menus appear on wrong screen when using "bigdesktop" mode
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: happyharris.bugzilla, Unassigned)
Details
(Whiteboard: [closeme 2010-09-15])
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071015 SUSE/2.0.0.8-1.1 Firefox/2.0.0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071015 SUSE/2.0.0.8-1.1 Firefox/2.0.0.8
I have Suse Linux 10.2 with and ATI graphics card and two monitors in "Big Desktop" mode. This mode has a large virtual desktop, with each physical monitor occupying a different region on it. Monitor 1 has its (0,0) point at the (0,0) point of the virtual desktop. Monitor 2 has its (0,0) point at the (1600,0) point of the virtual desktop.
If I put my firefox browser in monitor 2, whenever I view a menu, instead of appearing in the correct place, the menu appears on the right hand edge of monitor 1. It is as if firefox is checking the maximum x coordinate that it can put a menu and using the size of the 1 instead of the size of the virtual desktop.
This behavior happens with the main menus (File, Edit, etc.), right click context menus, and "history" menus: (what you see when you start typing in the address bar or a text input on a form).
Firefox is the only application I have that exhibits this behavior. All others seem fine (including an old installation of Thunderbird).
Reproducible: Always
Steps to Reproduce:
1. Set up a Linux box with two monitors in "Big Desktop" mode
2. Put the firefox window in monitor 2 (the one whose origin is not the origina of the virtual desktop)
3. Click on the main File menu
Actual Results:
The menu pops up on the right hand edge of monitor 1
Expected Results:
The menu should pop up in the normal position relative to the File menu header.
Comment 1•18 years ago
|
||
Could you try with an official build (the one you can download from http://www.mozilla.com/en-US/firefox/) and see if you encounter the same issue? (another useful thing would be to test with a nightly from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/)
Information that could be useful here:
* build option used by Suse, available in about:buildconfig of your Suse Firefox
* Do you have Xinerama active? check by running "xdpyinfo |grep -i xinerama"
Component: Menus → Widget: Gtk
Product: Firefox → Core
Version: unspecified → 1.8 Branch
Updated•18 years ago
|
QA Contact: menus → gtk
| Reporter | ||
Comment 2•18 years ago
|
||
I tried with an official build and got the following results which I cannot explain:
1) official firefox-2.0.0.11 - menus in correct place
2) official firefox-2.0.0.8 - menus in correct place
3) original firefox-2.0.0.8 - menus in correct place!!
4) restart machine, then start original firefox-2.0.0.8 - menus in wrong place
5) close firefox, restart original firefox-2.0.0.8 - menus in correct place
running "xdpyinfo |grep -i xinerama" gives the result XINERAMA
about:buildconfig displays
=================================== start ===================================
about:buildconfig
Build platform
target
i686-pc-linux-gnu
Build tools
Compiler Version Compiler flags
gcc gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) -Wall -W -Wno-unused -Wpointer-arith -Wcast-align -Wno-long-long -pedantic -O2 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Os -fno-strict-aliasing -fstack-protector -pthread -pipe
c++ gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -pedantic -O2 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Os -fno-strict-aliasing -fstack-protector -fshort-wchar -pthread -pipe
Configure arguments
--enable-application=browser --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc --mandir=/usr/share/man --includedir=/usr/include '--enable-optimize=-O2 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Os -fno-strict-aliasing -fstack-protector' --with-system-jpeg --with-system-png --with-system-mng --with-system-zlib --enable-default-toolkit=gtk2 --enable-gconf --enable-svg --enable-canvas --enable-xft --disable-freetype2 --disable-installer --enable-static --disable-shared --disable-tests --disable-debug --enable-pango --with-system-nspr --with-system-nss --enable-system-cairo --enable-dbus '--enable-extensions=dbus default' --enable-startup-notification --enable-official-branding
==================================== end ====================================
Comment 3•18 years ago
|
||
(In reply to comment #2)
> I tried with an official build and got the following results which I cannot
> explain:
> 1) official firefox-2.0.0.11 - menus in correct place
> 2) official firefox-2.0.0.8 - menus in correct place
> 3) original firefox-2.0.0.8 - menus in correct place!!
> 4) restart machine, then start original firefox-2.0.0.8 - menus in wrong place
> 5) close firefox, restart original firefox-2.0.0.8 - menus in correct place
This is indeed very strange. Are you sure you you have all your firefox windows closed when you start another version? If you have an opened window left, it will reuse that one unless to pass the -no-remote option on the command line.
The fact that you see no issue with the official builds shows that this issue is distribution specific. They could be patching firefox which makes it behave differently. You should report the issue on the SuSE bug tracking system and link to it from here. (is 2.0.0.8 the latest version available on SuSE 10.2? This is a security risk to use that old version unless they apply the security patches on top of that).
Comment 4•15 years ago
|
||
Do you still see this problem using the most recent versions of all components?
If you do not, please close the bug with resolution set to WORKSFORME.
If you do, please comment in the bug.
Whiteboard: [closeme 2010-09-15]
| Reporter | ||
Comment 5•15 years ago
|
||
I am now on firefox 3, Suse 11, and not even the same computer has when I reported the bug. Thankfully I no longer see any problems.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
OS: Linux → Windows CE
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•