should not save iso in /tmp which is 1 GB tmpfs

Bug #1215726 reported by Paul Dufresne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UNetbootin
New
Undecided
Unassigned

Bug Description

unetbootin try to save os image in /tmp which on Fedora 19 is a 1GB tmpfs and it is full for me after trying to put xbuntu daily image which was about 850 Mb.

[paul@ip216-239-66-63 ~]$ yum info unetbootin.i686 in
Modules complémentaires chargés : langpacks, refresh-packagekit
Paquets installés
Nom : unetbootin
Architecture : i686
Version : 0
Révision : 13.581bzr.fc19
Taille : 3.5 M
Dépôt   : installed
Depuis le dépôt : fedora

[paul@ip216-239-66-63 ~]$ df /tmp
Sys. de fichiers blocks de 1K Utilisé Disponible Uti% Monté sur
tmpfs 1032620 1032620 0 100% /tmp
[paul@ip216-239-66-63 ~]$

http://fedoraproject.org/wiki/Features/tmp-on-tmpfs says:
"/tmp now defaults to tmpfs. This might break a few programs which assume that they can place large files in /tmp or that /tmp is persistant across boot. If these programs cannot be fixed to use /var/tmp instead of /tmp for this, there are two options to undo the /tmp-on-tmpfs change locally: "

I did not try to edit $TMPDIR variable yet.

Tags: full tmp tmpfs
Revision history for this message
Paul Dufresne (paulduf) wrote :

Line 300 of http://sourceforge.net/p/unetbootin/code/ci/master/tree/src/unetbootin/unetbootin.cpp is
ubntmpf = "/tmp/";
inside bool unetbootin::ubninitialize(QList<QPair<QString, QString> > oppairs) function
might be it, not sure at all.

Also I now see that our fedora package seems to still use 581 (Révision : 13.581bzr.fc19) and latest version is 585.

I do not expect to recompile the package yet... I am not used to do it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.