Bug 957162
| Summary: | [abrt] gvfs-mtp-1.16.1-1.fc19: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gal Leibovici <gleibovi> | ||||||||||||||||||||
| Component: | gvfs | Assignee: | Ondrej Holy <oholy> | ||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||
| Version: | 19 | CC: | alexl, bac_norman, bnocera, chrys87, danielhc99, dr.diesel, elwellj, evan, fonya, gwync, hancockrwd, hugh, ignatenko, ja, maj.linux, marcandre.lureau, marciobds, milan.kerslager, mswal2846, murray.alex, piowie, redhat-bugzilla, req1348, sanjay.ankur, srevivo | ||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||
| Whiteboard: | abrt_hash:6539328398377b638da591e2ad7043d7cd24b19f | ||||||||||||||||||||||
| Fixed In Version: | gvfs-1.16.4-2.fc19 | Doc Type: | Bug Fix | ||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||
| Last Closed: | 2014-06-10 03:14:15 UTC | Type: | --- | ||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||
|
Description
Gal Leibovici
2013-04-26 13:37:22 UTC
Created attachment 740395 [details]
File: backtrace
Created attachment 740396 [details]
File: cgroup
Created attachment 740397 [details]
File: core_backtrace
Created attachment 740398 [details]
File: dso_list
Created attachment 740399 [details]
File: environ
Created attachment 740400 [details]
File: limits
Created attachment 740401 [details]
File: maps
Created attachment 740402 [details]
File: open_fds
Created attachment 740403 [details]
File: proc_pid_status
After I clicked unmount in Nautilus, an error message popped up: "Unable to unmount Nexus 4: The connections is closed" Went to unmount / eject my Samsung Galaxy S 4 from nautilus side-bar and abrt popped up with gvfs-mtp crash reporter: libreport-2.1.4 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/3 executable: /usr/libexec/gvfsd-mtp kernel: 3.9.1-301.fc19.x86_64 package: gvfs-mtp-1.16.1-1.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Attempted to unmount a Galaxy S4 phone that was mounted. Unmounting hung and gave a timeout error, but then eventually unmount. reporter: libreport-2.1.4 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/1 executable: /usr/libexec/gvfsd-mtp kernel: 3.10.0-0.rc2.git2.1.fc20.x86_64 package: gvfs-mtp-1.16.2-2.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 Attempted to umount a Google Nexus 4. "Ejected" galaxy S3 via nautilus. It seemed to unmount successfully. The device does not show up in the notification area though. From Nautilus, after copying a file to a Samsung ACE2, and unmounting/ejecting the device. backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/3 executable: /usr/libexec/gvfsd-mtp kernel: 3.9.0-301.fc19.x86_64 package: gvfs-mtp-1.16.1-1.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 ureports_counter: 1 Happens when I click the eject icon in Nautilus for a Google Nexus 4. reporter: libreport-2.1.5 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 executable: /usr/libexec/gvfsd-mtp kernel: 3.9.5-301.fc19.x86_64 package: gvfs-mtp-1.16.3-1.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 Crashed while unmounting Nokia's folder. reporter: libreport-2.1.5 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 executable: /usr/libexec/gvfsd-mtp kernel: 3.9.5-301.fc19.x86_64 package: gvfs-mtp-1.16.3-1.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 Working with photos on Samsung Galaxy S II connected with MTP reporter: libreport-2.1.5 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/3 executable: /usr/libexec/gvfsd-mtp kernel: 3.9.8-300.fc19.x86_64 package: gvfs-mtp-1.16.3-2.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 i try to connect my samsung s2 via mtp reporter: libreport-2.1.6 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/1 executable: /usr/libexec/gvfsd-mtp kernel: 3.10.9-200.fc19.x86_64 package: gvfs-mtp-1.16.3-2.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 Works with my Galaxy S3, gvfs-mtp 1.16.3-2. I was trying to eject/dismount my Nexus 4 after loading some songs onto the internal hard drive of the device. reporter: libreport-2.1.6 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/7 executable: /usr/libexec/gvfsd-mtp kernel: 3.10.10-200.fc19.x86_64 package: gvfs-mtp-1.16.3-2.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000 I was detaching the phone, i think. BTW, my S3, when using gedit to open a text file shows only a string of numbers instead of file/folder names. Is this typical? reporter: libreport-2.1.7 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/22 executable: /usr/libexec/gvfsd-mtp kernel: 3.11.1-200.fc19.x86_64 package: gvfs-mtp-1.16.3-2.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 2746 I plugged in a Sony Xperia Go with CyanogenMod. reporter: libreport-2.1.8 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-mtp --spawner :1.3 /org/gtk/gvfs/exec_spaw/4 executable: /usr/libexec/gvfsd-mtp kernel: 3.11.1-200.fc19.x86_64 package: gvfs-mtp-1.16.3-2.fc19 reason: Process /usr/libexec/gvfsd-mtp was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000 The upstream patch potentially fix this issue: https://git.gnome.org/browse/gvfs/commit/?id=91bd02a0e3216d7b901405b7636055881867bf92 (according https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1194677/comments/6) Unfortunately I'm unable to reproduce it with my Android (gvfs-1.16.3-2.fc19.x86_64), does it occur every time when disconnecting? Could you reproduce it? No, it does not happen all the time ... at least for me. I'm running the same version of gvfs as you (gvfs-1.16.3-2.fc19.x86_64). gvfs-1.16.4-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gvfs-1.16.4-2.fc19 Package gvfs-1.16.4-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gvfs-1.16.4-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-22421/gvfs-1.16.4-2.fc19 then log in and leave karma (feedback). gvfs-1.16.4-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |