when plugging in a gphoto cam, import question appears twice

The reason for that are the supplemental fdi files which were introduced earlier
to make hal recognize selected camera models. This has been obsoleted by hal's
hotplug map scanning feature.

So the fix is to just remove all camera-related fdi files.

Created an attachment (id=432)
ubuntu8 interdiff to fix this

Patch looks good, go ahead

Fixed in:
 hal (0.2.98-1ubuntu8) warty; urgency=low
 .
   * deleted all digital camera fdi files from fdi/20freedesktop/ (and their
     entries in Makefile.am) since these are obsoleted by usb user map
     scanning; with the fdi files, you got two camera nodes for one device
     (Warty bug #8986)
   * ran autoreconf to activate the Makefile.am change

I have the same bug with my new Panasonic camera on Gutsy.

Michal, please do

  lshal > hal.txt

while the camera is plugged in and attach hal.txt here.

Hi,

I will in a few hours. The problem occurres on my parents pc which i dont have a direct access too. Actually, the last time the camera was plugged the import window appeared only once but im not sure if thats good news :)

Best regards,
Michal

im attaching the file you asked for

and a screenshot with two import windows (they appeared again).

michal

Thanks, Michal. The hal output is correct, there is just one camera in hal. Thus the original bug still remains fixed.

This seems to be a gnome-volume-manager bug instead. Michal, can you please do the following in a Terminal:

  killall gnome-volume-manager
  gnome-volume-manager -n 2>&1 | tee /tmp/gvm.log

Now please plug in your camera and switch it on. You should get some further text output. Now press Control-C, and run "gnome-volume-manager" to get the background instance back. Please attach /tmp/gvm.log here. Thank you!

here you go.

Ah, thanks. Your camera supports *both* mass-storage (i. e. behaves like an USB hard disk) and PtP (libgphoto2 support).

Note to self: g-v-m should ignore the PtP interface if it sees info.linux.driver = 'usb-storage'. A more robust solution would be to check if any peer interfaces are a mass storage device

thanks for the info! is there any temporary solution for this? the thing is, as i said, it it my parents PC and i ve been trying to convince them to use ubuntu instead of windows. the bug is kinda annoying thing for begginers like them coz they get totally confused where to click.

michal przadka [2008-01-03 18:24 -0000]:
> thanks for the info! is there any temporary solution for this? the thing
> is, as i said, it it my parents PC and i ve been trying to convince them
> to use ubuntu instead of windows. the bug is kinda annoying thing for
> begginers like them coz they get totally confused where to click.

Removing /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi
should do the trick:

  sudo rm /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi

afterwards, restart hal or reboot the machine:

  sudo /etc/init.d/hal restart

I have the same problem with an USB-Stick. I'm running a plain Ubuntu with KDE installed on top.
The critical thing is, that if I answer twice "yes" I get two konqueror windows and one of them has root permission!

From what I understand TOSHIBA is listed twice in the attached hal.txt

(K)UBUNTU 7.10 very happy with it!!

Juergen, this sounds very alarming! This bug is about GNOME, so Kubuntu needs a similar fix and should get a separately filed bug report. However, how did you check that it has root permissions? Can you please reproduce this situation, open a Terminal, and do

  ps aus > /tmp/ps.txt

and attach /tmp/ps.txt here?

We don't use g-v-m any more, but nautilus does the automounting now. It will pop up a dialog of possible actions instead of opening any application twice, so this should be fixed now.

This is still happening, I've just attached a Canon EOS 300D, and had both a "You have attached a camera" dialogue and the "you have attached removable media" dialogues open up.

Fresh install of Karmic, updated to latest packages.

Martin, please use "ubuntu-bug storage" to report a new bug. We don't use hal in Karmic any more for cameras, so the fix for this needs to be entirely different. Thanks!

Martin, please let me know the new bug number after you filed it.