Bug 746413 - [abrt] xscreensaver-gl-extras-1:5.15-1.fc14: destroy_image: Process /usr/libexec/xscreensaver/glslideshow was killed by signal 6 (SIGABRT)
Summary: [abrt] xscreensaver-gl-extras-1:5.15-1.fc14: destroy_image: Process /usr/libe...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: xscreensaver
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:64b3088b82db9e97b693aa35653...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-15 14:20 UTC by Alexey
Modified: 2011-12-20 00:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-20 00:55:44 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (10.68 KB, text/plain)
2011-10-15 14:20 UTC, Alexey 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alexey 2011-10-15 14:20:18 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 10938 bytes
cmdline: /usr/libexec/xscreensaver/glslideshow -root
component: xscreensaver
Attached file: coredump, 54206464 bytes
crash_function: destroy_image
executable: /usr/libexec/xscreensaver/glslideshow
kernel: 2.6.35.14-97.fc14.i686
package: xscreensaver-gl-extras-1:5.15-1.fc14
rating: 4
reason: Process /usr/libexec/xscreensaver/glslideshow was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1318687858
uid: 500

How to reproduce
-----
1. Nothing
2.
3.
Comment 1 Alexey 2011-10-15 14:20:24 UTC 
Created attachment 528322 [details]
File: backtrace
Comment 2 Mamoru TASAKA 2011-10-18 00:44:23 UTC 
I have no idea currently.
Comment 3 Alexey 2011-12-19 18:06:18 UTC 
Package: xscreensaver-gl-extras-1:5.15-3.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. не знаю
2.
3.
Comment 4 Mamoru TASAKA 2011-12-20 00:55:44 UTC 
Fedora 14 is no longer supported.
Note You need to log in before you can comment on or make changes to this bug.