Red Hat Bugzilla – Bug 995551
regression: gthumb crashes on moving a file
Last modified: 2013-08-23 20:03:23 EDT
Description of problem:
gthumb crashes when I move a jpg file to another directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
More info soon.
This seems to be related to movie files and creating thumbnails (even though movies are disabled in preferences).
The console shows the following error:
totem-video-thumbnailer couldn't open file 'file:///home/blah/blah.mov'
This is a regression and a crash bug, any chance you could up the severity?
This crasher is fixed upstream. Any chance of a backport?
I tried to reproduce the problem:
- I can reproduce the issue described in https://bugzilla.redhat.com/show_bug.cgi?id=995724
- but it looks like that this is a different problem because the console output is different:
gthumb: symbol lookup error: /usr/lib/gthumb/extensions/libgstreamer_tools.so: undefined symbol: gst_is_video_overlay_prepare_window_handle_message
- the suggest upstream patch does not help for problem 995724
So far, I can't reproduce the problem of this bug report.
Occasionally (if the thumbnails cache is empty), I see the error messages from comment #2, but it does not seem to cause a crash.
Please can you try to describe exactly how the problem can be reproduced?
Are you using Dropbox by any chance? I have a feeling this might be linked to the com.dropbox.attributes xattr which a Mac writes...
Eventually I could reproduce the issue by copying a file with "Copy To..." into my home directory.
gthumb-3.2.3-2.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gthumb-3.2.3-2.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
gthumb-3.2.3-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.