A NOTE has been added to this issue. ====================================================================== https://www.opencsw.org/mantis/view.php?id=4966 ====================================================================== Reported By: ghenry Assigned To: cgrzemba ====================================================================== Project: evince Issue ID: 4966 Category: regular use Reproducibility: always Severity: block Priority: normal Status: assigned ====================================================================== Date Submitted: 2012-06-24 08:30 CEST Last Modified: 2012-06-25 09:25 CEST ====================================================================== Summary: Segmentation fault on S10 sparc Description: machine-me% evince file.pdf Segmentation fault machine-me% evince Segmentation fault
====================================================================== ---------------------------------------------------------------------- (0009982) ghenry (reporter) - 2012-06-25 09:25 https://www.opencsw.org/mantis/view.php?id=4966#c9982 ---------------------------------------------------------------------- machine-root% pkgparam CSWevince VERSION 2.30.3,REV=2012.04.19 machine-root% uname -a SunOS machine 5.10 Generic_142900-15 sun4u sparc SUNW,Sun-Fire-V440 i think the problem is X11 related. V440 is a Sunray Server. The displays are very different: - centos sunray server (launching evince with ssh -X) - X11 on macosx thru Secure Global Desktop - VNC desktop It always crashes on centos, with the following messages: ** (evince:11757): WARNING **: Setting attribute metadata::evince::sidebar_visibility not supported The program 'evince' received an X Window System error.This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 212 error_code 16 request_code 5 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.) _______________________________________________ bug-notifications mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/bug-notifications
