Bug 1321470 - file-roller fails when renaming a certain file before extraction.
Summary: file-roller fails when renaming a certain file before extraction.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: file-roller
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-27 17:11 UTC by Sergio
Modified: 2016-12-20 19:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 19:39:49 UTC
Type: Bug


Attachments (Terms of Use)

Description Sergio 2016-03-27 17:11:36 UTC
Description of problem:
Usually I can rename a file before extraction successfully, but when I download http://www.madredivina.org/sites/default/files/mensajes-san_jose-pt-br-2016-01-01-2016-03-22.zip whose tree is
home/
└── md
    └── public_html
        └── sites
            └── default
                └── files
                    └── pdf
                        └── mensaje_san_jose
                            ├── mensagensdiarias_saojose_10fevereiro_2016.pdf
                            ├── mensagensdiarias_saojose_10janeiro_2016.pdf
                            |...

When I try to rename the 'mensaje_san_jose' folder to 'São José 2016 - parcial' it fails first by instead of renaming the original folder it creates a new folder with the new name and then when I try to extract the new folder it reports as if successful but actually doesn't extract anything.

When I start file-roller from the terminal it gives just one error when I close it so I think it has nothing to do with the bug:
(file-roller:7581): Gtk-CRITICAL **: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

It's been a while that I don't use a computer/Linux so I will study again how to have more verbose info but you can direct me on that too.

Version-Release number of selected component (if applicable):
I'm using gnome in updated fedora 23
file-roller.x86_64 3.16.4-1.fc23 @koji-override-0 

How reproducible:
Always

Steps to Reproduce:
1. Open http://www.madredivina.org/sites/default/files/mensajes-san_jose-pt-br-2016-01-01-2016-03-22.zip
2. Rename the 'mensaje_san_jose' folder to 'São José 2016 - parcial'
3.

Actual results:
Creates new folder and extracts nothing.

Expected results:
Renames original folder and extraction is successful.

Additional info:

Comment 1 Fedora End Of Life 2016-11-24 16:15:23 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

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 23 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 2 Fedora End Of Life 2016-12-20 19:39:49 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.


Note You need to log in before you can comment on or make changes to this bug.