Comment 2 for bug 81219

Thanks for the comment, Cristian. I attach all the files as directed (I followed the Dapper instructions). I have cut the dmesg file to only include the messages produced from the moment the device was plugged in.

Be warned that the device is not exactly a USB key in its behavior. When it is first plugged in, it gets recognized as a Palm PDA (that's what the "Handspring Visor" messages are for). Then, you run an utility on the device and it starts to behave like a USB drive, so the kernel "sees" a disconnect from the Visor and a connect from the USB drives. The device used to work perfectly that way under Edgy and, just to try, I have done it the other way around (first enable "USB key mode", then plug it in) and the behavior is identical.

The result is always the same: the drives get recognized (as in, the scsi /dev/ entries are created and I can manually mount/unmount/use them) but only the SD card (first of the created drives) gets mounted (if a card is present, that is; in fact, the "photos found" dialog box pops up in that case). The "palmOne file storage" device does not get mounted automatically (no matter whether there is a SD card in the slot or not) but, as I just mentioned, I can access it just fine by mounting it manually.

Output of id: uid=1000(cepe) gid=1000(cepe) grupos=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),44(video),103(plugdev),107(lpadmin),108(scanner),1000(cepe)

Output of id hal: complains that the user hal does not exist

Output of id haldaemon: uid=118(haldaemon) gid=118(haldaemon) grupos=118(haldaemon),24(cdrom),25(floppy),103(plugdev),122(powerdev)

Output of uname -a: Linux ubuntu 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

I hope that sheds some light on the problem. Thanks for your help and don't hesitate to ask for any further information you might need.

Best regards.