Bug 1008727

Summary: [abrt] mate-document-viewer-1.6.1-5.fc19: clear_job_selection: Process /usr/bin/atril was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: pioutw
Component: mate-document-viewerAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, daw-redhatbugzilla, fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:bc2e44b5d8e92e0d6ef811d7f6366ecaa9c0cec5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-20 17:50:39 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 pioutw 2013-09-16 23:51:08 UTC 
Description of problem:
no visible problem

Version-Release number of selected component:
mate-document-viewer-1.6.1-5.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        atril '/home/pi/Documents/Programme culture 1706.pdf'
crash_function: clear_job_selection
executable:     /usr/bin/atril
kernel:         3.10.11-200.fc19.i686.PAE
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 clear_job_selection at ev-pixbuf-cache.c:1014
 #1 ev_pixbuf_cache_set_selection_list at ev-pixbuf-cache.c:1078
 #2 clear_selection at ev-view.c:5998
 #3 start_selection_for_event at ev-view.c:3492
 #4 ev_view_button_press_event at ev-view.c:3596
 #5 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #11 gtk_widget_event_internal at gtkwidget.c:5017
 #12 gtk_widget_event at gtkwidget.c:4814
 #13 gtk_propagate_event at gtkmain.c:2490
 #14 gtk_main_do_event at gtkmain.c:1685
Comment 1 pioutw 2013-09-16 23:51:12 UTC 
Created attachment 798455 [details]
File: backtrace
Comment 2 pioutw 2013-09-16 23:51:15 UTC 
Created attachment 798456 [details]
File: cgroup
Comment 3 pioutw 2013-09-16 23:51:18 UTC 
Created attachment 798457 [details]
File: core_backtrace
Comment 4 pioutw 2013-09-16 23:51:21 UTC 
Created attachment 798458 [details]
File: dso_list
Comment 5 pioutw 2013-09-16 23:51:24 UTC 
Created attachment 798459 [details]
File: environ
Comment 6 pioutw 2013-09-16 23:51:27 UTC 
Created attachment 798460 [details]
File: exploitable
Comment 7 pioutw 2013-09-16 23:51:30 UTC 
Created attachment 798461 [details]
File: limits
Comment 8 pioutw 2013-09-16 23:51:33 UTC 
Created attachment 798462 [details]
File: maps
Comment 9 pioutw 2013-09-16 23:51:36 UTC 
Created attachment 798463 [details]
File: open_fds
Comment 10 pioutw 2013-09-16 23:51:39 UTC 
Created attachment 798464 [details]
File: proc_pid_status
Comment 11 pioutw 2013-09-16 23:51:42 UTC 
Created attachment 798465 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-09-28 15:44:29 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 pioutw 2013-09-30 20:30:24 UTC 
(In reply to Wolfgang Ulbrich from comment #12)
> Can you describe a little more detailed what happend?
> Did this issue occurs frequently ?

no visible problem happened, so i cannot describe anything
it occured only one time
Comment 14 Wolfgang Ulbrich 2013-09-30 20:34:19 UTC 
OK, feel free to post here if it happens again.
I'll leave the report a while open.
Comment 15 D. Wagner 2014-02-07 00:18:37 UTC 
For what it's worth, it just happened to me too when opening a new PDF file, but I can't seem to figure out which PDF file it was, so I can't reproduce and I don't have any new useful information.  I tried reporting the backtrace through abrt but it doesn't want to upload anything since it'd be a dup of this bug and this bug is status CLOSED.
Comment 16 Wolfgang Ulbrich 2014-02-07 14:40:02 UTC 
(In reply to D. Wagner from comment #15)
> For what it's worth, it just happened to me too when opening a new PDF file,
> but I can't seem to figure out which PDF file it was, so I can't reproduce
> and I don't have any new useful information.  I tried reporting the
> backtrace through abrt but it doesn't want to upload anything since it'd be
> a dup of this bug and this bug is status CLOSED.

You can create the backtrace by hand. Go to /var/temp/abrt/<folder-of-the report-no.>
Check for the right application in component file. Than run in this folder
'abrt-action-perform-ccpp-analysis'
Check the created backtrace for missing debuginfo files
ie.
0x0000003708407a30  0x000000370842ba07  Yes         /lib64/librsvg-2.so.2
0x00007fd4155dacd0  0x00007fd4155f9858  Yes         /lib64/libcroco-0.6.so.3
(*): Shared library is missing debugging information.

Install the missing missing debuginfo files with 'debuginfo-install <package name>
Than run
'abrt-action-generate-backtrace'