Created attachment 857920 [details] reverse order journalctl at time of abend Description of problem: Caja abends when closing window. Version-Release number of selected component (if applicable): Name : mate-file-manager Arch : x86_64 Version : 1.6.3 Release : 1.fc20 Name : abrt Arch : x86_64 Version : 2.1.11 Release : 1.fc20 How reproducible: It has happened 9 times since Jan 23. Just about every time it is used. Steps to Reproduce: 1. plug kindle into usb slot. Plug data stick into usb slot. 2. copy stuff to data stick. close data stick window (switch to kindle window). 3. eject data stick. 4. copy stuff to kindle. close kindle window 5. eject kindle. select File / Close (the one remaining window). Actual results: data stick and kindle are OK - data is not corrupted. However caja has abended. Expected results: caja does not abend. Additional info: When trying to report bug, get message "back trace is unusable" and bug is not reported using automated bug reporting tool.
Jan 31 08:07:46 fedorad.dswaner.home kernel: caja[16233]: segfault at 8 ip 0000003a634648b9 sp 00007fff1d2f3d70 error 4 in libglib-2.0.so.0.3800.2[3a63400000+129000] Honestly, i don't know why your kindle drive always crash caja. I will re-asign it to kernel, maybe thos guys can help us with analysing the issue.
Dear kernel-team, can you help us with this issue? see also https://bugzilla.redhat.com/show_bug.cgi?id=1055058 thanks
Processing the USB data stick and the kindle separately, not in the same caja execution, resulted in no abend. However, when tried a second time with just the kindle, the usual abend resulted. FWIW, when ejecting with the "eject" command, root privileges are necessary - you can umount as a normal user, but not eject (at least with my configuration).
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Kernel 3.13.4-200.fc20.x86_64 gave same result - caja segfaulted: caja[1284]: segfault at 0 ip 00000034b4c646d0 sp 00007fff35 f15a90 error 4 in libglib-2.0.so.0.3800.2[34b4c00000+129000]. Also still not able to do automatic bug report: reporting disabled because back trace is unusable.
This isn't a kernel problem. Even if the volume is not cleanly unmounted, the kernel isn't causing caja to segfault. That's a problem in caja itself.
With kernel-3.13.4-200.fc20.x86_64 and mate-file-manager-1.6.3-2.fc20.x86_64 the problem is still occurs sometimes, but not always.
Apparently the latest kernel has fixed the problem - caja no longer abends (for the last 4 days). kernel-3.13.5-200.fc20.x86_64, mate-file-manager-1.6.3-2.fc20.x86_64. Still getting message that kindle fs needs fsck.