Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.
Firefox 12.0 will not open on 2nd display by default
I just upgraded to Firefox 12.0. I have a second monitor connected to my MacBook Pro. With Firefox 11 and all previous versions, I had it set up that Firefox would automatically open on the second monitor when I open the program. With Firefox 12, it absolutely will not do this any longer. It's extremely annoying and makes me want to switch to Safari or Chrome, both of which do correctly open on the 2nd monitor.
Here's what I tried:
-Resizing the window and moving it to the second display, then quitting the program and reopening it.
-Moving the window to the second display and maximizing it, then quitting the program and reopening it.
-Uninstalling Firefox and deleting ALL files (including those in the Library Application Support and Preferences folders), then reinstalling version 12.0
-Uninstalling Firefox and deleting ALL files (including those in the Library Application Support and Preferences folders), then reinstalling version 13.0b
-Uninstalling Firefox and deleting ALL files (including those in the Library Application Support and Preferences folders), then running disk utility to repair permissions and disk, THEN reinstalling version 12.0.
What will correct the problem (though not a solution):
-Uninstalling Firefox and deleting ALL files (including those in the Library Application Support and Preferences folders), then reverting back to reinstalling version 11 and turning off the automatic updates.
The tech specs:
MacBook Pro 15" 2.66 GHz Intel Core i7, 8 GB 1067 MHz DDR3
Mac OS X Lion 10.7.3 (11D50)
Intel HD Graphics:
Chipset Model: Intel HD Graphics Type: GPU Bus: Built-In VRAM (Total): 288 MB Vendor: Intel (0x8086) Device ID: 0x0046 Revision ID: 0x0018 gMux Version: 1.9.21
NVIDIA GeForce GT 330M:
Chipset Model: NVIDIA GeForce GT 330M Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 512 MB Vendor: NVIDIA (0x10de) Device ID: 0x0a29 Revision ID: 0x00a2 ROM Revision: 3560 gMux Version: 1.9.21 Displays:
Resolution: 1440 x 900 Pixel Depth: 32-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Built-In: Yes
Resolution: 1280 x 1024 @ 75 Hz Pixel Depth: 32-Bit Color (ARGB8888) Display Serial Number: 4H065468 Mirror: Off Online: Yes Rotation: Supported Adapter Type: Apple Mini DisplayPort To VGA Adapter Adapter Firmware Version: 1.03
All Replies (16)
Try if this helps : Move the Firefox window to your second display, then shut down your Mac and do not turn off the second display. Restart the Mac with both screens on.
Thanks for the response. I did try what you suggested above, but unfortunately it did not work. Firefox will still only open on the main monitor (unlike before I upgraded to version 12).
Probably Corrupt localstore.rdf
Thank you again for helping troubleshoot this.
Before I posted here, I did google the problem and found those web sites you linked to. I tried the solution and it did not work. I tried it again now just to make sure, and unfortunately the problem persists.
If it helps and to clarify, this problem goes away if I delete all Firefox files, directories, etc., and reinstall Firefox version 11. As soon as I try upgrading to version 12 however, the problem comes back. It appears to be something that was introduced with version 12.
1. Un-maximise Firefox window 2. Position un-maximised window on monitor of you choice (second) 3. Close Firefox window 4. Reopen Firefox window 5. Maximise Firefox window 6. Close Firefox window
Now, probably, firefox will open maximised on the second monitor.
Thanks for continuing to try.
Tried this several times... no luck. It always reopens back on the first monitor.
I am having this same issue. It seems every time theres an update this happens. I have attempted all of the above techniques; deleting the localstore.rdf, unmaximizin- maximizing, all combinations of above, etc. with no results.
Please fix this bug. I really need to stop updating for these "fixes" only to break something else.
I am relieve to see someone else having this problem so I know it's not just me. This appears to be a bug with something introduced in Firefox 12. How would I go about filing an official bug report or is that necessary?
if you do find a solution, please post it here. I really don't want to hassle with everything to roll it back to 11
Just like Scott, dno_bot...and the many others across Google that are experiencing this same problem.
Previous versions behaved properly - Version 12.0 has a bug! hopefully it is fixed before they lose users to the likes of Chrome, Safari, IE, Aurora, Opera, etc, etc. There is a reason we chose Firefox, and there could be a reason why we chose to delete it????
they have about a week to fix it before I switch to chrome permanently.
dno_bot - While I understand your frustration, I really doubt that a threat is really going to accomplish anything here. Keep in mind that most of the people who help develop Firefox are volunteers.
I have opened a bug on Mozilla here: https://bugzilla.mozilla.org/show_bug.cgi?id=752149
Scott - Perhaps your subsequent frustration will be similar...if the same thing happens to your Bug report to Mozilla as has happened with mine - nothing!
(link fixed by Mod.)
Athraithe ag cor-el ar
I couldn't open your link for some reason.
If everyone who is having this problem would go to https://bugzilla.mozilla.org/show_bug.cgi?id=752149 and vote for this bug, it will move it up in priority.
based on that bugzilla thread it looks like they might not fix it until release 13.... guess I'll just skip 12. rolled back to 11 and turned off updates. let me know if this ever gets fixed.
Athraithe ag dno_bot ar
Yes, I opened the bug report and have been following the thread. They have identified the problem but they need to ensure that by instituting the fix, they don't regress some other bug or cause a new one.
Being that Firefox 13 is well into beta, it won't give them enough time to adequately test the fix before FF 13 is released. It will most likely be in FF 14. I am on the Firefox beta channel for updates and have been using the FF 13 beta. It's very stable. I assume the FF 14 beta will be to, so once they move FF 14 from alpha to beta and implement the fix, I'll switch to FF 14. If this bug is a huge issue for you, I'd recommend doing the same. I'm sure they would appreciate more people who experience this bug testing the fix when it is released into beta.