Ubuntu
file-roller package

archive manager won't load flstudio_9.0.3.exe

Bug #492716 reported by kickpush05 on 2009-12-05

This bug report is a duplicate of: Bug #508120: every program i download,does never open or work always archive manager have a problem.i cant open my download programs. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	file-roller (Ubuntu)	Invalid	Low	Ubuntu Desktop Bugs

Bug Description

Binary package hint: file-roller

Ok guys,
     I saved the fl studio program flstudio_9.0.3.exe. I have a linux computer. When i open the file archive manager opens and reads the archive. Then it says... [/home/austin/Desktop/flstudio_9.0.1.exe]
  End-of-central-directory signature not found. Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive. In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
zipinfo: cannot find zipfile directory in one of /home/austin/Desktop/flstudio_9.0.1.exe or
          /home/austin/Desktop/flstudio_9.0.1.exe.zip, and cannot find /home/austin/Desktop/flstudio_9.0.1.exe.ZIP, period.

What does this mean? And how do i fix it?

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/file-roller
Package: file-roller 2.26.1-0ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: file-roller
Uname: Linux 2.6.28-11-generic i686

Tags:

Revision history for this message

kickpush05 (pitbull2890) wrote on 2009-12-05:

Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (22.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (777 bytes, text/plain; charset="utf-8")

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-12-08:

could you attach such file to the report? thanks.

Changed in file-roller (Ubuntu):
assignee:	nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-01-05:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.