Red Hat Bugzilla – Bug 145403
Save-as dialog crash on auto-mounted directories
Last modified: 2007-11-30 17:10:58 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
/net/p2 is NFS mounted on another computer using am-utils.
Use the "File => Save as..." menu to images opened in
NFS auto-mounted directories (no need to do any editing to the image).
[itai@itai ~]$ gimp /net/p2/big/itai-itai/Canon/2005-01-15_40/img_8469.jpg
*** glibc detected *** double free or corruption (fasttop): 0x0a7dbf40 ***
gimp: terminated: Aborted
Gimp then aborts and all changes to images are lost.
It worked OK when I used the /.automount/ name:
so the problem may be relaed to having symbolic links in path names.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: Gimp aborts and all changes to images are lost.
Expected Results: File save-as dialog box should appear
I don't know if this should be a separate feature request!
There must be a text-field in file dialog boxes, It is required if a
directory in the path is not readable, for auto-mounted directories or
for network files (eg., accessed using HTTP). And off-couse, to be
able to copy and paste path names with other applications.
(I was happy with the file dialogs in gimp-2.0.x).
Hmm, an application shouldn't behave differently when accessing a file
over symlinks instead of directly.
Can you run gimp please with enabled core files, i.e. run "ulimit -c
unlimited" in the same shell before running gimp? It should then dump
a core file (named "core.<pid>" where <pid> is the process ID of the
process that dumped the file) which would help in debugging the error.
Mind that there's an update on the way (gimp-2.2.2-0.fc3.3) with fixes
not related to your problem. Please state whether you used -0.fc3.2 or
-0.fc3.3 when generating the core file.
Created attachment 109918 [details]
Repeated same actions in and show stack trace in gdb
There is a similar problem with other programs. I changed the
component to gtk2. Installed components that may have effect on
Is there anything that I can do to promote fixing this bug?
If there are plans for switching to gtk-2.6.x I would be happy to try
it. I's prefer using binary RPMs and not compile it myself.
I have compiled and installed gtk+-2.6.2. That fixes he problem.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.