I just did a little bit more debugging. From what i've seen, the menu errors i was reporting earlier seem to be a function of iceweasel starting up when the screen is at one resolution, and then persisting across a screen resolution change.
In particular, if i start iceweasel when my screen is 1024x600 (single
builtin LVDS), and then attach an external monitor (LVDS + VGA) to get a
setup like this:
0 d...@pip:~$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1624, maximum 1280 x 1624
VGA connected 1280x1024+0+0 (normal left inverted right x axis y axis)
338mm x 270mm
1280x1024 60.0*+ 75.0 59.9 60.0*
1280x960 60.0
1280x800 60.0
1152x864 75.0
1280x768 60.0
1024x768 85.0 75.1 75.0 70.1 60.0 59.9
832x624 74.6
800x600 72.2 75.0 60.3 59.9 56.2
640x480 75.0 72.8 72.8 75.0 66.7 60.0
59.9
720x400 70.1
LVDS connected 1024x600+0+1024 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x600 59.5*+
800x600 85.1 72.2 75.0 60.3 56.2
640x480 85.0 72.8 75.0 59.9
720x400 85.0
640x400 85.1
640x350 85.1
TV disconnected (normal left inverted right x axis y axis)
0 d...@pip:~$
then iceweasel prefers to show tooltips and menus still limited to the
old 1024x600 resolution, even if the browser is running in the larger
1280x1024 display. this means that tooltips and menus that would
otherwise be placed in reasonable spots in the righthand or bottom areas
of the screen instead are placed in the small upper-left region.
Conversely, if i start iceweasel when i have both screens attached and
running, and then detach the larger screen, i get the problem i reported
before: menus/etc end up displaying half off the screen to the point
where i can't get to them.
It's as though iceweasel is caching some information about the available
display space at process start and failing to update that information
when the available screen space gets resized.
Hope this helps to track down the problem. Let me know if i can debug
or test anything.
Regards,
--dkg
signature.asc
Description: OpenPGP digital signature
