Public bug reported:
After update to Ubuntu 14.04 latest alpha (all packages up to date as at
15/3/2014) I opened the application. SHotwell launched and then went
into the auto import (I had 9 new images in my library to import). The
screen then went grey and the application stopped responding, al
Public bug reported:
Viewing an event containing multiple pictures. Clicked on the left arrow
to go to the previous picture when the app stopped responding (window
went grey) and the crash occurred.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: shotwell 0.18.0-0ubuntu2
ProcVersionSignat
*** This bug is a duplicate of bug 1299664 ***
https://bugs.launchpad.net/bugs/1299664
Public bug reported:
Opened a zip file contained a number of folders (with .fla and .mp3
files in it if that is relevant). Dragged the top level folder to my
Music folder. Crash occurred - the files were no
Public bug reported:
Importing pictures from a 4GB Compact Flash card plugged in via a USB
card reader. After displaying about a third of the pictures the app
stopped responding and the crash occurred.
Ubuntu 13.10 beta (patched to 6/10/2013), 64 bit.
ProblemType: Crash
DistroRelease: Ubuntu 13.
It happens often enough that I thought it worthwhile to report as a bug,
but I can't reproduce it easily.
I have an old Canon DLSR and the transfer speed via USB was terrible so
I now do the transfer by taking the card out and putting it in a reader.
What I have found is that often, but not predic
Norbert, I have 13.04 beta running (64bit) and I only have the option to
eject, not safely remove.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1067876
Title:
Missing "Safely Remove
I had a similar problem too. I was trying to browse to another users
home folder to check disk usage. I launched a root nautilus through gksu
nautilus. When I right clicked on the folder (in this case 'pictures')
and selected properties I got the crash. Aport pointed me to this bug
rather than repo
