Bug 702186 - [abrt] eog-2.32.0-3.fc14: IA__gtk_tree_model_get_valist: Process /usr/bin/eog was killed by signal 11 (SIGSEGV)
Summary: [abrt] eog-2.32.0-3.fc14: IA__gtk_tree_model_get_valist: Process /usr/bin/eog...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: eog
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Siddhesh Poyarekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5a746f59dc2600d076f3edff314...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 01:30 UTC by Luke Hutchison
Modified: 2015-09-14 00:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-27 07:06:27 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (29.82 KB, text/plain)
2011-05-05 01:30 UTC, Luke Hutchison 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Luke Hutchison 2011-05-05 01:30:15 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 30533 bytes
cmdline: eog /home/luke/Photos/Me/TED-Headshots/a-select-IMG_8457.JPG
component: eog
Attached file: coredump, 161955840 bytes
crash_function: IA__gtk_tree_model_get_valist
executable: /usr/bin/eog
kernel: 2.6.36-1.1.fc15.x86_64
package: eog-2.32.0-3.fc14
rating: 4
reason: Process /usr/bin/eog was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Not sure if it is reproducible, I was opening and closing a number of large images at the same time. One I tried opening directly from the Trash, not sure if that caused the problem.
time: 1304558738
uid: 500
Comment 1 Luke Hutchison 2011-05-05 01:30:18 UTC 
Created attachment 496955 [details]
File: backtrace
Comment 2 Kalev Lember 2012-04-27 07:06:27 UTC 
Fedora 14 that this bug was reported against is EOL. Closing the ticket; please
reopen if you can reproduce this with eog in a newer Fedora release.

Thanks!
Note You need to log in before you can comment on or make changes to this bug.