I solved the problem really simply. The fact is that evince is so concieved that it keeps an history of recently used files. However, if the files are not available anymore, because for example they are located on a share, on a remote machine, evince tries - it takes generally minutes - to make something with them.
So to resolve the problem, I deleted the file recently-used.xbel, which is located in the home directory under .local/share/. Once the file is deleted, evince starts instantly. Yeah! For me, this is definitely a bug. It should really investigated in the start process of evince. What does evince with the list of recently used files. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/67407 Title: evince very slow to start Status in “dbus” package in Ubuntu: Invalid Status in “evince” package in Ubuntu: Invalid Bug description: Binary package hint: evince when I want to start evince, it is very slow to start.. when i launch it starting from a console, it send to me this following error : ** (evince:30194): WARNING **: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/67407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
