gnome-mag not working

[Murray Cumming]

The gnome-magnifier does not seem to work at all, for instance when chosen from
the accessibility control panel. When started from the command line, I see this
output. Hopefully it helps:

wolfgang@ubuntu:~$ magnifier

(magnifier:6986): Bonobo-WARNING **: Assigning a default value to a non readable
property 'source-display-screen'

(magnifier:6986): Bonobo-WARNING **: Assigning a default value to a non readable
property 'target-display-screen'

** (magnifier:6986): WARNING **: this copy of gnome-mag was built without damage
extension support.

** (magnifier:6986): WARNING **: Damage client hooks were not initialized.

** (magnifier:6986): WARNING **: this copy of gnome-mag was built without xfixes
extension support.

** (magnifier:6986): WARNING **: Cursor change notification hooks were not
initialized.
initial viewport 1280 1024
** Message: set source bounds to 0,0; 1280,0
region to update: 0 0 1280 0
region to update: 0 0 1280 0

http://bugzilla.gnome.org/show_bug.cgi?id=316484: http://bugzilla.gnome.org/show_bug.cgi?id=316484

[Sebastien Bacher (seb128)]

I've forwarded this issue upstream: http://bugzilla.gnome.org/show_bug.cgi?id=316484

[Bill-haneman (bill-haneman)]

This bug may have been filed against the wrong component; the test, running the
'magnifier' binary from the command line, is not valid in the form given here.

Try 'magnifier -v -m' for something that will actually put output on screen;
also see "magnifier --usage".

[Sebastien Bacher (seb128)]

thanks, it works for me, closing the bug. Feel free to reopen if that's still an
issue for you.

[Murray Cumming (murrayc)]

I showed the command-line output just so you would have some more information.

I actually was trying to use it from the Applications menu. It still does not
work - the startup notification cursor shows for a while and then stops. I
assume that the application crashed while starting.

[Sebastien Bacher (seb128)]

That works fine here with the current version. What happens when you run
"gnopernicus" from the command line?

[Murray Cumming (murrayc)]

In case it is useful information: xorg.conf says that the video card (or
driver, at least) is a GeForce2 MX/MX 400.

[Murray Cumming (murrayc)]

> What happens when you run "gnopernicus" from the command line?

wolfgang@ubuntu:~$ gnopernicus
Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open
shared object file: Datei oder Verzeichnis nicht gefunden
GTK Accessibility Module initialized
Bonobo accessibility support initialized

(gnopernicus:7678): Gnome-WARNING **: Accessibility: failed to find module
'libatk-bridge' which is needed to make this application accessible

**********************
* SCREEN READER CORE *
**********************

Bonobo accessibility support initialized
GTK Accessibility Module initialized

(srcore:7679): Gnome-WARNING **: Accessibility: failed to find module
'libatk-bridge' which is needed to make this application accessible

** ERROR **: Could not locate registry
aborting...

(gnopernicus:7678): gnopernicus-WARNING **: srcore beendet.

Clicking the radio button for the magnifier in the Startup section, and clicking
Apply, does nothing, and gives no output on the terminal. On my Breezy install
on another computer this starts the magnifier.

[Henrik Nilsen Omma (henrik)]

Our magnifier setup has seen many changes since 2005. Is anyone still seeing this in Edgy or Feisty. If not we should close it as fixed.

[GadAbraham (gad-abraham)]

It's not working for me on Edgy:

$ magnifier

(magnifier:15465): Bonobo-WARNING **: Assigning a default value to a non readable property 'source-display-screen'

(magnifier:15465): Bonobo-WARNING **: Assigning a default value to a non readable property 'target-display-screen'

** ERROR **: Error registering magnifier server.

aborting...
Aborted (core dumped)

t$ dpkg -s gnome-mag
Package: gnome-mag
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 1200
Maintainer: Ubuntu Core Developers <email address hidden>
Architecture: i386
Version: 1:0.13.1-0ubuntu3

[Henrik Nilsen Omma (henrik)]

Works nicely for me on feisty, both from the command line and from Orca (and it seems to work for others as well). Please reopen if you still have crashes on Feisty. We are also considering a shift to a Compiz-based solution for Feisty+1.

[GadAbraham (gad-abraham)]

I've just upgraded to Feisty and I'm getting:

$ magnifier
GTK Accessibility Module initialized

(magnifier:23706): Bonobo-WARNING **: Assigning a default value to a non readable property 'source-display-screen'

(magnifier:23706): Bonobo-WARNING **: Assigning a default value to a non readable property 'target-display-screen'
** Message: added event source to xfixes cursor-notify connection
** Message: added event source to damage connection
** Message: added event source to composite connection
initial viewport 1680 1050
** Message: set source bounds to 0,0; 1680,1050

The program 'magnifier' received an X Window System error.
This probably reflects a bug in the program.
The error was '180'.
  (Details: serial 6536 error_code 180 request_code 153 minor_code 12)
  (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.)