Bug 1009633

Summary: [abrt] file-roller-3.8.3-1.fc19: sanitize_filename: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mikhail Yarashevich <aloner>
Component: file-rollerAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: arikomagik, gracca, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3fe9080b118945a4ea94947b93544219fb886d07
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:14:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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 Mikhail Yarashevich 2013-09-18 18:39:03 UTC
Version-Release number of selected component:
file-roller-3.8.3-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        file-roller '/home/mike/distrib/MS Office 2010/14.0.4763.1000_Professional_Plus_x86_ru_Krokoz.iso'
crash_function: sanitize_filename
executable:     /usr/bin/file-roller
kernel:         3.10.11-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 sanitize_filename at glib-utils.c:1030
 #1 _g_path_get_relative_basename_safe at glib-utils.c:1055
 #2 _fr_window_ask_overwrite_dialog at fr-window.c:6648
 #3 fr_window_archive_extract at fr-window.c:6854
 #4 extract_cb at dlg-extract.c:226
 #5 file_selector_response_cb at dlg-extract.c:254
 #10 _g_closure_invoke_va at gclosure.c:840
 #13 gtk_real_button_released at gtkbutton.c:1973
 #14 _g_closure_invoke_va at gclosure.c:840
 #17 gtk_button_button_release at gtkbutton.c:1805

Comment 1 Mikhail Yarashevich 2013-09-18 18:39:09 UTC
Created attachment 799525 [details]
File: backtrace

Comment 2 Mikhail Yarashevich 2013-09-18 18:39:12 UTC
Created attachment 799526 [details]
File: cgroup

Comment 3 Mikhail Yarashevich 2013-09-18 18:39:16 UTC
Created attachment 799527 [details]
File: core_backtrace

Comment 4 Mikhail Yarashevich 2013-09-18 18:39:20 UTC
Created attachment 799528 [details]
File: dso_list

Comment 5 Mikhail Yarashevich 2013-09-18 18:39:23 UTC
Created attachment 799529 [details]
File: environ

Comment 6 Mikhail Yarashevich 2013-09-18 18:39:27 UTC
Created attachment 799530 [details]
File: exploitable

Comment 7 Mikhail Yarashevich 2013-09-18 18:39:31 UTC
Created attachment 799531 [details]
File: limits

Comment 8 Mikhail Yarashevich 2013-09-18 18:39:39 UTC
Created attachment 799532 [details]
File: maps

Comment 9 Mikhail Yarashevich 2013-09-18 18:39:43 UTC
Created attachment 799533 [details]
File: open_fds

Comment 10 Mikhail Yarashevich 2013-09-18 18:39:47 UTC
Created attachment 799534 [details]
File: proc_pid_status

Comment 11 Mikhail Yarashevich 2013-09-18 18:39:50 UTC
Created attachment 799535 [details]
File: var_log_messages

Comment 12 Germán Racca 2013-10-12 23:01:37 UTC
1) Download this file: https://github.com/bling/vim-airline/archive/master.zip

2) Open it with file-roller

3) Click in the folder called vim-airline-master

4) Select all with Ctrl + A

5) Right click on selection, click Extract, select folder to extract into it, and press Enter

6) Now it crashes

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        file-roller vim-airline-master.zip
crash_function: sanitize_filename
executable:     /usr/bin/file-roller
kernel:         3.11.3-201.fc19.x86_64
package:        file-roller-3.8.3-1.fc19
reason:         Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 Fedora End Of Life 2015-01-09 19:53:22 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2015-02-17 17:14:33 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.