Bug 1275021 - Kernel Upgrade Killed Iphone Mounting
Kernel Upgrade Killed Iphone Mounting
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: ifuse (Show other bugs)
22
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Peter Robinson
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-24 22:20 EDT by vmjersey
Modified: 2016-07-19 16:15 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 16:15:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description vmjersey 2015-10-24 22:20:49 EDT
Description of problem:
I just used fedup to upgraded to 22.  When I plugged my iphone, I was able to mount it and see my pictures using shotwell.  

I did a "dnf -y update", which one updated the kernel files.  Now when I plug my iphone it, it won't accept the "trust computer" button that appears on my iphone.

Version-Release number of selected component (if applicable):

Kernel: 4.2.3
ifuse: 1.1.3
Iphone: iOS 9.1

How reproducible:  Everytime


Steps to Reproduce:
1.  Boot into kernel 4.2.3
2.  plug in Iphone
3.  Pull hair out of head

Actual results:


Expected results:


Additional info:
Comment 1 Fedora End Of Life 2016-07-19 16:15:07 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.

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