GNOME Bugzilla – Bug 408133
Opening 2nd instance of magnifier causes core dump
Last modified: 2007-06-03 23:17:47 UTC
Forwarded from: https://launchpad.net/ubuntu/+source/gnome-mag/+bug/85183 Using Ubuntu Edgy. When a 2nd instance of magnifier is opened it crashes with a core dump. Reproducible: Always Steps to Reproduce: 1) Open a terminal type "magnifier" 2) Open a 2nd terminal, type "magnifier" Expected result: A second magnifier opens, or a message saying magnifier is already open Actual Result: The program crashes with a core dump. Attached is a proposed patch that will display a message that another magnifier is already running then close properly.
Created attachment 82582 [details] [review] patch to fix opening of a second instance of gnome-mag patch by Michael Broadbent <michael.broadbent@ubuntu.com> to make starting of a second instance of gnome-mag not crash, but fail properly
I had three types of behavior here: 1 - Two instances running, but the second interfering in the first; 2 - One instance running and when trying to run the another I get: GTK Accessibility Module initialized (lt-magnifier:8993): Bonobo-WARNING **: Assigning a default value to a non readable property 'source-display-screen' (lt-magnifier:8993): Bonobo-WARNING **: Assigning a default value to a non readable property 'target-display-screen' ** ERROR **: Error registering magnifier server. aborting... Aborted 3 - The first instance giving the following messages: The program 'lt-magnifier' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 2707 error_code 3 request_code 3 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) and the second giving the messages in '2'. This patch doesn't correct this behavior, but clarify a bit the messages. More work need to be done to address this issue!
Created attachment 88164 [details] [review] correct the ambiguity in the if-then-else
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Created attachment 89303 [details] [review] the last patch correct the ambiguity but insert a logic bug that his new one correct