Magnifier screen stays split even after exit

[John Baptist]

Binary package hint: gnome-mag

After quitting magnifier, the screen stays split, and mouse behavior is abnormal. In particular, the apparent visual position of the cursor does not correspond to where the clicks actually happen.

WHAT I EXPECT TO HAPPEN: When running magnifier, the screen is split between magnified and non-magnified views. After quitting magnifier, the screen should be restored to a single non-magnified pane.

WHAT ACTUALLY HAPPENS: After quitting magnifier, the screen remains split. The top pane (or the left pane, in the case of vertical split) contains only my desktop background. The bottom pane (or right pane, in the case of vertical split) contains my desktop icons, gnome-panel, and mouse pointer etc. However, clicking on an icon visible in the bottom pane has the effect of clicking on what would be in the bottom half of the screen, if the whole desktop were visible. See enclosed screen shot.

WHY THIS IS BAD: Beyond the fact that magnifier doesn't work when it's running, it also leaves the system in an unusable state.

WORKAROUND: I can restore the screen to a normal mode by switching video mode. E.g.: xrandr -s 1; xrandr -x 0

SYSTEM: Tested on Lucid 10.04, but as I recall this problem has existed at least since Jaunty. I am using nvidia drivers.

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug? Please describe step-by-step starting with how to start the gnome-mag application.

This will help us to find and resolve the problem.

[John Baptist (jepst79)]

To answer your questions:

Yes, it is reproducible. This happens every time I run it.

Running either "magnifier -h" or "magnifier -v" and then killing the magnifier program (by kill, pkill, or process manager) will trigger this bug.

If you need any more information, please let me know.

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. I was able to reproduce this issue in Ubuntu 10.10.

This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=640977

Thanks for taking the time to make Ubuntu better!