I was going to say temporarily move your .recently-used.xbel file in case it is trying to reload a broken PDF file, but if this is happening with or without argument, that shouldn't be a problem. The problem you describe only happens to me when it is called without argument and tries to load a broken PDF.
Was it fine with Karmic and then broke, or was it like this from the first time you tried to run it? One thing that might help diagnose this is to type "script evince.out" and then "strace -tt evince" Then, if "Force Quit" pops up do that, or go to "File -> Close". Then hit Control-D in the terminal window. Then attach the output here. For me evince's UI shows up in about a second, on a less powerful machine. With strace running, it takes about five seconds - and that is on the strace delay. -- evince mostly un-responsive, without CPU load https://bugs.launchpad.net/bugs/507679 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
