eog crashed with SIGABRT in raise() (image viewer crashes after a few pictures)

[ליאור שמואל]

I've been viewing one of my image folders when the image folder suddenly crashed. it happened only twice. this never happened to me on quantal... hope this gets fixed soon :)

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: eog 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Tue May 28 00:42:36 2013
ExecutablePath: /usr/bin/eog
InstallationDate: Installed on 2013-03-07 (81 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: eog /home/username/roleplay/World\ of\ Darkness/.e/18699d5a4e7f40_full.jpg
Signal: 6
SourcePackage: eog
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
Title: eog crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-05-24 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (gnome-settings-daemon:3487): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
 (gnome-settings-daemon:3487): color-plugin-WARNING **: unable to get EDID for xrandr-LVDS1: unable to get EDID for output
 (tracker-miner-fs:3577): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/share/desktop-directories/vmware-ace-vms.directory': 'Desktop file doesn't contain type'

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1153624, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.