Bug 137543

Summary:	open large tgz file results in full /tmp partition and displays wrong content list of tar-file in konqueror
Product:	[Unmaintained] kio	Reporter:	Christian Mischeff <chrimi1>
Component:	tar	Assignee:	Mario Bensi <mbensi>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	amantia, j_schaef, mail
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Christian Mischeff 2006-11-18 17:58:31 UTC

Version:           Unbekannt (using KDE 3.5.1 Level "a" , SUSE 10.1)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.21-0.13-smp

I have a 500MB /tmp partition.
If i browse a *.tgz file with konqueror, kio_tar generates a file like
  /tmp/kde-<username>/ktar-<something>.tar
If the tgz-file is bigger than 500 MB the related /tmp-file requires more than the existing place in /tmp: the partition is 100% in use.

The first result is that konqueror displays only a little subset of the content from the tgz-file: the file looks corrupt. Konqueror generates no warning that there is a problem to unpack the file.

But the major problem is, that the file still exists until leaving the file using the return arrow in konqueror, the konqueror is closed, the user logs off and it even isnt deleted when the system is rebooted. So you have to login at a commandline and remove the tmp-file manually.
Ark has an analog problem with the size of the file but removes the file when the programm is closed.

The programms tar on the commandline or File-Roller have no problems to show the contents of the tgz.

I think kio_tar should only show a list of the contents if their is not enough space for unpacking the tgz-file and generate a warning that it is not possible to use the displayed content.

Comment 1 Julian Steinmann 2018-07-22 18:18:36 UTC

I cannot test this bug on my own because I don't have a separate /tmp partition. If this email does somehow still reach you and you do still have a setup similar to the one described in the original report it'd be great if you could try to reproduce this behavior - if it does still exist I'd need to move it over to kio-extras. Thanks!

Comment 2 Andrew Crouthamel 2018-09-28 03:27:15 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-10-29 02:00:37 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!