Description of problem: Run trash-cli, nothing special. Version-Release number of selected component: trash-cli-0.12.9.14-8.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/trash-list crash_function: __fgets_unlocked executable: /usr/bin/python2.7 global_pid: 3062 kernel: 4.2.6-301.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __fgets_unlocked at iofgets_u.c:53 #1 __getmntent_r at mntent_r.c:130 #2 ffi_call_unix64 at ../src/x86/unix64.S:76 #3 ffi_call at ../src/x86/ffi64.c:525 #4 _call_function_pointer at /usr/src/debug/Python-2.7.10/Modules/_ctypes/callproc.c:836 #5 _ctypes_callproc at /usr/src/debug/Python-2.7.10/Modules/_ctypes/callproc.c:1179 #6 PyCFuncPtr_call at /usr/src/debug/Python-2.7.10/Modules/_ctypes/_ctypes.c:3965 #7 PyObject_Call at /usr/src/debug/Python-2.7.10/Objects/abstract.c:2529 #8 do_call at /usr/src/debug/Python-2.7.10/Python/ceval.c:4330 #9 call_function at /usr/src/debug/Python-2.7.10/Python/ceval.c:4135
Created attachment 1105546 [details] File: backtrace
Created attachment 1105547 [details] File: cgroup
Created attachment 1105548 [details] File: core_backtrace
Created attachment 1105549 [details] File: dso_list
Created attachment 1105550 [details] File: environ
Created attachment 1105551 [details] File: exploitable
Created attachment 1105552 [details] File: limits
Created attachment 1105553 [details] File: maps
Created attachment 1105554 [details] File: mountinfo
Created attachment 1105555 [details] File: namespaces
Created attachment 1105556 [details] File: open_fds
Created attachment 1105557 [details] File: proc_pid_status
Hiya, Looking into this now. The issue is reported upstream already. I'll build a new version with this patch and hopefully that'll fix it: https://github.com/andreafrancia/trash-cli/issues/52 https://github.com/andreafrancia/trash-cli/pull/53/files BTW, any reason this is a private bug? Doesn't seem to be a security issue or anything? Cheers, Ankur
*** Bug 1293065 has been marked as a duplicate of this bug. ***
(In reply to Ankur Sinha (FranciscoD) from comment #13) > > Looking into this now. The issue is reported upstream already. I'll build a > new version with this patch and hopefully that'll fix it: > > https://github.com/andreafrancia/trash-cli/issues/52 > https://github.com/andreafrancia/trash-cli/pull/53/files Did anything ever come of this fix, BTW? It doesn't appear that new RPMs were ever built, or at least I can't locate them in koji or any of the repos. In fact, it seems releng auto-built trash-cli for f24 last week, but that appears to still be the 0.12.9.14 version that's currently broken in F23. http://koji.fedoraproject.org/koji/packageinfo?packageID=10024 If the patches referenced did indeed fix the Python issues under F23+, it'd be a huge help if a new build could be pushed out, and (more importantly) make it into F24 before release. Thanks!
trash-cli-0.12.9.14-10git798b71d.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-bf9a22f717
trash-cli-0.12.9.14-10git798b71d.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-bf9a22f717
trash-cli-0.12.9.14-10git798b71d.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.