error when try to write comments

[procuste]

Using suse 11.1 and jbrout jbrout 0.3.174
if I try to add or modify a comment to a picture I receive this error:
Traceback (most recent call last):
File "/usr/share/jbrout/jbrout.py", line 1898, in
on_selecteur_menu_select_plugin
ret=callback(l)
File "/usr/share/jbrout/plugins/__init__.py", line 203, in
myCallBack
ret=callback(*a,**k)
File "/usr/share/jbrout/plugins/comment/__init__.py", line 47, in
comment
i.setComment(ret)
File "/usr/share/jbrout/jbrout/db.py", line 738, in setComment
if pc.addComment(txt):
File "/usr/share/jbrout/jbrout/tools.py", line 534, in addComment
self.__maj()
File "/usr/share/jbrout/jbrout/tools.py", line 515, in __maj
self.__info.writeMetadata()
RuntimeError: /dati/foto/diego/2008-2009-capodanno(anema e
core)/2008-2009-capodanno(anema e core){mik}415(anema e
core).jpg15295:
(1) (chmod)
have you any suggestion??
thanks a lot for any reply

[François Chartier]

I'd guess that your picture (or the filesystem) is not writeable...


2009/12/14 procuste <proc...@gmail.com>:

> --
>
> You received this message because you are subscribed to the Google Groups "jBrout" group.
> To post to this group, send email to jbr...@googlegroups.com.
> To unsubscribe from this group, send email to jbrout+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/jbrout?hl=en.
>
>
>

[manatlan]

i guess too

2009/12/15 François Chartier <chartier...@gmail.com>

[procuste]

On 15 Dic, 21:24, manatlan <manat...@gmail.com> wrote:
> i guess too
>

> 2009/12/15 François Chartier <chartier.franc...@gmail.com>

>
>
>
> > I'd guess that your picture (or the filesystem) is not writeable...

I solved putting "quiet" in fstab, the filesystem is fat32, now
comments are written well.
but I have some big (100MB) photos with extension jpeg, to inser them
in jbrout I have to change the extension in jpg, why?? and I noted
that with this photos is quite slow, is this a problem or normal?

[thierry benita]

2009/12/15 procuste <proc...@gmail.com>

This is normal as the file is loaded in order to get its metadatas.