Closed Bug 442925 Opened 11 years ago Closed 10 years ago
new mail notifications end up in wrong place on screen after randr
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061712 Fedora/3.0-1.fc9 Firefox/3.0 Build Identifier: thunderbird-126.96.36.199-1.fc10 (originally from the Fedora Bugzilla on the URL shown above) If you use xrandr to switch resolutions (like, say, due to switching to an external monitor with a higher resolution), the new mail notifications from thunderbird continue to pop up at the same coordinates on the screen rather than remaining at the bottom right until you restart it. Reproducible: Always Steps to Reproduce: 1.see above 2. 3. Actual Results: notification is displayed in the old position Expected Results: position of the notification should be adjusted to the current state of the screen
possible for you to try trunk build?
Severity: normal → minor
I see the same issue with thunderbird-188.8.131.52.en-US.solaris10-i386
Note that I don't think the Severity of this bug is "minor" (should be "normal"), since if you switch to a monitor with *lower* resolution, the notification is off-screen and not visible. The only workaround is to restart thunderbird. With Thin Clients (e.g. www.sun.com/sunray) moving from one station to another with a lower-resolution monitor can require use of xrandr and cause this problem, so occurrence can be rather frequent (I see it multiple times per day) in enterprises where large numbers of thin clients may be deployed.
I can empathize, because I use remote desktop constantly. You won't see a fix to TB2, so please try TB3 alpha 2 or trunk  to determine if the problem also exists there and report results? There are windowing improvements in the base gecko code  http://www.mozillamessaging.com/en-US/thunderbird/early_releases/ ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-trunk/
Whiteboard: [needs confirmation on trunk] → [needs trunk test] closeme 2009-12-01
Version: unspecified → 2.0
RESO INCO due to lack of response to last question. If you feel this change was in error, please respond to this bug with your reasosn why.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.