'Extract here' for .zip files not working as intended.

Bug #1919008 reported by Jalansh Munshi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Repro steps:

1. Download a .zip file.
2. Right-click on it and select 'Extract here'.

Note that my .zip file had one sub-folder and that sub-folder had many other sub-folders and files. Size ~ 240 MB

Expected behavior: A sub-folder should be extracted with size ~240 MB.

Actual behavior: A sub-folder was extracted, but its size was zero. No sub-folders or files in it.

This has happened multiple times with me over the past few weeks. Opening the .zip file and dragging and dropping the files works for the time being.

If it helps, the zip file I am mentioning here was downloaded from Google Drive.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-11-10 (123 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Package: file-roller 3.36.3-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Tags: focal
Uname: Linux 5.4.0-66-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-11-11 (122 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1919008

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Jalansh Munshi (jalansh) wrote :

Thank you for letting me know. I will keep that in mind next time.

I executed the command you mentioned and an alert popped up after a few minutes, saying - 'No additional information collected.'

Revision history for this message
Paul White (paulw2u) wrote :

Jalansh, no information was collected as you failed to tell us which flavour or release of Ubuntu you are using. Please provide that information so that the bug report can be attributed to the relevant package version. Once that has been done 'apport-collect 1919008' should provide additional information about your installation.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Jalansh Munshi (jalansh) wrote :

It's 20.04. It never asked me to put in my Ubuntu version. Where should I put it? Is this comment section fine?

Revision history for this message
Paul White (paulw2u) wrote :

Assuming that it's Ubuntu you're using and not a flavour I've assigned the bug to file-roller.

Try running

  apport-collect 1919008

in a terminal and see what data gets added to the bug report. I

tags: added: focal
affects: ubuntu → file-roller (Ubuntu)
Revision history for this message
Jalansh Munshi (jalansh) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Jalansh Munshi (jalansh) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Jalansh Munshi (jalansh) wrote :

Done! Please let me know if there's anything else I need to do.

Revision history for this message
Paul White (paulw2u) wrote :

Excellent. I'n un-subscribing now. Someone else will take a look and help you further.

Changed in file-roller (Ubuntu):
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, it sounds like bug #1917812, could you make sure you have the update https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/0.2.3-2ubuntu0.2 and try if it's working correcly with it installed?

Changed in file-roller (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Jalansh Munshi (jalansh) wrote :

It is not installed on my system. Should I run 'sudo apt-get --only-upgrade 0.2.3-2ubuntu0.2'?

Clarifying this as it is my first time doing something like this and I do not want my machine to mess up.

Revision history for this message
Sebastien Bacher (seb128) wrote :

weird, it's a security update, it should be part of normal updates or being automatically upgraded by unattended-upgrades if you wait a bit

what's the output of

$ dpkg -l | grep autoar

Revision history for this message
Jalansh Munshi (jalansh) wrote :

Here it is -

ii libgnome-autoar-0-0:amd64 0.2.3-2ubuntu0.2 amd64 Archives integration support for GNOME

Does this mean it is already installed? I executed 'dpkg -s 0.2.3-2ubuntu0.2 | grep version' yesterday and it said - "dpkg-query: package '0.2.3-2ubuntu0.2' is not installed and no information is available"

Revision history for this message
Sebastien Bacher (seb128) wrote :

Yes, as it's a security update it probably got autoinstalled. Do you still get the issue? Could you attach an example of problematic file to the bug?

The dpkg -s command you are using is invalid, the argument is a package name not a version, so it would be

$ dpkg -s libgnome-autoar-0-0

Revision history for this message
Jalansh Munshi (jalansh) wrote :

Interesting, I do not get the issue now. However, I did check multiple times and in different directories before opening this bug. And since it has already been reported before, means there may have been a problem with my system or something else.

Nevertheless, it is working fine now. I checked it with the same .zip file I used to report this bug.

If this happens again, then I will make sure to report it.

Thanks, Sebastien!

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, as said there was a regression which had been fixed in https://bugs.launchpad.net/ubuntu/+source/gnome-autoar/0.2.3-2ubuntu0.2 , which was published on the March 8th. Since security updates are auto applied in background it probably means you the fix installer without notice. Assuming that's what happened I'm going to take your recent comment of a confirmation that the fix is working as intended and close the ticket.

Changed in file-roller (Ubuntu):
status: Incomplete → Fix Released
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.