[SRU] Backport file-roller 44.3

Bug #2067387 reported by Nathan Teodosio
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Fix Released
Fix Released
Nathan Teodosio

Bug Description


This Gnome release has the following bug fixes:

1: File name not changed when creating a new archive.
2: 7z error when creating archives with volumes.
3: Crash upon opening rar archives.
4. Crash upon loading an empty file.

[1] https://gitlab.gnome.org/GNOME/file-roller/-/issues/248
[2] https://gitlab.gnome.org/GNOME/file-roller/-/issues/249
[3] https://gitlab.gnome.org/GNOME/file-roller/-/issues/243
[4] ttps://gitlab.gnome.org/GNOME/file-roller/-/issues/233

Test plan


Regression potential

* 7z archives creation.
* Extension->Filetype detection in general when creating the archive (i.e., writing a .tar.xz extension should create a application/x-xz-compressed-tar.
* Loading archives in general must not say "archive not supported" for supported types.

Changed in file-roller (Ubuntu Noble):
assignee: nobody → Nathan Teodosio (nteodosio)
Changed in file-roller (Ubuntu):
assignee: Nathan Teodosio (nteodosio) → nobody
Changed in file-roller (Ubuntu Noble):
status: New → In Progress
description: updated
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

Ubuntu sponsors, correct me if I'm wrong: Since this is a request to back port the current version from Oracular to Noble, I don't need to attach a debdiff.

description: updated
Changed in file-roller (Ubuntu Noble):
status: In Progress → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks Nathan, I updated the changelog to target the right serie, lower the revision comparated to the oracular upload and include the bug number. If you go through the sponsoring process it's probably easier to still provide a debdiff next time because other reviewers/sponsors might not want to be doing those changes themselves.

Changed in file-roller (Ubuntu Noble):
status: Triaged → Fix Committed
importance: Undecided → Low
Changed in file-roller (Ubuntu):
importance: Undecided → Low
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Nathan, or anyone else affected,

Accepted file-roller into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/file-roller/44.3-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed verification-needed-noble
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

On a 24.04 virtual machine with File Roller 44.3-0ubuntu1, I carried out each item of the test plan below reproduced, and the test plan was thoroughly successful.

Start File Roller

    Start File Roller from the launcher or desktop overview

    :)) The program is opened and reports that no archive is open.

Create an archive

    Use Ctrl+n or navigate the main menu to "New Archive". Type a name with an archive extension, e.g. u.tar.
    Use the + button to add some stuff to it.

    :)) tar tf u.tar lists the files that were added in the previous step.

Inspect an archive

    wget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/file-roller/44.3-1/file-roller_44.3.orig.tar.xz.

    file-roller file-roller_44.3.orig.tar.xz.

    :)) File Roller opens and you after entering file-roller-44.3 you see its source tree.

    :)) Alt+Return or 'main menu -> Properites' identifies the archive as an application/x-xz-compressed-tar.

Extract an archive

    Click the 'extract' button on the upper left corner.
    Choose '/tmp' as the target location.

    :)) Dialog says that extraction completed successfully.
    Click show the files.

    :)) Your file manager opens and displays the /tmp directory. The file-roller-44.3 directory is inside.

Alter an archive's contents

    Select any file, right-click it and rename.

    :)) tar tf file-roller_44.3.orig.tar.xz reflects the rename.

tags: added: verification-done verification-done-noble
removed: verification-needed verification-needed-noble
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package file-roller - 44.3-0ubuntu1

file-roller (44.3-0ubuntu1) noble; urgency=medium

  * New upstream release (lp: #2067387)

 -- Sebastien Bacher <email address hidden> Wed, 29 May 2024 10:39:15 +0200

Changed in file-roller (Ubuntu Noble):
status: Fix Committed → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote : Update Released

The verification of the Stable Release Update for file-roller has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Fabricio Azor (fabricioazor) wrote :

Tive esse erro, resolvi com atualizações:

$ sudo apt update && sudo apt upgrade
$ sudo apt install aptitude
$ sudo aptitude safe-upgrade
$ sudo apt update && upgrade
$ sudo apt-get update && sudo apt-get upgrade
$ sudo apt update && sudo apt full-upgrade && sudo snap refresh
$ sudo apt update && sudo apt full-upgrade -y && sudo apt autoremove -y && sudo apt autoclean && sudo snap refresh

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.