Bug 699758 - Rhythmbox doesn't recognize iPhone
Summary: Rhythmbox doesn't recognize iPhone
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 15
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-26 14:42 UTC by redhat
Modified: 2012-08-07 15:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 15:13:35 UTC
Type: ---


Attachments (Terms of Use)

Description redhat 2011-04-26 14:42:13 UTC
Description of problem:
Rhythmbox doesn't recognize my iPhone; when I click 'Open Rhythmbox Music Player' in Nautilus, it opens, but does not display any iPhone connection at all.  The iPod plugin is installed and enabled.

Version-Release number of selected component (if applicable):
2.90.1 (Fedora 15 YUM repo)

How reproducible:
always

Steps to Reproduce:
1. Plug in iPhone
2. After Nautilus opens to reveal contents, click on 'Open Rhythmbox Music Player'

  
Actual results:
Rhythmbox starts but doesn't see iPhone

Expected results:
Rhythmbox starts and displays iPhone

Comment 1 Thomas Walker 2011-08-25 17:17:25 UTC
Came across this bug while researching why my iphone stopped showing up in rhythmbox after upgrading from fc14 to fc15.  I'm neither a gvfs nor rhythmbox expert but had a look under gdb and found a simple solution to my problem (and perhaps yours):

sudo modprobe fuse
cd /tmp && /usr/libexec/gvfsd -r &
attach iphone and open rhythmbox as normal

The problem seems to be that fc15 did away with the 'fuse' group to grant permission to /dev/fuse and instead defaults to perms 'root:root 0600' without the fuse module loaded, and 'root:root 0666' with the module loaded.  Under a clean fc15 install though, fuse doesn't load automatically so isn't available when the user logs in and gvfsd probes for fuse support (by trying to mount $HOME/.gvfs).  End result is that fuse support in gvfs is disabled (fuse_available == false) and calls like 'g_file_get_path (root)' in rb_ipod_helpers_get_itunesdb_path() get short-circuited to return NULL.  Restarting gvfsd after loading the fuse module seems to fix this.

It appears that these days the more permanent fix is something like the below to autoload fuse on boot:

echo "fuse" | sudo tee /etc/modules-load.d/fuse.conf

Which gets picked up by systemd somewhere long before the user logs in and gvfsd starts.

Anyway, perhaps this is indeed the problem you're having, perhaps not.  Hopefully it saves someone else a few hours of debugging regardless ;)

My versions of various related packages at the time of testing this:
gvfs-1.8.2-1.fc15.x86_64
gvfs-fuse-1.8.2-1.fc15.x86_64
gvfs-afc-1.8.2-1.fc15.x86_64
rhythmbox-2.90.1-10.git20110502.fc15.x86_64
libgpod-0.8.0-9.fc15.x86_64
ifuse-1.1.1-2.fc15.x86_64

btw- probably a gvfs bug that if the fuse module is loaded between when gvfsd is started and an iphone is plugged in, it appears to happily mount the device on $HOME/.gvfs/iphone (or whatever), oblivious to the fact that $HOME/.gvfs was never mounted (although the directory was created if it didn't exist prior) during the initial gvfsd startup.  Didn't dig into this much beyond the fact that calling g_file_get_path() on the iphone mount returns NULL and mucks up the rhythmbox device detection.

Comment 2 Fedora End Of Life 2012-08-07 15:13:38 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.