Hide Forgot
Description of problem: plugging my Nexus-4 phone into F20 via USB causes rhythmbox to notice it as a media player. However, dragging music onto it causes a non-fatal kernel crash (attached) Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: I used to have F17 and have replaced it with F20. Under F17 it also didn't work, but I had successfully used a manually compiled go-mtpfs to successfully mount the Nexus and write to it - so I can state that there is no hardware or even "real" kernel problem with this situation - at least with the older F17 environment
More detail. I just had exactly the same (non-fatal) kernel error with a brand-new Nexus-7 tablet that I plugged into a rebooted F20 system. As before, the weird thing is that I get MTP errors in Rhythmbox when I try to drop music files from itself onto the Nexus-7, but if I look under /run/user/1000/gvfs/mtp\:host\=%5Busb%3A002%2C012%5D/Internal\ storage/Music/, I can copy mp3s just fine - without any errors - into there So maybe the real reason is that Rhythmbox is trying to write to an already mounted "disk"? ie either F20 should not mount the device (thereby giving rhythmbox exclusive access), or Rhythmbox should simply do a standard unix copy onto the mount path? Or something in between? ;-)
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.