For me, this bug (if it's one bug we're talking about) was caused, or
exposed, by a recent dist-upgrade to testing. I have a Motorola Xoom
that I mount on my Debian wheezy box with:
mtpfs -o allow_other /media/android
(run as root). This has worked with no problems since I got the Xoom
about a month ago. In particular it was working on Friday evening
January 31st. But then:
Start-Date: 2013-02-01 00:01:06
Commandline: apt-get -t testing dist-upgrade
This upgrade included:
Upgrade:
mtpfs:i386 (0.9-3+b1, 1.1-4),
libmono-system-xml4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
gnome-shell:i386 (3.4.2-5, 3.4.2-6),
libmono-sharpzip4.84-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
gnome-control-center:i386 (3.4.2+git20121016.29d7c0-1, 3.4.3.1-2),
libmono-cairo4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
libmono-system-configuration4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
libmono-i18n-west4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
libmono-posix4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
libmono-security4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
mono-gac:i386 (2.10.8.1-6, 2.10.8.1-7),
unattended-upgrades:i386 (0.79.3, 0.79.4),
libmono-system-drawing4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
libmono-system-security4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
libmono-corlib4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
mono-runtime:i386 (2.10.8.1-6, 2.10.8.1-7),
gnome-control-center-data:i386 (3.4.2+git20121016.29d7c0-1,3.4.3.1-2),
libmono-system4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
libmono-system-core4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7),
mono-4.0-gac:i386 (2.10.8.1-6, 2.10.8.1-7),
gnome-shell-common:i386 (3.4.2-5, 3.4.2-6),
libmono-i18n4.0-cil:i386 (2.10.8.1-6, 2.10.8.1-7)
End-Date: 2013-02-01 00:02:09
As soon as the upgrade completed, I was unable to mount the tablet or
communicate with it at all.
% mtpfs -o allow_other /media/android
Listing raw device(s)
Device 0 (VID=22b8 and PID=70a8) is a Motorola Xoom (ID 1).
Found 1 device(s):
Motorola: Xoom (ID 1) (22b8:70a8) @ bus 1, dev 3
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: (NULL)
fuse: bad mount point `/media/android': Transport endpoint is not connected
and:
cd /media/android
bash: cd: /media/android: Transport endpoint is not connected
and the /media/android directory is listed as:
d????????? ? ? ? ? ? android
`adb devices' shows no devices attached and `adb shell' reports:
error: device not found (fusermount -u /dev/android returns the
directory listing to normal, as reported by another user above).
mtab, however, does list the device as mounted:
mtpfs /media/android fuse.mtpfs
rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
Among the packages upgraded, presumably mtpfs is the likely
culprit. And presumably the problem was caused by whatever is
different between version 0.9-3+b1 and version 1.1-4. Looking at the
changelog, the only likely possibilities seemed to be a dependency on
fuse rather than on fuse-utils, or else the move to a new upstream
version.
I tried purging fuse-utils but that made no difference.
I tried to downgrade to mtpfs 0.9-3 0 in stable, but apt wanted to
remove grub in doing that, so ....
Installing libmtp9 from the experimental repository made no difference.
I hope this is helpful.
Jim McCloskey
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
