No, the card wasn't removed/inserted at runtime; it was there at boot and stayed there.
The most reliable way to reproduce this issue is to go through QA's sanity test plan in order. By the time the mtp step is reached, it usually has devolved far enough to have several copies of the SD device. In the logs I'm attaching, it was shortly after boot so there were only two copies. I connected, selected one of the two SD devices, listed the contents of the root dir, then disconnected. The relevant bits start at 01:42:59 in the log, and go to the end. I think it's a phone-side bug, in part because the behavior depends on how long the device has been in use that boot, and in part because I see two copies of a file listed in the log under different object IDs. I0115 01:42:59.180575 2734 UbuntuMtpDatabase.h:154] Adding "/media/phablet/3562-3231/XposedCM10-10.1NetflixWorkaround-Dinc.apk" I0115 01:43:10.457561 2729 MtpObjectInfo.cpp:99] MtpObject Info 9: XposedCM10-10.1NetflixWorkaround-Dinc.apk I0115 01:43:11.222623 2729 MtpObjectInfo.cpp:99] MtpObject Info 372: XposedCM10-10.1NetflixWorkaround-Dinc.apk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389510 Title: SD card and contents listed several times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1389510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
