Aw: [Bug 1256414] Re: evince rotion bug with postscript files

2014-12-25 Thread JMB
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1256414 Title: evince rotion bug with postscript files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu

[Bug 1256414] Re: evince rotion bug with postscript files

2014-12-25 Thread JMB
be shown to not be effective just with this little (and boring) example. JMB "Without feedback, you cannot learn." -- Richard M. Stallman ** Changed in: evince (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of U

[Bug 1256414] Re: evince rotion bug with postscript files

2014-05-03 Thread JMB
As the bug is still present in 14.04 LTS final is there any solution in reach? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1256414 Title: evince rotion bug with postscript files

[Bug 1256414] [NEW] evince rotion bug with postscript files

2013-11-29 Thread JMB
evince:3776): Gtk-WARNING **: drawing failure for widget `EvView': invalid matrix (not invertible) Many thanks for your help - a fix or at least workaround for 13.10 would be much appreciated. Regards, JMB P.S.: lsb_release -rd Description:Ubuntu 13.10 Release:13.10 #

[Bug 1159931] Re: Evince not rendering Postscript files

2013-07-02 Thread JMB
After a little bit of experimenting I found a valid workaround for me: LANG=en_US evince .ps (which is also soltion for the search-problem in current google-earth). Nevertheless one should fix this nasty regression for those users not accustomed to setting variables, looking through forums and

[Bug 1159931] Re: Evince not rendering Postscript files

2013-07-01 Thread JMB
I don`t understand while a bug known for so long seems to be still present in Xubuntu 13.04. If ghostscript is the problem why is the buggy version still in use? Or do I encounter a different problem? Additional, the workaround (comment #11) given above is not effective (at least not for me): $