Bug 156574 - gthumb will not "rename series" in directories with space
gthumb will not "rename series" in directories with space
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: gthumb (Show other bugs)
3
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Behdad Esfahbod
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-01 20:03 EDT by Mike Hudson
Modified: 2008-02-07 23:03 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-07 23:03:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike Hudson 2005-05-01 20:03:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
When I use the "rename series" (using th edate format) option it fails in a directory in which there is a space. 

"Could not rename the image
/path1/path with space/image 002.jpg
invalid parameter"

However when I move the image to a diffrent directory (with no space) it succeeds.
 

Version-Release number of selected component (if applicable):
gthumb-2.4.2-5

How reproducible:
Always

Steps to Reproduce:

  

Additional info:
Comment 1 Matthew Miller 2006-07-10 17:39:14 EDT
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.

Thank you!
Comment 2 petrosyan 2008-02-07 23:03:22 EST
Fedora Core 3 is not maintained anymore.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.

Note You need to log in before you can comment on or make changes to this bug.