Linux - Problem with files in /tmp/something

137 views
Skip to first unread message

Fotografia

unread,
Feb 4, 2013, 2:27:39 PM2/4/13
to hugi...@googlegroups.com
Hello everyone,

 i have found out that Hugin 2012.0.0.a94faa15c927 doesn't create the panorama if i use files that are from /tmp folder (this time they were in /tmp/pano.

I attach the output:

If i put the very same files in ~/pano everything works fine.

===========================================================================
***************  Panorama makefile generated by Hugin       ***************
===========================================================================
System information
===========================================================================
Operating system: GNU/Linux
Release: 2.6.32-45-generic
Kernel version: #102-Ubuntu SMP Wed Jan 2 22:38:04 UTC 2013
Machine: x86_64
Disc usage
File system            Dimens. Usati Disp. Uso% Montato su
/dev/sda1              29G  5,8G   22G  22% /
none                  996M  392K  995M   1% /dev
none                 1000M  184K 1000M   1% /dev/shm
none                 1000M  200K 1000M   1% /var/run
none                 1000M     0 1000M   0% /var/lock
none                 1000M     0 1000M   0% /lib/init/rw
/dev/sda2             663G  622G  7,7G  99% /home
Memory usage
             total       used       free     shared    buffers     cached
Mem:          1999       1367        631          0        103        681
-/+ buffers/cache:        582       1417
Swap:         2000          0       2000
===========================================================================
Output options
===========================================================================
Hugin Version: 2012.0.0.a94faa15c927
Project file: /tmp/huginpto_pwOgEA
Output prefix: IMG_1947-IMG_1948
Projection: Rectilinear (0)
Field of view: 56 x 56
Canvas dimensions: 2767 x 2767
Crop area: (93,167) - (2755,2767)
Output exposure value: 11.28
Selected outputs
Normal panorama
* Blended panorama
===========================================================================
Input images
===========================================================================
Number of images in project file: 2
Number of active images: 2
Image 0: /tmp/pano/pano/IMG_1947.JPG
Image 0: Size 3648x2736, Exposure: 10.98
Image 1: /tmp/pano/pano/IMG_1948.JPG
Image 1: Size 3648x2736, Exposure: 11.57
===========================================================================
Testing programs
===========================================================================
Checking nona...[OK]
Checking enblend...[OK]
Checking enfuse...[OK]
Checking hugin_hdrmerge...[OK]
Checking exiftool...[OK]
===========================================================================
Stitching panorama
===========================================================================
make: ***  Nessuna regola per generare l'obiettivo "/tmp/pano/pano/IMG_1947.JPG", necessario per "IMG_1947-IMG_19480000.tif".  Arresto.

Thank you in advance.

T. Modes

unread,
Feb 5, 2013, 2:05:33 PM2/5/13
to hugin and other free panoramic software


On 4 Feb., 20:27, Fotografia <fotogiuli...@gmail.com> wrote:
> Hello everyone,
>
>  i have found out that Hugin 2012.0.0.a94faa15c927 doesn't create the
> panorama if i use files that are from /tmp folder (this time they were in
> /tmp/pano.
>
> I attach the output:
>
> If i put the very same files in ~/pano everything works fine.
>

I can't reproduce the issue. I tested on Fedora and Win7. All files
in /tmp/pano. Output is correctly created also in this folder.

Thomas

Frederic Da Vitoria

unread,
Feb 5, 2013, 3:15:22 PM2/5/13
to hugi...@googlegroups.com
2013/2/5 T. Modes <Thomas...@gmx.de>
Couldn't that be again a problem with special characters in the user name?

--
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org

Fotografia

unread,
Feb 5, 2013, 4:08:19 PM2/5/13
to hugi...@googlegroups.com

Here i'm using Ubuntu 10.04 .

Analyzing the log i see this message:


Nessuna regola per generare l'obiettivo "/tmp/pano/pano/IMG_1947.JPG"

Should be, in english, something like no rule to create target  "/tmp/pano/pano/IMG_1947.JPG"

I see /tmp/pano/pano/IMG_1947.JPG and not only /tmp/pano/IMG_1947.JPG . Maybe the problem is here?

Thank you again.

Greg 'groggy' Lehey

unread,
Feb 5, 2013, 8:21:34 PM2/5/13
to hugi...@googlegroups.com
On Tuesday, 5 February 2013 at 13:08:19 -0800, Fotografia wrote:
> Il giorno martedì 5 febbraio 2013 20:05:33 UTC+1, T. Modes ha scritto:
>> On 4 Feb., 20:27, Fotografia <fotogiuli...@gmail.com> wrote:
>>>
>>> i have found out that Hugin 2012.0.0.a94faa15c927 doesn't create
>>> the panorama if i use files that are from /tmp folder (this time
>>> they were in /tmp/pano.
>>>
>>> I attach the output:
>>>
>>> If i put the very same files in ~/pano everything works fine.
>>>
>>
>> I can't reproduce the issue. I tested on Fedora and Win7. All files
>> in /tmp/pano. Output is correctly created also in this folder.
>
> Analyzing the log i see this message:
>
>> Nessuna regola per generare l'obiettivo "/tmp/pano/pano/IMG_1947.JPG"
>
> Should be, in english, something like no rule to create target
> "/tmp/pano/pano/IMG_1947.JPG"
>
> I see /tmp/pano/pano/IMG_1947.JPG and not only /tmp/pano/IMG_1947.JPG .
> Maybe the problem is here?

Most definitely. My guess is that this is one of the input files, and
you didn't move them to /tmp. Would that fit?

Greg
--
Sent from my desktop computer.
Finger gr...@FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua

Henner Zeller

unread,
Feb 5, 2013, 11:33:18 PM2/5/13
to hugi...@googlegroups.com
Hi,
I had a similar problem before and I think I know what the problem is,
though I didn't look in the source (I solved my problem by doing
things in my home directory and didn't have time to drill to the
bottom of the problem; however a Hugin developer might be able to
quickly find the problem).

My analysis from the time:

Hugin generates a makefile with things to do (it is called
something.pto.mk) in your project directory. If the project is outside
/tmp, then the makefile contains absolute paths to images it
references.

If the images happen to be in /tmp, then Hugin generates relative
paths, probably because Hugin creates its own temporary directory and
whatever code generates the makefile is too smart for its own good and
realizes its opportunity to generate relative paths.
So if you create a directory
/tmp/foo
and copy all the images in there, then the makefile does not refer to
/tmp/foo/image_1234.jpg but to something like ./foo/iimage_1234.jpg
(don't remember the exact way, but I remember that it was a relative
path instead of an absolute path).

However, later the execution fails because (presumably) the process'
working directory is actually not /tmp, but /tmp/foo. So the places
where it looks for the pictures are /tmp/foo/foo/image_1234.jpg ...
which is wrong.

So - whatever code generates the makefile, it should try to be less
smart about it :)

T. Modes

unread,
Feb 6, 2013, 11:56:20 AM2/6/13
to hugin and other free panoramic software
> Analyzing the log i see this message:
>
> Nessuna regola per generare l'obiettivo "/tmp/pano/pano/IMG_1947.JPG"
>
>
>
> Should be, in english, something like no rule to create target
> "/tmp/pano/pano/IMG_1947.JPG"
>
> I see /tmp/pano/pano/IMG_1947.JPG and not only /tmp/pano/IMG_1947.JPG .
> Maybe the problem is here?
>

The same path is used in the pto file:

===========================================================================
Input images
===========================================================================
Number of images in project file: 2
Number of active images: 2
Image 0: /tmp/pano/pano/IMG_1947.JPG
Image 0: Size 3648x2736, Exposure: 10.98
Image 1: /tmp/pano/pano/IMG_1948.JPG
Image 1: Size 3648x2736, Exposure: 11.57

So maybe you have saved the pto file in the parent folder and copied
the file later to the pano folder.

@Henner The project.pto.mk is not used for stitching. I checked again:
If the project file / images is in the temp folder, the makefile is
still using absolute file names. And so it works for me.

Fotografia

unread,
Feb 6, 2013, 5:42:10 PM2/6/13
to hugi...@googlegroups.com
Il giorno mercoledì 6 febbraio 2013 17:56:20 UTC+1, T. Modes ha scritto:
> Analyzing the log i see this message:
>
> Nessuna regola per generare l'obiettivo "/tmp/pano/pano/IMG_1947.JPG"
>
>
>
> Should be, in english, something like no rule to create target
> "/tmp/pano/pano/IMG_1947.JPG"
>
> I see /tmp/pano/pano/IMG_1947.JPG and not only /tmp/pano/IMG_1947.JPG .
> Maybe the problem is here?
>

The same path is used in the pto file:

===========================================================================
Input images
===========================================================================
Number of images in project file: 2
Number of active images: 2
Image 0: /tmp/pano/pano/IMG_1947.JPG
Image 0: Size 3648x2736, Exposure: 10.98
Image 1: /tmp/pano/pano/IMG_1948.JPG
Image 1: Size 3648x2736, Exposure: 11.57

So maybe you have saved the pto file in the parent folder and copied
the file later to the pano folder.

No i did everything from the gui.
 
I retried, this time images are in /tmp/prova

When i choose the point 2 (align) in the messages i see the right directory basename.

Also a strace: http://ubuntuone.com/3r5TPcaLMf1UQnEmtmLXwM


===========================================================================
***************  Panorama makefile generated by Hugin       ***************
===========================================================================
System information
===========================================================================
Operating system: GNU/Linux
Release: 2.6.32-45-generic
Kernel version: #102-Ubuntu SMP Wed Jan 2 22:38:04 UTC 2013
Machine: x86_64
Disc usage
File system            Dimens. Usati Disp. Uso% Montato su
/dev/sda1              29G  5,9G   22G  22% /

none                  996M  392K  995M   1% /dev
none                 1000M  184K 1000M   1% /dev/shm
none                 1000M  200K 1000M   1% /var/run
none                 1000M     0 1000M   0% /var/lock
none                 1000M     0 1000M   0% /lib/init/rw
/dev/sda2             663G  622G  7,2G  99% /home

Memory usage
             total       used       free     shared    buffers     cached
Mem:          1999       1778        220          0         64        753
-/+ buffers/cache:        960       1038

Swap:         2000          0       2000
===========================================================================
Output options
===========================================================================
Hugin Version: 2012.0.0.a94faa15c927
Project file: /tmp/huginpto_R115Wv

Output prefix: IMG_1947-IMG_1948
Projection: Rectilinear (0)
Field of view: 56 x 56
Canvas dimensions: 2767 x 2767
Crop area: (93,167) - (2755,2767)
Output exposure value: 11.28
Selected outputs
Normal panorama
* Blended panorama
===========================================================================
Input images
===========================================================================
Number of images in project file: 2
Number of active images: 2
Image 0: /tmp/prova/prova/IMG_1947.JPG

Image 0: Size 3648x2736, Exposure: 10.98
Image 1: /tmp/prova/prova/IMG_1948.JPG

Image 1: Size 3648x2736, Exposure: 11.57
===========================================================================
Testing programs
===========================================================================
Checking nona...[OK]
Checking enblend...[OK]
Checking enfuse...[OK]
Checking hugin_hdrmerge...[OK]
Checking exiftool...[OK]
===========================================================================
Stitching panorama
===========================================================================
make: ***  Nessuna regola per generare l'obiettivo "/tmp/prova/prova/IMG_1947.JPG", necessario per "IMG_1947-IMG_19480000.tif".  Arresto.


T. Modes

unread,
Feb 7, 2013, 11:22:51 AM2/7/13
to hugin and other free panoramic software
Hi fotografia,

>
> No i did everything from the gui.
>
> I retried, this time images are in /tmp/prova
>
> When i choose the point 2 (align) in the messages i see the right directory
> basename.
>
> Also a strace:http://ubuntuone.com/3r5TPcaLMf1UQnEmtmLXwM

I could not reproduce the issue on my system. Could you please provide
the pto file (without jpg images)?

Thomas

Fotografia

unread,
Feb 7, 2013, 12:58:16 PM2/7/13
to hugi...@googlegroups.com

T. Modes

unread,
Feb 7, 2013, 2:13:33 PM2/7/13
to hugin and other free panoramic software

>
> http://ubuntuone.com/6UZSkC9P7kisDXMwzeZk18
>
> Thank you.

Thanks for files.
In the pto file the relative path prova/IMG_1947.JPG is stored. When
using this relative path in the project file /tmp/prova/IMG_1947-
IMG_1948.pto this becomes /tmp/prova/ prova/IMG_1947.JPG, which does
not exists.
When you open this project, Hugin bails about missing files, correct?

But I don't understand why the relative path is stored inside the pto
file. I can't reproduce this issue. Can somebody else reproduce this
issue?
(Create directory /tmp/pano, copy image files to this dir, add these
images to a new project and save project in /tmp/pano; now check pto
file)

Thomas

Lukas Jirkovsky

unread,
Feb 7, 2013, 3:34:44 PM2/7/13
to hugi...@googlegroups.com
> But I don't understand why the relative path is stored inside the pto
> file. I can't reproduce this issue. Can somebody else reproduce this
> issue?
> (Create directory /tmp/pano, copy image files to this dir, add these
> images to a new project and save project in /tmp/pano; now check pto
> file)
>
> Thomas

If you load images first and then store the pto file, absolute paths
are used. If you store the pto file and then add images, it will use
relative paths. In fact I use this behavior quite a lot to make sure
hugin uses relative paths, because relative paths makes pto files more
portable.

Lukas

Carlos Eduardo G. Carvalho (Cartola)

unread,
Feb 7, 2013, 3:44:37 PM2/7/13
to hugi...@googlegroups.com
Hmm, thats an interesting and relevant knowledge.

Thanks,


2013/2/7 Lukas Jirkovsky <l.jir...@gmail.com>

--
--
You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



Fotografia

unread,
Feb 7, 2013, 6:46:18 PM2/7/13
to hugi...@googlegroups.com
Il giorno giovedì 7 febbraio 2013 20:13:33 UTC+1, T. Modes ha scritto:

>
> http://ubuntuone.com/6UZSkC9P7kisDXMwzeZk18
>
> Thank you.

Thanks for files.
In the pto file the relative path prova/IMG_1947.JPG is stored. When
using this relative path in the project file /tmp/prova/IMG_1947-
IMG_1948.pto this becomes /tmp/prova/ prova/IMG_1947.JPG, which does
not exists.
When you open this project, Hugin bails about missing files, correct?

Yes. A popup appears, with something like "can't find /tmp/prova/prova/IMG_1947.JPG"

T. Modes

unread,
Feb 8, 2013, 11:24:35 AM2/8/13
to hugin and other free panoramic software
Hi Lukas,

> If you load images first and then store the pto file, absolute paths
> are used. If you store the pto file and then add images, it will use
> relative paths. In fact I use this behavior quite a lot to make sure
> hugin uses relative paths, because relative paths makes pto files more
> portable.

Strange. But I can not reproduce this. If I store the pto file in the
same directory as the image, the pto files contains always relative
paths. (or if the pto file is saved in one of the parent directories
of the images. Only if this does not apply, absolute paths are used.)
It makes no difference if I start from scratch or use an existing file
- always relative paths.

Thomas

Fotografia

unread,
Feb 10, 2013, 5:37:58 AM2/10/13
to hugi...@googlegroups.com
Il giorno venerdì 8 febbraio 2013 16:24:35 UTC, T. Modes ha scritto:
Hi Lukas,

> If you load images first and then store the pto file, absolute paths
> are used. If you store the pto file and then add images, it will use
> relative paths. In fact I use this behavior quite a lot to make sure
> hugin uses relative paths, because relative paths makes pto files more
> portable.

Strange. But I can not reproduce this.

I tried Linux Mint 14 xfce from usb stick, booted, sudo apt-get install hugin (it is the 2011.04 version in the repo) and i see the same problem.

I copied 2 images in /tmp, then i choosed align but this time i choosed the proposed /home/mint as output directory.

Here the pto files: http://ubuntuone.com/3Vzno07UxCAKfZiYqhZMOG

Here is the output log:


===========================================================================
***************  Panorama makefile generated by Hugin       ***************
===========================================================================
System information
===========================================================================
Operating system: GNU/Linux
Release: 3.5.0-17-generic
Kernel version: #28-Ubuntu SMP Tue Oct 9 19:32:08 UTC 2012
Machine: i686
Disc usage
Filesystem      Size  Used Avail Use% Mounted on
/cow           1004M  288M  716M  29% /
udev            992M  4.0K  992M   1% /dev
tmpfs           402M  1.0M  401M   1% /run
/dev/sdd        872M  872M     0 100% /cdrom
/dev/loop0      840M  840M     0 100% /rofs
tmpfs          1004M  3.1M 1001M   1% /tmp
none            5.0M     0  5.0M   0% /run/lock
none           1004M   88K 1004M   1% /run/shm
none            100M  8.0K  100M   1% /run/user
/dev/sda2       663G  624G  5.1G 100% /media/mint/dc72152f-e9a1-4acb-94f6-a7505effc0d1

Memory usage
             total       used       free     shared    buffers     cached
Mem:          2006       1603        403          0        145       1146
-/+ buffers/cache:        311       1695

Swap:         2000          0       2000
===========================================================================
Output options
===========================================================================
Hugin Version: 2011.4.0.cf9be9344356
Project file: /tmp/huginpto_nbCgAB
Output prefix: IMG_3547-IMG_3548
Projection: Rectilinear (0)
Field of view: 80 x 53
Canvas dimensions: 4376 x 2626
Crop area: (66,221) - (4287,2128)
Output exposure value: 13.63

Selected outputs
Normal panorama
* Blended panorama
===========================================================================
Input images
===========================================================================
Number of images in project file: 2
Number of active images: 2
Image 0: /home/mint/IMG_3547.JPG
Image 0: Size 3648x2736, Exposure: 13.61
Image 1: /home/mint/IMG_3548.JPG
Image 1: Size 3648x2736, Exposure: 13.65

===========================================================================
Testing programs
===========================================================================
Checking nona...[OK]
Checking enblend...[OK]
Checking enfuse...[OK]
Checking hugin_hdrmerge...[OK]
Checking exiftool...df: `/root/.gvfs': Permission denied
make: [info] Error 1 (ignored)

[OK]
===========================================================================
Stitching panorama
===========================================================================
make: *** No rule to make target `/home/mint/IMG_3547.JPG', needed by `IMG_3547-IMG_35480000.tif'.  Stop.

Thank you again.

Lukas Jirkovsky

unread,
Feb 11, 2013, 3:02:56 PM2/11/13
to hugi...@googlegroups.com
On 8 February 2013 16:24, T. Modes <Thomas...@gmx.de> wrote:
> Hi Lukas,
>
> Strange. But I can not reproduce this. If I store the pto file in the
> same directory as the image, the pto files contains always relative
> paths. (or if the pto file is saved in one of the parent directories
> of the images. Only if this does not apply, absolute paths are used.)
> It makes no difference if I start from scratch or use an existing file
> - always relative paths.
>
> Thomas

Hi Thomas,
I'm sure it used to work like this at some point, because that's why
my workflow has been for years to save pto and then load images. Maybe
the behavior changed meanwhile.

Lukas
Reply all
Reply to author
Forward
0 new messages