I tried about a week ago same setup, on Debian 5.0. Everything worked as normal. Hardy worked just fine. I currently compiled latest libmtp, gnomad2 and Jaunty still mounts/docks incorrectly.
AT this point I feel that it has alot more to do with how it is being handled by the USBbus, not so much with gphoto, etc... The biggest hint I have is the double mounting aspect. When plugged in, in the past (and on Debian), the Zen will 'mount' briefly, then disengage, making it available to mount through gnomad, rhythmbox, etc... On Jaunty since early Alpha stages, when plugged in it does the same action, but then immediately mounts a second time (I can watch it happen on the Zen screen), and stays in a 'docked' state to the system. It does not work with Gnomad or Rhythmbox at this point. If I pick it from the desktop or from places, etc... and choose to eject, it frees up and then is available to use normally. This is the most obvious thing I see. Something changed in Jaunty as to how it is handled by USB, or by the system in general. Again, I am willing to help by tracking whatever else it may be. The above valgrind log may not show any error, but it was on and logging and I got the same Gphoto error when plugged in that time. Tell me what other info you might need. S* -- gvfsd-gphoto2 crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/349555 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
