I've been running firefox-bin for some while on my system (amd64, fluxbox) and it's performed quite well. However, at some point a few weeks ago, firefox started drawing most new windows at 1x1 pixels. I can resize/maximize, but this gets annoying. Windows that are affected: --new full size windows. --new popup windows (ie the comments at http://atrios.blogspot.com) --user interface windows (the downloads window, the "choose the application to open this file window, etc. Curiously, the "save this file to disk, or choose an application" window is at the proper size.) I've re-emerged the program several times, with no changes. I've also done a fair bit of mucking around in the .mozilla directory. Deleting localstore.rdf (as one forum post suggested) didn't solve the problem. Neither did deleting the .mozilla directory entirely and generating a new configuration. I also tried importing a known-good .mozilla directory from a new system, and the same problem arose. Until this point, the problem had occurred with firefox-bin v. 1.0.2, but a downgrade to 1.0.1-r1 didn't change anything. Most curiously, the same problem occurred when I emerged mozilla-bin, leading me to wonder if the problem is a) in some common mozilla library or b) in fluxbox. When I built a 64-bit firefox, it drew all windows properly. But the 64 bit firefox doesn't have flash support. :-) Any ideas or suggestions? I'd be glad to post any config files. Thanks! Reproducible: Always Steps to Reproduce: 1. Start up firefox 2. Go to http://atrios.blogspot.com 3. Open a comment window for a post. (Alternatively, download a pdf or other file, save a web page, etc, open a new browser window....almost anything that will cause a new window to open.) Actual Results: New windows open at 1x1 pixel size. They can be resized and/or maximized. Expected Results: New windows open at size that makes them readable. I'm running fluxbox 0.9.12-r1. I've had some difficulty with firefox and fluxbox before (generally in that firefox will not start in certain fluxbox themes) but this problem is new. I'm also running amd64 stable, and haven't yet tried any unstable versions of firefox or fluxbox. Emerge Info: Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.9-gentoo-r14 x86_64) ================================================================= System uname: 2.6.9-gentoo-r14 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 16 2005, 08:13:55)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O2 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://mirrors.tds.net/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X acpi alsa berkdb bitmap-fonts cdr cjk crypt cups curl dvd esd fam flac font-server fortran gdbm gif gpm gtk imagemagick imlib ipv6 java jp2 jpeg libwww lzw lzw-tiff mad matroska motif mp3 multilib ncurses nls oggvorbis opengl oss pam perl png python readline sdl ssl tcpd tetex tiff truetype truetype-fonts type1-fonts usb userlocales xml xml2 xmms xpm xprint xrandr xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
Ok, problem has now gone away. Two possible theories as to what solved it: 1) There was an entry for firefox in ~/.fluxbox/apps, which may have restricted the window size. I've subsequently removed the entry. 2) I used a 64-bit mozilla-firefox build for a while, making an entirely new ~/.mozilla directory. firefox-bin runs fine on this directory. Something here isn't entirely as it should be, but the browser works for me now.
Problem hasn't really gone away. A number of circumstances where firefox doesn't exit properly (either due to a freeze in X or a bug in firefox) cause the program to draw all subsequent windows at 1x1. It's always possible to maximise that window and have a useable browser, but new windows are still created at 1x1, and the problem is only really solved by deleting the .mozilla directory and rebuilding a new one (deleting all bookmarks, history, installed extensions, etc. in the process). I've tried backing up the .mozilla directory, but the window size issues persist even after renaming the backup directory to .mozilla and restarting the browser. This seems to happen on 1.0.4 as well as earlier versions. Renewed attention to the bug seems to be in order :-) Thanks.
i have the same issue, but slightly worse. occasionally firefox's window is less than 1x1 (ie 0x0) and doesn't even appear in the task bar. the oly solution is to killall -9 firefox-bin. Sometime restarting fluxbox fixes this. It only seems to happen on one of my (2) screens. I noticed a fix on fluxbox's site relating to it saving window positions correctly. I am currently running the version with the 'fix' and so far so good.
Same here. Sometimes I do not get a window at all (i.e. 0x0 window?), sometimes they are too small (~ 100x50 or so), and sometimes it works correctly. I also tried "firefox -width 1130 -height 900", but that does not help actually getting a window. I use windowmaker-0.92.0-r1 and mozilla-firefox-1.0.6-r5 on amd64. I also tried (on earlier firefox) CFLAGS="", which did not help.
I have the same problem where both mozilla (64 bit) and firefox-bin (32 bit) fail to display when started on a regular basis. I'm using openbox though, so it's not a fluxbox specific issue. Also, firefox-bin has been playing up for a very long time but it's only been recently that mozilla has been doing the same trick. I'm very frustrated by this (as is my wife).
ALL window manager issues should be fixed in latest releases of them, openbox3.3_rc2-r1 contains fix for 64bit users wm works fine and so does fluxbox. if this problem still persist please open a new bug with windows manager of version of ff/tb that is causing a problem. You may have to use ~arch for windows managers as I do not add patches to stable wm's for 64bit fixes.
