eog - Eye of gnome takes too long to open

Somewhat but not quite to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/193010

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * Could you get a gdb stacktrace while it's hanging?

 This will help us to find and resolve the problem.

Your welcome,

Please answer these questions:
 * Is this reproducible?
    This is reproducable when it happens but it gets breaks too from breaking. For a few minutes I was able to get it twice to instantly open the images one time briefly last night without any action on my part.

 * If so, what specific steps should we take to recreate this bug?

You could approach this two ways:

Method 1:

1. open your gnome terminal
2. type in eog

What will happen depends randomly either:

  You will have eog open empty and instantly.

-- if the bug springs into action -----

   You will have eog wait about 1 1/2 minutes and display:

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.

and open afterwards.

Method two:

1. Open nautilus either clicking on your gnome home desktop. Or calling it anyway you want to.

2. Open any folder with pictures and click on the picture. If the bug is activated your image will appear in about 1 1/2 minutes.

or you may want to keep image slideshow and switch images you'll notice the lag too,

 * Could you get a gdb stacktrace while it's hanging?

The program never hangs it just seems to without a known trigger point either work instantly or delay and work with that error.

I will need the commands to type in if you want the gdb stacktrace despite of it not actually hanging but delaying. What is weird about this bug is that it gave me a break two times by not activating itself. Seems even though one time I stopped dbus it was just a coincidence when the bug stopped. The second time it stopped with no action on my part.

To clarify: The bug is back again without any actions on my part. However it may just go away for a bit anytime it decides to. Funny as this may be but this bug seems to have a mind of its own.

run the software in gdb:
- gdb eog
(gdb) run
... get the hang ...
<ctrl-C>
(gdb) thread apply all bt

Having trouble here but here is what i understood so far:

mypc$ gdb eog
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/eog
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb6c2f750 (LWP 15757)]
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no...

Now the bug is gone again all i did was reboot like the 10th time. Wonder what will trigger it again, it is a very strange case.

Think was able to pinpoint how to trigger it (but not sure yet see if you try this it wakes the bug up). Perform the following steps:

1. Go to a folder with lots of pictures
2. Inside of eog enable "image collection" from the file --> view menu.
3. Close eog
4. click on a single picture in the folder or try to call eog from the terminal.

Results:

   You should get eog lag of at least 1.5 ..... 1 1/2 minutes. followed by the error if you started from the command line:

** (eog: random x): 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.

does it seem similar to bug #288765?

very little connection barely [bug #288765] but not quite because eog will open but delayed. In that bug as understood it will refuse to open at all. Also more info says guy is running a vfat system while only ubuntu is installed on that machine. Also they need to logout for the bug to start doing its problems. While here one just needs to activate the "image collection," browse the collection and close the program. Restart it and it will run after a long delay each time. From trying to reproduce it few times it always seems to happen after activating the image collection.

Again see if you can reproduce it I was able to confirm it after repeating the same thing it started to bug out. The steps below are as above but with slight language fixes.

===========================================

1. Go to a folder with lots of pictures
2. Inside of eog enable "image collection" from the file --> view menu. in the image collection select few pictures by clicking on them individually with mouse. Now stop.
3. Close eog
4. click on any single picture in the picture folder or try to call eog from the terminal.

Results:

You should get eog lag of at least 1.5 ..... 1 1/2 minutes. Eog empty or with a picture will still open but very late. You'll think it did nothing. followed by the error if you started from the command line:

** (eog: random x): 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.

============================================

you seem to be the only one to get this bug which means you either have a local issue or it's due to some configuration, does it do the same using an another user on the same box?

Turns out i'm not alone actually i came across few threads across ubuntu doing google search. Not one but it would take a while to hunt more.

For one here are a few:

1. http://ubuntuforums.org/showthread.php?p=7120888

2 . https://bugs.launchpad.net/ubuntu/+source/eog/+bug/134616
{Same problem slightly different varient}

3. https://bugzilla.redhat.com/show_bug.cgi?id=451871 {same problem bit different varient}

 If I can come up with anything more from my own system let you know. But this is not an isolated bug to me only.

4. http://ubuntuforums.org/showthread.php?t=842536&page=2

there is no real point to argue on whether 5 or 15 users are having this issue, it's just happening to very few users and need debugging by somebody having the issue

[ there is no real point to argue on whether 5 or 15 users are having this issue, ]

Was not arguing you did not understand me through the internet. No enemy made and no enemy lost was merely pointing out what felt was not true for this bug.

[it's just happening to very few users]

That is "true" it is happening for a select "few" something must be in common with this small percentage of us who are hit by it. Somehow we triggered it if I may be of any help it will make me feel better that others will not run into it.

[ and need debugging by somebody having the issue ]

  Later today will get a chance to create a fake new account and see if it is isolated to the profile. I'll post back when get some information. Be it a yes or a no.

Sadly I was able to confirm this to be localized to my profile. As another user the problem does not exist. The small percent sufferered likely the same issue. If this is in fact some corrupting bug despite being low risk it might cause more damages to others. Let me know, if anything else you want me to check. But at this point I feel have noway to trace it back. Other then recreating a profile as for me that used for a year and was happily adjusted to. I'll wait until hear back thanks. bye.

One other thing If this would be any help .xsession-errors from home-dir. Last errors leading up to the text may / may not be related (don't know):

chXlib: extension "XFree86-Misc" missing on display ":0.0".
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

** (eog:7699): 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.

do you have the accessibility options activated for you user? can you try without those? otherwise it could be due to some configuration

Nope I do not, trying to isolate the cause i just reinstalled a library. Following someones forum instruction: sudo apt-get install --reinstall liblcms1. So far eog is working but not sure if it is related.

It is fixed by following an unrelated issue (sudo apt-get install --reinstall liblcms1). If you notice the poster had a totally different issue. Yet what he did worked for me too the thread is at: http://ubuntuforums.org/showthread.php?t=1132113. Anyone having same problem trick is to reinstall liblcms1. Since it can't be tracked to the cause anyone having this problem reinstall that lib.

I had a same issue. Bug started to show after I enabled View -> Image collection. I found this comment http://bugzilla.gnome.org/show_bug.cgi?id=572013#c4 and disabled Assistive Technologies. Log out and log in and everything was fine.

I've been having this problem too, disabling Assistive Technologies and logging out/in fixed the issue.

Exactly the same issue here, after using eog with no problems at all for a few years. I don't know what the trigger was, but it started after viewing a directory with many jpg files with the collections display on. From that point the same "Did not receive a reply" error when starting in the terminal and failure to start after a long delay in Nautilus.

Disabling Assistive Technologies cured the problem.