Bug 1030706

Summary: [abrt] mate-screensaver-1.6.1-3.fc19: op_load_image: Process /usr/libexec/mate-screensaver/slideshow was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Tym Rehm <tymrehm>
Component: mate-screensaverAssignee: Dan Mashal <dan.mashal>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4e925fa16c547359a6e1eebec3a44cfa6f5fdb90
Whiteboard: abrt_hash:0e7fdeb12a65a0cb345028eba6b9636fd82bc448
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-01 09:47:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Tym Rehm 2013-11-15 01:36:11 UTC 
Description of problem:
I was setting the screensaver to picture folder option and clicked closes.

Version-Release number of selected component:
mate-screensaver-1.6.1-3.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/mate-screensaver/slideshow
crash_function: op_load_image
executable:     /usr/libexec/mate-screensaver/slideshow
kernel:         3.11.7-200.fc19.i686.PAE
runlevel:       N 5
type:           CCpp
uid:            16777216

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 op_load_image at gste-slideshow.c:691
 #1 load_threadfunc at gste-slideshow.c:724
 #2 g_thread_proxy at gthread.c:798
 #3 g_deprecated_thread_proxy at deprecated/gthread-deprecated.c:310
Comment 1 Tym Rehm 2013-11-15 01:36:19 UTC 
Created attachment 824219 [details]
File: backtrace
Comment 2 Tym Rehm 2013-11-15 01:36:23 UTC 
Created attachment 824220 [details]
File: cgroup
Comment 3 Tym Rehm 2013-11-15 01:36:26 UTC 
Created attachment 824221 [details]
File: core_backtrace
Comment 4 Tym Rehm 2013-11-15 01:36:30 UTC 
Created attachment 824222 [details]
File: dso_list
Comment 5 Tym Rehm 2013-11-15 01:36:35 UTC 
Created attachment 824223 [details]
File: environ
Comment 6 Tym Rehm 2013-11-15 01:36:38 UTC 
Created attachment 824224 [details]
File: exploitable
Comment 7 Tym Rehm 2013-11-15 01:36:41 UTC 
Created attachment 824225 [details]
File: limits
Comment 8 Tym Rehm 2013-11-15 01:36:44 UTC 
Created attachment 824226 [details]
File: maps
Comment 9 Tym Rehm 2013-11-15 01:36:47 UTC 
Created attachment 824227 [details]
File: open_fds
Comment 10 Tym Rehm 2013-11-15 01:36:51 UTC 
Created attachment 824228 [details]
File: proc_pid_status
Comment 11 Tym Rehm 2013-11-15 01:36:55 UTC 
Created attachment 824229 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-11-20 17:36:16 UTC 
I can't reproduce the issue here in my f19 installation.
Does the crask ocours everytime if you use the picture folder for screensaver slideshow?
Can you check if all pictures/directories are acxessable in the picture folder?

Likely crash reason: Jump to an invalid address
Exploitable rating (0-9 scale): 6