GNOME Bugzilla – Bug 698408
image crashes eog
Last modified: 2014-11-29 18:01:05 UTC
The attached image was taken with an old camcorder. Opening the image in eog crashes my whole desktop environment. I end up at the lightdm login again. The first time, it happened when switching to full screen. i think. Now it happens immidiately. I can view the said image using firefox. I'm running ubuntu 12.04 Just upgraded everything. But same thing happens. gnome3 fallback session. I'm aware this bug must be related to more than eog, but please point me in the right direction. It might be related to my gpu/gpu-driver # lspci | grep VG 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M52 [Mobility Radeon X1300] xserver-xorg-video-radeon version: 1:6.14.99~git20111219.aacbd629-0ubuntu2
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Or could you attach the image? Thanks in advance!
I see, the image was too big (2.3MB) to be attached. Please download it from: https://bigmail.tugraz.at/outgoing/stefan_123334_15217/CRIM0001.JPG I'll try to create that backtrace
Created attachment 242004 [details] backtrace created with apport-retrace Seems like I am unable to get the symbols working... this is what I did: apport-retrace -c -C apport_cache/ -o _usr_bin_eog.1000.crash_bt_nocore --sandbox system /var/crash/_usr_bin_eog.1000.crash
We generally recommend running in gdb ("gdb eog", then "run") and after crash entering "thread apply all bt" at the prompt. For "apport" questions, please feel free to ask in an Ubuntu forum.
Thank you for your reply This is hard for me to follow, because my whole desktop environmet dies after running eog. so my terminal would exit as well. It's funny. I did run eog from tty2 with $DISPLAY set correctly. But then the bug does not occur. I will commit this bug to ubuntu, referencing this page... mayby this is the way to go
Hi mindoms, I am closing this bug report as no updated information has been provided. Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment and if this still happens in 3.14 or 3.12.