evince very slow to start

Hello! Thank you for the report. I've updated the privacy to "public" so other people can see this report.

thanks for your bug. That looks like a dbus issue. Do you have issue with other applications too? Does it work after restarting the session?

Bonjour Sebastien

J'espère que vous comprenez le français, j'ai du nouveau pour ce bug mais si
je comprends la langue anglaise en lecture je la parle assez mal ....

Lorsque je veux ouvrir un fichier .dvi avec Evince, ça ne pose aucun
problème, néanmoins, le logiciel reste dans la liste des processus en cours.

Si je veux ouvrir un fichier .pdf juste après, le problème signalé survient
:

~$ evince

** (evince:8122): 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.

1) le problème ne se produit pas si on kille Evince de la liste des
processus...

2) Après avoir relancé la machine, le message d'erreur n'apparaît pas, ce
qui me paraît logique puisqu'il est killé lors de cette opération.

Si vous ne comprenez pas ce message, je chercherais un traducteur ...
If you don't understand this message, i would search a translator ...

Jean-Claude

2006/10/28, Sebastien Bacher <email address hidden>:
>
> thanks for your bug. That looks like a dbus issue. Do you have issue
> with other applications too? Does it work after restarting the session?
>
> ** Also affects: dbus (Ubuntu)
> Importance: Undecided
> Status: Unconfirmed
>
> --
> evince very slow to start
> https://launchpad.net/bugs/67407
>

--
http://www.flickr.com/photos/leonux/

Merci pour le commentaire. Est-ce que vous pouvez lancer "ps aux | grep dbus" d'une ligne de commande et copier ça sur la page du bug? Est-ce que ca arrive aussi lorsque vous lancez plusieurs copies d'evince sans ouvrir de document ou seulement après ouvrir un .dvi? Est-ce que vous utilisez GNOME?

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

This is bullshit. This is a real bug and you shouldn't be rejecting it because you don't have enough information. The status of the bug should remain open or pending.

I have this bug. atm it is occurring whenever I open a pdf document. I already have evince open (some other documents open). I am opening it from the command line with some other pdf as commandline arg. I have opened dvis with evince since the program was last closed, but none are open now. It may be related to evince not being able to access default or previous profile as each time the layout of the document, when it finally opens, is different than usual (thumbnails enabled)?

I am using Gnome.
base3@effie:/media/USB DISK/AnnEcoStat$ ps aux | grep dbus
102 497 0.0 0.1 3192 1244 ? Ss Nov20 4:15 dbus-daemon --system --fork
gdm 5029 0.0 0.0 3388 12 ? S Nov27 0:00 /usr/bin/dbus-launch --exit-with-session
base3 5226 0.0 0.0 4716 76 ? Ss Nov27 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session gnome-session
base3 5229 0.0 0.1 3232 1248 ? Ss Nov27 0:03 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session
base3 5230 0.0 0.0 3388 12 ? S Nov27 0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session gnome-session
base3 21338 0.0 0.0 3052 868 pts/2 R+ 22:23 0:00 grep --color=auto dbus

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.