Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1871442
Summary: | jmtpfs: crashes when started | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dominik 'Rathann' Mierzejewski <dominik> |
Component: | jmtpfs | Assignee: | Robert Scheck <redhat-bugzilla> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | redhat-bugzilla |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | jmtpfs-0.5-1.fc33 jmtpfs-0.5-1.fc32 jmtpfs-0.5-1.el7 jmtpfs-0.5-2.fc32 jmtpfs-0.5-2.fc33 jmtpfs-0.5-2.el8 jmtpfs-0.5-2.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-01-14 01:38:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dominik 'Rathann' Mierzejewski
2020-08-23 15:28:26 UTC
FEDORA-2021-5afd82bb39 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5afd82bb39 FEDORA-EPEL-2021-d2e48f2408 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d2e48f2408 FEDORA-2021-5727b9d170 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-5727b9d170 FEDORA-2021-5afd82bb39 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-5afd82bb39` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5afd82bb39 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-5727b9d170 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-5727b9d170` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5727b9d170 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-d2e48f2408 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d2e48f2408 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. As per https://bodhi.fedoraproject.org/updates/FEDORA-2021-5727b9d170#comment-1805486 this is still happening: $ jmtpfs Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device terminate called after throwing an instance of 'MtpErrorCantOpenDevice' what(): Can't open device Aborted (core dumped) $ jmtpfs --version jmtpfs version: 0.5 FUSE library version: 2.9.9 fusermount version: 2.9.9 using FUSE kernel interface version 7.19 Reported to upstream https://github.com/JasonFerrara/jmtpfs/issues/25 Btw, https://github.com/JasonFerrara/jmtpfs/issues/19#issuecomment-685705205 mentions a possible workaround. Dominik, could you test https://koji.fedoraproject.org/koji/taskinfo?taskID=59119895, please? It should fix the crash. Confirmed. It's no longer crashing and seems to work fine. Sorry, I was too quick. It's still crashing if an MTP device is mounted already: $ mount | grep mtp jmtpfs on /tmp/SAMSUNG_SAMSUNG_Android_42003714f287a4a3 type fuse.jmtpfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) $ jmtpfs Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device terminate called after throwing an instance of 'MtpErrorCantOpenDevice' what(): Can't open device Aborted (core dumped) $ rpm -q jmtpfs jmtpfs-0.5-1.1.fc33.x86_64 And it's still crashing if it's mounted by something else, e.g. GIO (a.k.a. GNOME VFS) $ gio mount -l ... Volume(0): SAMSUNG Android Type: GProxyVolume (GProxyVolumeMonitorMTP) Mount(0): SAMSUNG Android -> mtp://SAMSUNG_SAMSUNG_Android_42003714f287a4a3/ Type: GProxyShadowMount (GProxyVolumeMonitorMTP) Mount(1): mtp -> mtp://SAMSUNG_SAMSUNG_Android_42003714f287a4a3/ Type: GDaemonMount $ jmtpfs Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device terminate called after throwing an instance of 'MtpErrorCantOpenDevice' what(): Can't open device Aborted (core dumped) My mistake, I didn't apply the patch. https://koji.fedoraproject.org/koji/taskinfo?taskID=59181035 applies it really. FEDORA-2021-5727b9d170 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-5afd82bb39 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2021-62c72550e5 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-62c72550e5 FEDORA-2021-052a32b217 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-052a32b217 FEDORA-2021-d73a1ada4e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d73a1ada4e FEDORA-2021-052a32b217 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-052a32b217` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-052a32b217 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-d2e48f2408 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2021-7095bb6a7d has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-7095bb6a7d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-62c72550e5 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-62c72550e5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-d73a1ada4e has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d73a1ada4e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d73a1ada4e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-d73a1ada4e has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-052a32b217 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2021-7095bb6a7d has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2021-62c72550e5 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |