The GN is an MTP phone, and Banshee should be MTP capable assuming USE=mtp is set. It fails, however, to detect the phone being plugged in. media-sound/gmtp and sys-fs/mtpfs does not have this problem, so the issue appears to be with Banshee, specifically. Attaching output of mtp-detect for lack of ideas. Reproducible: Always
Created attachment 310707 [details] Output of mtp-detect with phone connected
Run banshee from a terminal and post its output here just after getting the failure please
There is no terminal output when plugging the device in. nolimitsoya@elin ~ $ banshee [Info 00:39:31.323] Running Banshee 2.4.0: [Gentoo/banshee/2.4.0-r1 (linux-gnu, x86_64) @ 2012-05-07 20:08:41 Local time zone must be set--see zic manual page] [Info 00:39:34.667] Updating web proxy from GConf [Info 00:39:35.144] All services are started 3.047852 [Info 00:39:37.544] nereid Client Started [Info 00:39:37.984] GStreamer version 0.10.35.0, gapless: True, replaygain: False (device plugged in at this point, but no further output.)
Have you checked /var/log/messages when you plug device in? Also attach ~/.xsession-errors after reproducing the problem
~/.xsession-errors contains nothing obviously related. It doesn't get recreated if I remove it, so i guess there's realy nothing written related to this. /var/log/everything/current (which i assume is the metalog equivalent of syslog-ng(?) /var/log/messages, that I don't have?) has this: May 12 01:27:29 [pulseaudio] [autospawn] core-util.c: Home directory /home/nolimitsoya not ours. May 12 01:27:29 [pulseaudio] [autospawn] lock-autospawn.c: Cannot access autospawn lock. May 12 01:27:29 [pulseaudio] [pulseaudio] main.c: Failed to acquire autospawn lock May 12 01:27:36 [kernel] [41325.528318] usb 2-2.1: new high-speed USB device number 7 using ehci_hcd May 12 01:27:36 [kernel] [41325.618725] usb 2-2.1: New USB device found, idVendor=04e8, idProduct=685c May 12 01:27:36 [kernel] [41325.618731] usb 2-2.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4 May 12 01:27:36 [kernel] [41325.618737] usb 2-2.1: Product: Galaxy May 12 01:27:36 [kernel] [41325.618742] usb 2-2.1: Manufacturer: samsung May 12 01:27:36 [kernel] [41325.618746] usb 2-2.1: SerialNumber: 0149C6F40700F007
Attach it anyway: 1. Logout 2. Log in 3. Open banshee 4. Attach that file
> May 12 01:27:36 [kernel] [41325.618725] usb 2-2.1: New USB device found, > idVendor=04e8, idProduct=685c $ qlist media-player-info | xargs grep -i 685c No results, but... $ qlist media-player-info | xargs grep -i 685 /lib/udev/rules.d/40-usb-media-players.rules:ATTRS{idVendor}=="04e8" , ATTRS{idProduct}=="6860|685e|685b" , ENV{ID_MEDIA_PLAYER}="samsung_galaxy-s2" /lib/udev/rules.d/40-usb-media-players.rules:ATTRS{idVendor}=="04e8" , ATTRS{idProduct}=="6602|6603|6640|681c|681d|685b|6877" , ENV{ID_MEDIA_PLAYER}="samsung_galaxy" /usr/share/media-player-info/samsung_galaxy-s2.mpi:DeviceMatch=usb:04e8:6860;usb:04e8:685e;usb:04e8:685b; /usr/share/media-player-info/samsung_galaxy.mpi:DeviceMatch=usb:04e8:6602;usb:04e8:6603;usb:04e8:6640;usb:04e8:681c;usb:04e8:681d;usb:04e8:685b;usb:04e8:6877;04e8:685e; Perhaps a missing device ID in the media-player-info package? Looked at upstream git and I'm not seeing this device ever getting added there: http://cgit.freedesktop.org/media-player-info/ Try adding the 685c to /lib/udev/rules.d/40-usb-media-players.rules and report back ?
(In reply to comment #7) > > May 12 01:27:36 [kernel] [41325.618725] usb 2-2.1: New USB device found, > > idVendor=04e8, idProduct=685c > > $ qlist media-player-info | xargs grep -i 685c > > No results, but... > > $ qlist media-player-info | xargs grep -i 685 > /lib/udev/rules.d/40-usb-media-players.rules:ATTRS{idVendor}=="04e8" , > ATTRS{idProduct}=="6860|685e|685b" , ENV{ID_MEDIA_PLAYER}="samsung_galaxy-s2" > /lib/udev/rules.d/40-usb-media-players.rules:ATTRS{idVendor}=="04e8" , > ATTRS{idProduct}=="6602|6603|6640|681c|681d|685b|6877" , > ENV{ID_MEDIA_PLAYER}="samsung_galaxy" > /usr/share/media-player-info/samsung_galaxy-s2.mpi:DeviceMatch=usb:04e8:6860; > usb:04e8:685e;usb:04e8:685b; > /usr/share/media-player-info/samsung_galaxy.mpi:DeviceMatch=usb:04e8:6602; > usb:04e8:6603;usb:04e8:6640;usb:04e8:681c;usb:04e8:681d;usb:04e8:685b;usb: > 04e8:6877;04e8:685e; > > Perhaps a missing device ID in the media-player-info package? Looked at > upstream git and I'm not seeing this device ever getting added there: > > http://cgit.freedesktop.org/media-player-info/ > > Try adding the 685c to /lib/udev/rules.d/40-usb-media-players.rules and > report back ? And /usr/share/media-player-info/samsung_galaxy.mpi or /usr/share/media-player-info/samsung_galaxy-s2.mpi Propably next to the ones it says 685b to see if 685c works on same merits. I'll close this pending on your testing & waiting a patch coming from you aimed at media-player-info. Please file also upstream bug for media-player-info with such patch attached.
Created attachment 311645 [details] xsession-errors - running Banshee and device plugged in
Samuli: media-player-info was not installed. Installing it and doing the edits you suggested did not change anything.
You will need to report this to media-player-info upstream I guess
Why? As I said, media-player-info wasn't even installed, and installing and "fixing" it didn't fix the bug I reported in the first place. I'm not saying that media-player-info might not need fixing too, but assuming that package is even needed, Banshee is missing a dependency, and is _still_ broken once that dependency is installed with the changes suggested here. I'd like this reopened; possibly with a title change.
+ 14 May 2012; Pacho Ramos <pacho@gentoo.org> banshee-2.4.0-r1.ebuild: + app-misc/media-player-info is needed as reported in bug #414513 by Bjoern + Ottervik and confirmed reading upstream release notes. + But you still need to report to upstream that your device is not supported
Please see: http://www.freedesktop.org/wiki/Software/media-player-info Under the 'Helping Out' section.
So, upstream says media-player-info doesn't even handle MTP devices. Can we please get this bug back where it started again? See → https://bugs.freedesktop.org/show_bug.cgi?id=49933#c2
(In reply to comment #15) > So, upstream says media-player-info doesn't even handle MTP devices. Can we > please get this bug back where it started again? > See → https://bugs.freedesktop.org/show_bug.cgi?id=49933#c2 "emerge -pv libmtp gvfs libgphoto2" output please
# emerge -pv libmtp gvfs libgphoto2 These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild R ] media-libs/libmtp-1.1.3::local-overlay USE="-doc -examples -static-libs" 0 kB [ebuild R ] gnome-base/gvfs-1.12.3 USE="bluetooth cdda http ios udev udisks -afp -archive -avahi -bluray -doc -fuse -gdu -gnome-keyring -gphoto2 -samba" 0 kB [ebuild R ] media-libs/libgphoto2-2.4.12 USE="exif jpeg nls -doc -examples -gd -zeroconf" CAMERAS="adc65 agfa_cl20 aox ax203 barbie canon casio_qv clicksmart310 digigr8 digita dimagev dimera3500 directory enigma13 fuji gsmart300 hp215 iclick jamcam jd11 jl2005a jl2005c kodak_dc120 kodak_dc210 kodak_dc240 kodak_dc3200 kodak_ez200 konica konica_qm150 largan lg_gsm mars mustek panasonic_coolshot panasonic_dc1000 panasonic_dc1580 panasonic_l859 pccam300 pccam600 polaroid_pdc320 polaroid_pdc640 polaroid_pdc700 ptp2 ricoh ricoh_g3 samsung sierra sipix_blink sipix_blink2 sipix_web2 smal sonix sony_dscf1 sony_dscf55 soundvision spca50x sq905 st2205 stv0674 stv0680 sx330z template topfield toshiba_pdrm11 tp6801" 0 kB Total: 3 packages (3 reinstalls), Size of downloads: 0 kB
Ok, sorryabout the noise, ignore 'local overlay' on libmtp. I was testing yesterday (while it still wasn't in portage) if -1.1.3 would help as it had a few Galaxy related additions. It didn't. The official 1.1.3 now in the tree doesn't help either. Output without my overlay was ↓ # emerge -pv libmtp gvfs libgphoto2 These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild R ] media-libs/libmtp-1.1.3::gentoo [1.1.3::local-overlay] USE="crypt%* -doc -examples -static-libs" 0 kB [ebuild R ] gnome-base/gvfs-1.12.3 USE="bluetooth cdda http ios udev udisks -afp -archive -avahi -bluray -doc -fuse -gdu -gnome-keyring -gphoto2 -samba" 0 kB [ebuild R ] media-libs/libgphoto2-2.4.12 USE="exif jpeg nls -doc -examples -gd -zeroconf" CAMERAS="adc65 agfa_cl20 aox ax203 barbie canon casio_qv clicksmart310 digigr8 digita dimagev dimera3500 directory enigma13 fuji gsmart300 hp215 iclick jamcam jd11 jl2005a jl2005c kodak_dc120 kodak_dc210 kodak_dc240 kodak_dc3200 kodak_ez200 konica konica_qm150 largan lg_gsm mars mustek panasonic_coolshot panasonic_dc1000 panasonic_dc1580 panasonic_l859 pccam300 pccam600 polaroid_pdc320 polaroid_pdc640 polaroid_pdc700 ptp2 ricoh ricoh_g3 samsung sierra sipix_blink sipix_blink2 sipix_web2 smal sonix sony_dscf1 sony_dscf55 soundvision spca50x sq905 st2205 stv0674 stv0680 sx330z template topfield toshiba_pdrm11 tp6801" 0 kB Total: 3 packages (3 reinstalls), Size of downloads: 0 kB
(In reply to comment #18) > Ok, sorryabout the noise, ignore 'local overlay' on libmtp. I was testing > yesterday (while it still wasn't in portage) if -1.1.3 would help as it had > a few Galaxy related additions. It didn't. > The official 1.1.3 now in the tree doesn't help either. > Output without my overlay was ↓ > > # emerge -pv libmtp gvfs libgphoto2 > > These are the packages that would be merged, in order: > > Calculating dependencies ... done! > [ebuild R ] media-libs/libmtp-1.1.3::gentoo [1.1.3::local-overlay] > USE="crypt%* -doc -examples -static-libs" 0 kB > [ebuild R ] gnome-base/gvfs-1.12.3 USE="bluetooth cdda http ios udev > udisks -afp -archive -avahi -bluray -doc -fuse -gdu -gnome-keyring -gphoto2 > -samba" 0 kB ^ Enable USE="gphoto2" in gnome-base/gvfs since pretty sure the dependency chain goes like: banshee -> gvfs -> libgphoto2 -> your device
After doing that it worked for about five connects or so. Then it stopped working. The next time I booted, it worked for even fewer connects, and then stopped working. Now it doesn't detect the phone getting plugged in at all again. It works _sometimes_ on a new user with a clean ~, but not all the time. Perhaps one in something-larger-than-ten. While it did connect, file transfer and transcoding seemed broken. The progress bar runs and it appears to be transfering, but the process is unbelievably fast and nothing actualy ends up on the device. It seems to get confused sometimes about wether the device is plugged in, or plugged out. Like it'll "detect" a connected Nexus first when I disconnect it, and un-detect it when I plug it back in. O.o After about thirty-odd tries just now, and more during the past days, I haven't been able to get in to connect when started from a terminal, so I don't think I have anything usefull to paste. Device detection in KDE works perfectly, but browsing the device (Doplhin) doesn't, if that's worth anything.
It might be worth to try uninstalling libmtp to avoid it confusing libghoto2 (both of these libraries do MTP independently) I'm sure I've seen bugs about this at our bugzilla but can't find none now In any case... You are the one with the device... You need to provide more information than just "it works sometimes" ;-)
(In reply to comment #21) > It might be worth to try uninstalling libmtp to avoid it confusing libghoto2 > (both of these libraries do MTP independently) > I'm sure I've seen bugs about this at our bugzilla but can't find none now > > In any case... You are the one with the device... You need to provide more > information than just "it works sometimes" ;-)
This is not resolved. I'll happily provide any info you request. There simply isn't anything changed in what I have provided already. Uninstalling libmtp didn't change anything. There is still no stderr/stdout output, the device never got detected again after the first three or four (fluke?) detects, and again, there is nothing in xsession-errors. Request something and you'll have it, but please don't assume it's resolved.
(In reply to comment #23) > This is not resolved. I'll happily provide any info you request. This might work in libgphoto2 ML or Gnome's bugzilla file against GVFS component but not here. I've been quite clear on pushing this forward in this bug imho, not sure what you are waiting for... > There simply isn't anything changed in what I have provided already. Yeah, you really need to deal this with upstream unless you are willing to donate Gentoo with one of these devices to debug the issue. Please reopen with futher information.
