On Wed, Jan 19, 2011 at 1:16 PM, David Necas (Yeti) <[email protected]> wrote: > > Upgraded from 2.21 or an older version? >
I believe it was from 2.21. > Do the other X apps that work include Gtk+-based programs (GIMP, ...)? > Yes, GIMP works... > Please try ssh -Y instead of -X. Normal Gtk+ apps such as Gwyddion > should not need it but who knows... > I was already using -Y. > Then try to run gwyddion --sync in gdb and obtain a backtrace, i.e: > I installed the libglib2.0-0-dbg and libgtk2.0-0-dbg packages and got the following, which to me does not look too helpful... $ gdb /usr/bin/gwyddion GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... (no debugging symbols found) (gdb) run --sync Starting program: /usr/bin/gwyddion --sync (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f507f47b700 (LWP 5474)] The program 'gwyddion' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 132 error_code 2 request_code 146 minor_code 19) (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.) Program exited with code 01. (gdb) bt No stack. (gdb) ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Gwyddion-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gwyddion-users
