VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Author Topic: Archiver problem  (Read 1827 times)

Chris H

  • Member
  • *
  • Posts: 29
Archiver problem
« on: March 11, 2009, 11:41:21 pm »

Want to tar.gz a file, right click on it in the file manager, create tar.gz file, all done.

If I select create archive it opens up the archiver window but errors out when creating the tar.gz archive, error message box is empty. With tar.bz2 it creates the archive, gives a blank error message and the archive is unaccessible.

Anyone else seeing this?
Logged

caitlyn

  • Packager
  • Vectorian
  • ****
  • Posts: 2878
    • The Linux Works
Re: Archiver problem
« Reply #1 on: March 13, 2009, 03:39:56 pm »

Which file manager are you using?  Thunar, PCManFM, or ???
Logged
eMachines EL-1300G desktop, 1.6GHz AMD Athlon 2650e CPU, 4GB RAM, nVidia GeForce 6150 SE video
CentOS 6.5 (will try VL64-7.1 soon)

Toshiba Satellite A135-S4727,  Intel Pentium T2080 / 1.73 GHz, 2GB RAM, Intel GMA 950

HP Mini 110 netbook, 1.6GHz Intel Atom CPU, 2GB RAM, Intel 950 video, VL 7.1

Chris H

  • Member
  • *
  • Posts: 29
Re: Archiver problem
« Reply #2 on: March 13, 2009, 05:19:08 pm »

Thunar 0.9.3

Recent download of VL6 Standard
Logged

wcs

  • Packager
  • Vectorian
  • ****
  • Posts: 1144
Re: Archiver problem
« Reply #3 on: March 17, 2009, 01:12:32 pm »

Same here for .bz2 archives... with thunar in VL6 Std.
Logged

Chris H

  • Member
  • *
  • Posts: 29
Re: Archiver problem
« Reply #4 on: March 30, 2009, 12:57:14 am »

As an update to this I find that if I double-click on an existing archive in thunar it doesn't open. What I did notice was excessive disk activity though.

So looking at the processes running I found the main process and also other spawned processes which were being created, then disppearing with more processes created to replace them. Sort of thing!

So I could check a process, say 12230 with ps aux, then immediately do another ps aux and 12230 is gone but the same command is now being run as 12239...... ad infinitum. Only stops when I kill the primary process, say 10057.

Hope that's clear  ;D
Chris
Logged