"Exract Here" in thunar does nothing

Bug #1038336 reported by glmm on 2012-08-18
50
This bug affects 11 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Undecided
Unassigned

Bug Description

The thunar context entry "Extract Here" does not work (when using on an archive file)

affects: file-roller (Ubuntu) → thunar-archive-plugin (Ubuntu)
glmm (glmm-deactivatedaccount) wrote :

Does not work with file-roller ( xarchiver works, but xarchiver cannot open iso files)

Edward Donovan (edward.donovan) wrote :

File-roller, in Quantal at least, is experiencing a lot of failures right now. There's a pretty good chance that's the problem. What do you see if you run file-roller from the command-line?

If it fails, the bug would likely be a duplicate of bug 1035688, or one of these crashes:

  https://bugs.launchpad.net/ubuntu/+source/file-roller/+bugs?field.searchtext=crash&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=&orderby=-id&start=0

Sorry for the ugly link, it's just searching file-roller bugs for 'crash'.

What versions of (x)ubuntu and file-roller are you running? I'm going to mark this incomplete until there's more information. Thanks!

affects: thunar-archive-plugin (Ubuntu) → file-roller (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in file-roller (Ubuntu):
status: New → Confirmed
glmm (glmm-deactivatedaccount) wrote :
Download full text (13.9 KiB)

*** glibc detected *** file-roller: double free or corruption (out): 0x0973bc30 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x73c22)[0xb6b28c22]
/lib/i386-linux-gnu/libglib-2.0.so.0(+0x4cb3b)[0xb6d64b3b]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xb6d64cb0]
file-roller[0x809e4cf]
/usr/lib/i386-linux-gnu/libffi.so.6(ffi_call_SYSV+0x1a)[0xb664a48e]
/usr/lib/i386-linux-gnu/libffi.so.6(ffi_call+0x6f)[0xb664a1ef]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_cclosure_marshal_generic_va+0x39a)[0xb6e2161a]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(+0xc177)[0xb6e1f177]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(+0xdad1)[0xb6e20ad1]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x497)[0xb6e39e77]
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x33)[0xb6e3a8b3]
/usr/lib/i386-linux-gnu/libgio-2.0.so.0(g_application_run+0x2ed)[0xb6efdbbd]
file-roller[0x8057d89]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb6ace4d3]
file-roller[0x8057dc5]
======= Memory map: ========
08048000-080be000 r-xp 00000000 08:01 132039 /usr/bin/file-roller
080be000-080bf000 r--p 00075000 08:01 132039 /usr/bin/file-roller
080bf000-080c1000 rw-p 00076000 08:01 132039 /usr/bin/file-roller
080c1000-080c2000 rw-p 00000000 00:00 0
096ad000-09928000 rw-p 00000000 00:00 0 [heap]
affa9000-afffb000 r--p 00000000 08:01 653297 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf
afffb000-b059b000 r--p 00000000 08:01 522519 /usr/share/icons/hicolor/icon-theme.cache
b059b000-b4118000 r--p 00000000 08:01 522569 /usr/share/icons/gnome/icon-theme.cache
b4118000-b4400000 r--p 00000000 08:01 532997 /usr/share/icons/gnome-colors-common/icon-theme.cache
b4400000-b4421000 rw-p 00000000 00:00 0
b4421000-b4500000 ---p 00000000 00:00 0
b450e000-b4546000 r-xp 00000000 08:01 134627 /usr/lib/i386-linux-gnu/libcroco-0.6.so.3.0.1
b4546000-b4548000 r--p 00038000 08:01 134627 /usr/lib/i386-linux-gnu/libcroco-0.6.so.3.0.1
b4548000-b4549000 rw-p 0003a000 08:01 134627 /usr/lib/i386-linux-gnu/libcroco-0.6.so.3.0.1
b4549000-b4580000 r-xp 00000000 08:01 136518 /usr/lib/i386-linux-gnu/librsvg-2.so.2.36.3
b4580000-b4581000 r--p 00036000 08:01 136518 /usr/lib/i386-linux-gnu/librsvg-2.so.2.36.3
b4581000-b4582000 rw-p 00037000 08:01 136518 /usr/lib/i386-linux-gnu/librsvg-2.so.2.36.3
b4582000-b45ff000 r--p 00000000 08:01 533013 /usr/share/icons/gnome-wise/icon-theme.cache
b45ff000-b4600000 ---p 00000000 00:00 0
b4600000-b4e00000 rw-p 00000000 00:00 0 [stack:4887]
b4e00000-b4e21000 rw-p 00000000 00:00 0
b4e21000-b4f00000 ---p 00000000 00:00 0
b4f05000-b4f21000 r-xp 00000000 08:01 391744 /lib/i386-linux-gnu/libgcc_s.so.1
b4f21000-b4f22000 r--p 0001b000 08:01 391744 /lib/i386-linux-gnu/libgcc_s.so.1
b4f22000-b4f23000 rw-p 0001c000 08:01 391744 /lib/i386-linux-gnu/libgcc_s.so.1
b4f38000-b4f39000 r-xp 00000000 08:01 136516 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
b4f39000-b4f3a000 r--p 00000000 08:01 136516 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
b4f3a000-b4f3b000 rw-p 00001000 08:0...

Major Grubert (majorgrubert) wrote :

Same problem here with Nautilus 3.4 or Nautilus 3.6

Leo Moseley (l-m-moseley) wrote :

I do not believe this is a file-roler bug but is a thunar-archive-plugin bug. I have had this issue on both i386 and amd64 and after re testing it, the only issue I see is that, the context menu "Extract Here" fails for both arch's, however context menu of "Open with "Archive Manager", Open with "Squeeze" and "Open to" does work.
I have not seen such in Nautilus from my personal experience so I will not comment on that.

Geert Jan Alsem (gj-alsem) wrote :

May be related to bug 978789. Someone on that bug page says it also happens with PCManFM, so that would mean it's not a Thunar specific bug, although I have not tested that myself.

I can say that installing file-roller 3.6.1.1-0ubuntu1 from the "proposed" repository does not fix this bug.

Geert Jan Alsem (gj-alsem) wrote :

I did some more research. When you do "Extract Here" in Thunar, it uses the following command to extract:

file-roller --extract-to=/home/example/foo/bar/ --extract-here --force /home/example/foo/bar/test.zip

The problem is with the --extract-to option. If I remove that it works, and any call to file-roller with --extract-to makes it crash.

If I look at file-roller's manpage, it does list --extract-to as a valid option, so it really is a bug in file-roller.

Geert Jan Alsem (gj-alsem) wrote :

And here's a manual fix for Thunar users:

Optionally, first make a backup of the file we're about to edit:

# sudo cp /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.tap /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.backup

Now we edit the file file-roller.tap (which is where the command for thunar-archive-plugin is stored) to remove the --extract-to option. The command will still work because the --extract-here option remains:

# sudo sed 's/"--extract-to=$(pwd)" //' /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.tap | sudo tee /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.temp > /dev/null; sudo mv /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.temp /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.tap; sudo chmod a+x /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.tap

eris23 (jdkatz23) wrote :

thunar Version: 1.5.2-0ubuntu1~ppa0.12.10.1
thunar-archive-plugin Version: 0.3.0-4
file-roller Version: 3.6.1.1-0ubuntu1
quantal amd64

"Extract Here" does nothing
"Extract to..." works fine

fix https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1038336/comments/9 worked

peterthevicar (peterbcs) wrote :

Just to confirm that removing "--extract-to=$(pwd)" from /usr/lib/x86_64-linux-gnu/thunar-archive-plugin/file-roller.tap fixed this for me. Thanks Geert.
ATB, Peter

Bernhard (b.a.koenig) wrote :

This seems fixed now.

Changed in file-roller (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers