Red Hat Bugzilla – Bug 1008727
[abrt] mate-document-viewer-1.6.1-5.fc19: clear_job_selection: Process /usr/bin/atril was killed by signal 11 (SIGSEGV)
Last modified: 2014-02-07 09:40:02 EST
Description of problem:
no visible problem
Version-Release number of selected component:
cmdline: atril '/home/pi/Documents/Programme culture 1706.pdf'
runlevel: N 5
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
Created attachment 798455 [details]
Created attachment 798456 [details]
Created attachment 798457 [details]
Created attachment 798458 [details]
Created attachment 798459 [details]
Created attachment 798460 [details]
Created attachment 798461 [details]
Created attachment 798462 [details]
Created attachment 798463 [details]
Created attachment 798464 [details]
Created attachment 798465 [details]
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
(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
OK, feel free to post here if it happens again.
I'll leave the report a while open.
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.
(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
Check the created backtrace for missing debuginfo files
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>