Cannot Extract in File Roller When Using Default Location

Bug #503690 reported by jamie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTK+
Unknown
Unknown
One Hundred Papercuts
Invalid
Undecided
Unassigned
gtk+2.0 (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

After opening a ZIP file using File Roller and clicking the Extract button. The Extract window already has a default location selected, yet the Extract button in the dialog is greyed out. If one is happy with the default location, you have to click another folder and then click back to the default folder again before the Extract button on the dialog is clickable.

Fix: The Extract button should not be greyed out when the default extraction folder is selected.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

not here, that works fine, which version of Ubuntu are you running there?

Changed in file-roller (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Vish (vish)
Changed in hundredpapercuts:
status: New → Incomplete
Revision history for this message
Triqui (triqui) wrote :

I Karmic Koala Fully updated as of this post date I have this same problem. The button is enabled, but when I click it nothing happens. I have to move to another location and then come back to the default location to make it work.

Revision history for this message
Omer Akram (om26er) wrote :

this is not a file-roller bug rather its a gtkfilechooser bug. to verify that open firefox press ctrl+o and click open without selecting anything.

Changed in hundredpapercuts:
importance: Undecided → Low
status: Incomplete → Triaged
Changed in file-roller (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Vish (vish) wrote :

I'm still unable to reproduce this problem.

Every time extract in file-roller and firefox works correctly ,no problems.
BTW , I'm on Lucid , either this problem has been solved or something in your respective system is creating a problem.

affects: file-roller (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in gtk+2.0 (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Vish (vish) wrote :

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

Changed in hundredpapercuts:
importance: Low → Undecided
status: Triaged → Invalid
Revision history for this message
Omer Akram (om26er) wrote :

I am using lucid fully updated and face this.

Revision history for this message
Vish (vish) wrote :

I'd suggest you try it again , in a guest session.
On lucid it works correctly.
It might be cruft from old hidden files in your /home directory.

Changed in gtk+2.0 (Ubuntu):
status: Incomplete → New
Revision history for this message
David Siegel (djsiegel-deactivatedaccount) wrote :

Vish, I don't see why this is not considered a paper cut.

Changed in hundredpapercuts:
status: Invalid → Confirmed
Changed in hundredpapercuts:
status: Confirmed → Invalid
Changed in gtk+2.0 (Ubuntu):
status: New → Triaged
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 80755, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

As a workaround , you can turn off the location bar , ctrl+l and it will work as expected.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.