GNOME Bugzilla – Bug 310081
clicking on already open pdf opens a second view but still raises the first
Last modified: 2005-08-26 01:48:38 UTC
So... when I open a document from nautilus with evince, and the document is already opened but minimized, evince seems to try to do the right thing- which is to show the minimized window, instead of opening a new one. But it *also* opens a new one. So I end up with two, both visible, instead of either only one, or one visible and one still minimized. This is minor but very weird. [It struck me while writing that maybe this is evince triggering a confusing metacity bug instead? But I can't duplicate with eog + png.]
I assume this is latest cvs... What dbus version are you compiling with? Please try to open the same document two times from the console and paste the output here. In particular the second process should exit.
yeah, sorry, forgot to specify version. This is HEAD everything, inc. dbus. Output from terminal: louie@towel:~/Desktop$ evince ncaa\ confirmation.ps & [1] 965 louie@towel:~/Desktop$ ** (evince:965): WARNING **: Starting evince process. evince ncaa\ confirmation.ps & [2] 968 louie@towel:~/Desktop$ Attempt to register the same DBusConnection with the message bus, but it is already registered
Are you actually running the dbus you are compiling with? For example I'm running FC4 which ship 0.33. Though jhbuild install 0.35+ and evince will link to that. Because of API changes this doesnt work... Personally I dont think jhbuild should build dbus at all, it's a system component, it would be better to use the one provided by your distribution.
> Are you actually running the dbus you are compiling with? Yes. HEAD in both cases. (Alternately, I've just double-checked this on breezy, without any jhbuilt components, and it is happening there too.) > Personally I dont think jhbuild should build dbus at all, it's a system > component, it would be better to use the one provided by your distribution. Leaving aside the fact that exactly one distro is currently shipping a version of dbus compatible with GNOME 2.11, which makes this a practical impossibility, pragmatically, we must test what we ship, especially when it is under active development. That means building and using it.
>Leaving aside the fact that exactly one distro is currently shipping a version >of dbus compatible with GNOME 2.11, which makes this a practical impossibility, >pragmatically, we must test what we ship, especially when it is under active >development. That means building and using it. I'm possibly missing something but... how do you install jhbuild dbus system wise if your distribution is shipping a different version? Can different dbus versions be installed on the same system at all? Otherwise how do you actually test newest dbus or stuff depending on it? All real questions, I'm possibly confused...
What dbus version breezy is shipping? 0.34?
Btw another useful test would be to run two evince process from the console (without passing any document to it) and see if the second exits...
Luis, how are you running the jhbuilt dbus system wise? I'd like to reproduce and fix this but I have actually no idea on how to do that or if it's possible at all.
*** This bug has been marked as a duplicate of 314475 ***