RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1186481 - file-roller SIGSEGV after extraction from command line
Summary: file-roller SIGSEGV after extraction from command line
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: file-roller
Version: 7.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: David King
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1133060
TreeView+ depends on / blocked
 
Reported: 2015-01-27 18:42 UTC by Helio Chissini de Castro
Modified: 2019-09-12 08:12 UTC (History)
9 users (show)

Fixed In Version: file-roller-3.14.2-5.el7
Doc Type: Bug Fix
Doc Text:
Cause: extracting an archive from the commandline, and closing the success dialog within 10 seconds Consequence: file-roller crashes Fix: a patch was added to ensure that the dialog could be closed at any time, not just after 10 seconds Result: file-roller no longer crashes when extracting an archive from the commandline and closing the success dialog
Clone Of:
Environment:
Last Closed: 2015-11-19 07:31:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 752478 0 None None None Never
Red Hat Product Errata RHBA-2015:2215 0 normal SHIPPED_LIVE gnome utilities bug fix and enhancement update 2015-11-19 08:26:52 UTC

Description Helio Chissini de Castro 2015-01-27 18:42:58 UTC 
Hello 

file-roller SIGSEGV after extract a compressed file, using command line arguments.
Crash happens after the extraction been done, just after progression dialog destruction. 100% reproducible.

Sample tests: 
file-roller --default-dir=/tmp --extract file:///home/user/VMwareTools-9.4.10-2092844.tar.gz
file-roller --default-dir=/tmp --extract file:///home/hcastro/tcp5432-22-10_30.zip

Gdb trace for latest sample

run /usr/bin/file-roller --default-dir=/tmp --extract file:///home/hcastro/tcp5432-22-10_30.zip
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffed791700 (LWP 17670)]
[New Thread 0x7fffecf90700 (LWP 17671)]
[New Thread 0x7fffe1ad8700 (LWP 17672)]
Detaching after fork from child process 17673.
Detaching after fork from child process 17674.
[New Thread 0x7fffe087c700 (LWP 17675)]
Detaching after fork from child process 17676.
[New Thread 0x7fffb3e18700 (LWP 17677)]
[Thread 0x7fffb3e18700 (LWP 17677) exited]
Detaching after fork from child process 17678.

Program received signal SIGSEGV, Segmentation fault.
archive_extraction_ready_cb (source_object=0x7d3b40 [FrCommandZip], result=0xa211f0, user_data=<optimized out>) at fr-window.c:6481
6481			open_progress_dialog_with_open_destination (window);
#0  archive_extraction_ready_cb (source_object=0x7d3b40 [FrCommandZip], result=0xa211f0, user_data=<optimized out>) at fr-window.c:6481
#1  0x00007ffff5f85557 in g_simple_async_result_complete (simple=0xa211f0 [GSimpleAsyncResult]) at gsimpleasyncresult.c:763
#2  0x00007ffff5f855b9 in complete_in_idle_cb (data=<optimized out>) at gsimpleasyncresult.c:775
#3  0x00007ffff59d99ba in g_main_dispatch (context=0x69cc80) at gmain.c:3061
#4  g_main_context_dispatch (context=context@entry=0x69cc80) at gmain.c:3660
#5  0x00007ffff59d9d08 in g_main_context_iterate (context=context@entry=0x69cc80, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3731
#6  0x00007ffff59d9dbc in g_main_context_iteration (context=0x69cc80, context@entry=0x0, may_block=may_block@entry=1) at gmain.c:3792
#7  0x00007ffff5fb80c4 in g_application_run (application=0x697120 [FrApplication], argc=argc@entry=4, argv=argv@entry=0x7fffffffdd28) at gapplication.c:2114
#8  0x0000000000416dbb in main (argc=4, argv=0x7fffffffdd28) at main.c:40
#0  archive_extraction_ready_cb (source_object=0x7d3b40 [FrCommandZip], result=0xa211f0, user_data=<optimized out>) at fr-window.c:6481
6481			open_progress_dialog_with_open_destination (window);
Undefined command: "liat".  Try "help".
6476		fr_archive_operation_finish (FR_ARCHIVE (source_object), result, &error);
6477		_archive_operation_completed (window, FR_ACTION_EXTRACTING_FILES, error);
6478	
6479		if ((error == NULL) && ask_to_open_destination) {
6480			window->priv->quit_with_progress_dialog = window->priv->batch_mode;
6481			open_progress_dialog_with_open_destination (window);
6482		}
6483		else if ((error == NULL) && ! batch_mode && ! gtk_window_has_toplevel_focus (GTK_WINDOW (window->priv->progress_dialog)))
6484			gtk_window_present (GTK_WINDOW (window));
6485	
A debugging session is active.

	Inferior 1 [process 17669] will be killed.

Quit anyway? (y or n)
Comment 2 Vadim Rutkovsky 2015-01-28 11:10:12 UTC 
Reproduced on RHEL 7.1's file-roller-3.8.3-3.el7.x86_64

However 'file-roller --extract <archive> --extract-to=/tmp' works flawlessly
Comment 7 Vitezslav Humpa 2015-05-12 14:01:51 UTC 
Still an issue withing the file-roller-3.14.2-1.el7.x86_64
Comment 8 Matthias Clasen 2015-05-16 16:23:48 UTC 
I've failed to reproduce this here, with file roller 3.16. What exactly are you running, this: ?

file-roller --default-dir=/tmp --extract file:///path/to/tar
Comment 9 Vitezslav Humpa 2015-06-17 10:10:21 UTC 
I am getting the segfault after extracting with:

$ file-roller --default-dir=/tmp --extract sample.tar.gz 
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Segmentation fault (core dumped)

Happens after confirming out the extraction completed dialog. Sometimes however the file-roller exits silently not showing the dialog or ending seconds after the dialog appears and exiting with '0' code.

Additionally:
- the file chooser never opens at /tmp but the home directory
- closing the file chooser before extraction, file-roller terminal instance does not close
Comment 15 Vitezslav Humpa 2015-09-01 10:17:45 UTC 
Verification tests passed on all architectures on Beta with file-roller-3.14.2-5.el7. Moving to verified.
Comment 17 errata-xmlrpc 2015-11-19 07:31:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2215.html
Note You need to log in before you can comment on or make changes to this bug.