unsquashfs often fails with error "failed to read fragment table". This error is due to missing return value to a non-void return statement in read_fragment_table_4(). I have a patch for this, along with a division by zero fix when 0 element is being "unsquashed". Reproducible: Always Steps to Reproduce: 1. Get a squashfs image version 4 2. Try to unsquash it Actual Results: FATAL ERROR aborting: failed to read fragment table Expected Results: Successful unsquash
Created attachment 209361 [details, diff] Fix missing return value to non-void return statement This change is already in upstream CVS
Created attachment 209362 [details, diff] Fix division by zero in status bar when no file has to be extracted This patch is from upstream CVS.
Created attachment 209364 [details] Updated ebuild that includes the previous patches This ebuild was tested out of my overlay using a x86_64 machine and works as expected.
while i see the first change in the upstream cvs, i dont see the second. could you post info on that ?
Sorry, went too fast, patch is from Matthew Creech, found on Nabble: http://old.nabble.com/-PATCH--squashfs:-Handle-progress-bar-when-max-%3D%3D-0-td22901074.html Sadly its not upstream yet, but it can be reproduced if you extract something like / folder from a squash image.
should be added in 4.0-r1 now; thanks