After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 679970 - wildcards OK but listing 2 or more files on command line crashes eog
wildcards OK but listing 2 or more files on command line crashes eog
Status: RESOLVED DUPLICATE of bug 677168
Product: eog
Classification: Core
Component: collection
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-07-15 18:27 UTC by Brian McMinn
Modified: 2012-07-15 20:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Brian McMinn 2012-07-15 18:27:13 UTC
I just loaded Fedora 17 on a new machine and started using it.
I am accessing my old directory from a previous (Fedora 12?) version
of Fedora so I'm accessing old files using an old setup and a new
version of eog.

I can run these two commands without any problem:
  eog foo.jpg
  eog bar.jpg
But every time I run the following command it core dumps:
  eog foo.jpg bar.jpg
The message is:
  Segmentation fault (core dumped)

This problem persisted for every run I attempted until I ran
  eog -g foo.jpg bar.jpg
Running this command once for two random files appears to have fixed
every instance of this problem for every pair of files I've tried.
I suspect that some old setup file option was modified when I ran with the
"-g" command line option because I am no longer able to re-create this
problem in my own directory.  (I can re-create it in a second user
directory where the "-g" option has not been used.)
Comment 1 Felix Riemann 2012-07-15 20:27:02 UTC
That's most likely the same issue as #677168, which is a problem with the redone GtkIconView layout code in gtk+-3.4.3. We already have a fix for this in our repository but I was holding back an eog update for a fixed gtk+-3.4.4 which is needed to really fix this. Funnily two hours ago said gtk+-release happened, so expect a fixed eog shortly. :)
---
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 677168 ***