Photo import failed with specific usb controller

[Eungkyu Song]

When f-spot is importing mass photos, It stop with following error message.
(also stop with gthumb and nautilus' copy, too)

Unspecified error
Error GeneraError: LibGPhoto2.GPhotoException: Unspecified error
  at LibGPhoto2.CameraFilesystem.GetFile (System.String folder, System.String filename CameraFileType type, LibGPhoto2.Context context) [0x00000]
  at GPhotoCamera.GetFile (Int32 index) [0x00000]
  at GPhotoCamera.SaveFile (Int32 index, System.String filename) [0x00000]
  at FSpot.CameraFileSelectionDialog.SaveFile (Int32 index) [0x00000]
  at FSpot.CameraFileSelectionDialog.Download() [0x00000]

Very interesting thing is that this is occurred only when camera is connected at "00:0f.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)"

Importing process is slow but gracefully completed when connected at "00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)"

ALi's usb controller is attached at PCI slot because I don't have on-board usb 2.0 controller.

And following messages are written at /var/log/kern.log while importing photos.

Apr 8 00:48:45 eungkyu kernel: [ 3793.718218] usb 6-6: new high speed USB device using ehci_hcd and address 7
Apr 8 00:48:45 eungkyu kernel: [ 3793.853146] usb 6-6: configuration #1 chosen from 1 choice
Apr 8 00:49:36 eungkyu kernel: [ 3844.971649] usb 6-6: USB disconnect, address 7
Apr 8 00:49:36 eungkyu kernel: [ 3845.214656] usb 6-6: new high speed USB device using ehci_hcd and address 8
Apr 8 00:49:37 eungkyu kernel: [ 3845.349505] usb 6-6: configuration #1 chosen from 1 choice

Device is automatically disconnected and reconnected while importing and importing stopped. Of course, I didn't do that

I think this bug is about kernel. I'm sorry that I reported at libgphoto2. I can't find the correct kernel package name.

uname -a says that

Linux eungkyu 2.6.24-15-generic #1 SMP Fri Apr 4 03:48:31 UTC 2008 i686 GNU/Linux

Thank you.

[Stolen (colin-shaw)]

I am also seeing this bug. It does not appear to be a kernel issue, but an issue with f-spot. I can import photos using gtkam.
stolen@beast:/etc$ lsusb
Bus 002 Device 008: ID 04b0:0406 Nikon Corp. DSC D70 (ptp)
Bus 002 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 002 Device 002: ID 046d:c518 Logitech, Inc. MX610 Laser Cordless Mouse
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Starting f-spot from the command line, I get this output on the console:
stolen@beast:/etc$ f-spot
Starting new FSpot server
Reloading
item changed
hda3 (10.1 GB) - gnome-dev-harddisk - Mountpoint file:///media/hda3 True True Harddrive
Harddrive
hda2 (48.8 GB) - gnome-dev-harddisk - Mountpoint file:///media/hda2 True True Harddrive
Harddrive
hda1 (16.0 GB) - gnome-dev-harddisk - Mountpoint file:///media/hda1 True True Harddrive
Harddrive
/storage (298.1 GB) - gnome-dev-harddisk - Mountpoint file:///storage True True Harddrive
Harddrive

(f-spot:11131): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
item ImportCommand+SourceItem
Testing gphoto path = usb:
PortInfo Universal Serial Bus, usb:
Error GeneraError: LibGPhoto2.GPhotoException: Unspecified error
  at LibGPhoto2.CameraFilesystem.ListFiles (System.String folder, LibGPhoto2.Context context) [0x00000]
  at GPhotoCamera.GetFileList (System.String dir) [0x00000]
  at GPhotoCamera.GetFileList (System.String dir) [0x00000]
  at GPhotoCamera.GetFileList () [0x00000]
  at GPhotoCamera.InitializeCamera () [0x00000]
  at MainWindow.ImportCamera (System.String camera_device) [0x00000]
cleanup context
cleanup context
cleanup context
stolen@beast:/etc$

[Eungkyu Song (eungkyu)]

To Stolen.

Your call stack is differenct from mine.
While importing can you see the kernel message reporting that USB device is disconnecting and re-connecting?
And I have failed with f-spot, gthumb and nautilus.
I think this is not a problem of f-spot.

[Leann Ogasawara (leannogasawara)]

Hi Eungkyu,

Care to confirm this is still an issue with the latest Alpha for the upcoming Intrepid Ibex 8.10. You should be able to test via a LiveCD - http://www.ubuntu.com/testing. Please let us know your results. If the issue still exists, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!