Opened 16 years ago
Closed 8 years ago
#16977 closed defect (worksforme)
qtpfsgui crash saving exr
Reported by: | dershow | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | ||
Port: | qtpfsgui |
Description (last modified by jmroot (Joshua Root))
qtpfsgui seems to work fine for most functions now. But if I try to save an HDR image as a .exr it crashes. I can save with no problem as an .hdr. And if I convert an image to .exr using another tool, then qtpfsgui can open it. So it is able to find and use openexr for reading but not for writing.
The following appears in my system.log when the crash happens:
Oct 23 09:42:10 adamsmacbook-3 [0x0-0x91091].qtpfsgui[7812]: terminate called after throwing an instance of 'Iex::EaccesExc' Oct 23 09:42:10 adamsmacbook-3 [0x0-0x91091].qtpfsgui[7812]: what(): Cannot open image file "�Q9". Permission denied.
(Yes, those odd characters are the same as what appear in my system.log file for the file name....)
I can post the full crash report that is generated if that might help.
I am not sure if this is a more general problem with qtpfsgui, but I did search and didn't find other references to this problem, so I think that it might be specific to the MacPort version.
Thanks,
--Adam
Change History (5)
comment:1 Changed 16 years ago by (none)
Milestone: | Port Bugs |
---|
comment:2 Changed 14 years ago by jmroot (Joshua Root)
Cc: | clubjuggler@… dersh@… removed |
---|---|
Description: | modified (diff) |
Keywords: | crash removed |
Owner: | changed from macports-tickets@… to clubjuggler@… |
comment:3 Changed 14 years ago by jmroot (Joshua Root)
Is this still a problem with the current version?
comment:4 Changed 9 years ago by mf2k (Frank Schima)
Owner: | changed from clubjuggler@… to macports-tickets@… |
---|
This port no longer has a maintainer. See #47483.
comment:5 Changed 8 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I am unable to replicate this error.
Perhaps a version update has fixed this error.
Milestone Port Bugs deleted