CrunchBang Linux

markwilson

Member

From: Norwich, UK

Registered: 2011-07-06

Posts: 22

Archive Manager problems

Hi all,
         I'm having problems with the Archive Manager (version 3.84). I get the following when
trying to extract:

An error occured while extracting files.
Error setting owner: Operation not permitted

One file in a folder will be extracted and that's it but curiously there's no problem via the command line:

tar xzf foo.tar.gz

I'm using 64-bit Crunchabang and tracking unstable.

Mark Wilson

Random Access

#! Member

From: vor dem Gesetz

Registered: 2013-11-02

Posts: 91

Re: Archive Manager problems

Same problem here with Jessiex686.

I came here looking for a solution, and sort of found one I guess.  I didn't know command line would work.

---

"Where I come from, that means you're about to steal a mirror."--Kilgore Trout

Random Access

#! Member

From: vor dem Gesetz

Registered: 2013-11-02

Posts: 91

Re: Archive Manager problems

I came across this problem at stackexchange where someone was getting a similar error trying to mount a USB drive with udisks. 

snip

EDIT:  This did not really work.  I don't know why I was able to extract the one archive but I can't anymore.

Last edited by Random Access (2013-12-02 01:49:10)

---

"Where I come from, that means you're about to steal a mirror."--Kilgore Trout

Random Access

#! Member

From: vor dem Gesetz

Registered: 2013-11-02

Posts: 91

Re: Archive Manager problems

I finally gave up and decided it was probably better to start with a fresh Debian minimal system from a Jessie snapshot, and install some of the #! packages rather than upgrading from Wheezy.

Sort of drastic, but the problem seems to be fixed.  I am using Wicd instead of network-manager, and lxpolkit with gvfs, gksu, udisks with thunar in daemon mode.  Then I pulled in some of the #! artwork and configs.  I'm also using lxpanel instead of tint2 because it is very light and has a calendar and great volume mixer built in.   I installed Dropbox locally in ~/.dropbox-dist and call it from keybindings in rx.xml, so I don't need the Nautilus dependencies.

---

"Where I come from, that means you're about to steal a mirror."--Kilgore Trout

markwilson

Member

From: Norwich, UK

Registered: 2011-07-06

Posts: 22

Re: Archive Manager problems

Bits of Gnome 3.10 are starting to appear in experimental so there may be a new version of file-roller in unstable soon. For the time being I'm using Ark but keeping file-roller installed so right-click compress still works in Thunar.

Random Access

#! Member

From: vor dem Gesetz

Registered: 2013-11-02

Posts: 91

Re: Archive Manager problems

It looks like the Thunar developers may be moving away from file-roller anyway:

Package: thunar-archive-plugin (0.3.1-2 and others)

Archive plugin for Thunar file manager

This plugin allows one to extract and create archive from inside the Thunar file manager. At the moment it uses file-roller but will use xarchiver in the future.

I see what you mean about Gnome3, though; if I select file-roller in apt-get here is what it wants to pull with it (Debian Jessie):

The following NEW packages will be installed:
  brasero brasero-common cdrdao file-roller gir1.2-clutter-gst-2.0
  gir1.2-evince-3.0 gir1.2-gtkclutter-1.0 gir1.2-gtksource-3.0
  gnome-desktop3-data gnome-keyring gnome-sushi gnustep-base-common
  gnustep-base-runtime gnustep-common gvfs-backends hwdata libbrasero-media3-1
  libclutter-gst-2.0-0 libclutter-gtk-1.0-0 libexempi3 libgmime-2.6-0
  libgnome-desktop-3-2 libgnustep-base1.22 libgoa-1.0-0 libgoa-1.0-common
  libgtksourceview-3.0-1 libgtksourceview-3.0-common libmusicbrainz5-0
  libnautilus-extension1a libobjc4 libquvi-scripts libquvi7
  libtotem-plparser17 libtracker-sparql-0.16-0 nautilus nautilus-data unar

Looks like the Gnome folks did not like the results of popularity-contest, and have gone full-blown troll.  It won't be long before gedit brings all of Gnome with it I suppose.

There is another thing going on here that I don't quite understand.  The thunar-archive-plugin is a custom package that resides in the Waldorf repo (thunar-archive-plugin_0.3.0-4crunchbang1), so depending an whether one upgrades with or without the #! Waldorf repo in the sources  will determine which thunar-archive-plugin is installed.  The part I don't understand is are there customizations in the #! version that prevent it from working with the file-roller version in testing?

Last edited by Random Access (2013-11-12 08:40:34)

---

"Where I come from, that means you're about to steal a mirror."--Kilgore Trout

melodie

New Member

Registered: 2012-05-11

Posts: 8

Re: Archive Manager problems

Hi,
I am seeking for the best recipe for all kinds of permissions in Debian testing/jessie and saw the thread here. In the file 55-storage.pkla you mention, the lines relate to udisks. In Jessie which I installed yesterday, there is no udisks, it is udisks2 by default. Perhaps changing all "udisks" in the lines of the file, to "udisks2" could fix at least part of the access issues some met with?

Random Access

#! Member

From: vor dem Gesetz

Registered: 2013-11-02

Posts: 91

Re: Archive Manager problems

Hi Melodie,  I edited that post, since it was basically bad advice.  I am using Jessie from a minimal install and I do not have that file in /etc/polkit-1/localauthority/50-local.d/ yet my udisks2 works OK.  Did you install Jessie from a Debian disk, or did you update #! Waldorf?  If you did a straight Debian install, did you use a USB flash drive for the install?  The reason I'm asking that is that the Debian installer put entries in /etc/fstab for my USB disk when I installed from a flash drive.  This created a few problems, plus my DVDROM would not mount.  I had to replace the flash drive entries with the proper settings for my DVD-ROM.

---

"Where I come from, that means you're about to steal a mirror."--Kilgore Trout

Nebucatnetzer

#! CrunchBanger

Registered: 2013-05-26

Posts: 205

Website

Re: Archive Manager problems

Hi Melodie,  I edited that post, since it was basically bad advice.  I am using Jessie from a minimal install and I do not have that file in /etc/polkit-1/localauthority/50-local.d/ yet my udisks2 works OK.  Did you install Jessie from a Debian disk, or did you update #! Waldorf?  If you did a straight Debian install, did you use a USB flash drive for the install?  The reason I'm asking that is that the Debian installer put entries in /etc/fstab for my USB disk when I installed from a flash drive.  This created a few problems, plus my DVDROM would not mount.  I had to replace the flash drive entries with the proper settings for my DVD-ROM.

Sorry to hijack this thread.
I'm having a problem with playing DVDs on my installation.
Could this be due the problem you mention?
If so what did you do to fix it?

Random Access

#! Member

From: vor dem Gesetz

Registered: 2013-11-02

Posts: 91

Re: Archive Manager problems

Probably not the problem if the DVD mounts OK.  My setup is a bit different from a normal #! install.   The file /etc/fstab should have an entry that begins "/dev/cdrom" or similar.  Mine had "/dev/sdb" after installing Debian from a USB drive.

---

"Where I come from, that means you're about to steal a mirror."--Kilgore Trout

melodie

New Member

Registered: 2012-05-11

Posts: 8

Re: Archive Manager problems

Hi,

To Random Access: I have no idea what you removed from my post, but it seems you left the important part. This file does not exist in distributions because it's up to the user to create it or not to create it.

I use several distributions, one is a recent install of Jessie, performed from a testing ISO (multi arch 32/64 bits), neither from a USB stick nor from a CD : instead I used the "poor man install" method, using hd-media files to initiate the boot to ISO.

What I use in Jessie:
PCManFM, (last version available in sid, because the install is meant to test a few programs coming from sid), gnome-polkit/polkit-gnome-authentication-agent-1 (not lxpolkit), gvfs and gvfs-backends.

yet my udisks2 works OK.

I don't know what works ok for you, in my Jessie install I could not have an access to my internal partitions (I have two other Debian installs, one which is a clone of Jessie and a Wheezy, as well as an Ubuntu home made with Openbox).

The different internal partitions could not be accessed normally, I wasn't even prompted for a password. Sometimes I dive in that kind of stuff to make it work with a password only, other times I only want to gain an access as simple user just by a click on the icon and name of the partition in the pcmanfm sidebar (my main file manager).

I think it is the post #3 of your's which made me think about talking of udisks2 here. The added custom file under the /etc/polkit-1 section solved it directly.

The file I am still using nowadays is a deprecated method, but which is still simple (add authorisations, add a user or a group, and if it is a group, be in that group : I chose sudo because it exists and added my user to it).

The new method used in Archlinux (another distro I use currently) uses javascript! (Always moving to new things… )

Conclusion: use a custom.plka file or not if you don't want to, if in need it gets very handy. (And it doesn't break anything, so it should not be a bad advice. )

Random Access

#! Member

From: vor dem Gesetz

Registered: 2013-11-02

Posts: 91

Re: Archive Manager problems

I didn't delete anything from your post Melodie.  I am not a moderator--I just joined.  I deleted the stuff I posted about polkit, because I felt it only confused the original issue discussed in this thread.

One thing I am wondering, but I suppose you have already checked is whether you have support installed for the type of file system on the partitions you are trying to access?

---

"Where I come from, that means you're about to steal a mirror."--Kilgore Trout

melodie

New Member

Registered: 2012-05-11

Posts: 8

Re: Archive Manager problems

I didn't delete anything from your post Melodie.  I am not a moderator--I just joined.  I deleted the stuff I posted about polkit, because I felt it only confused the original issue discussed in this thread.

Oh, ok.

One thing I am wondering, but I suppose you have already checked is whether you have support installed for the type of file system on the partitions you are trying to access?

I haven't given it the slightest thought, because they are all Ext4 partitions.

Last edited by melodie (2013-12-12 04:36:12)