Description of problem: 1. Opened a folder (e.g. /my/folder) 2. Highlighted a file from the folder 3. Pressed F2 to rename a file - a popup with the filename opened up 4. Copied the name of the file with ctrl+c (e.g. filename.ext) 5. Tried to paste the copied name to the address visible in the address bar (trying to concatenate the full file path like /my/folder/filename.ext) 6. Got the crash Version-Release number of selected component: pcmanfm-1.2.5-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: pcmanfm --desktop crash_function: fm_path_entry_completion_render_func executable: /usr/bin/pcmanfm global_pid: 1743 kernel: 4.10.5-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #7 fm_path_entry_completion_render_func at gtk/fm-path-entry.c:759 #8 apply_cell_attributes at gtkcellarea.c:1257 #9 g_hash_table_foreach at ghash.c:1608 #10 gtk_cell_area_real_apply_attributes at gtkcellarea.c:1286 #11 gtk_cell_area_box_apply_attributes at gtkcellareabox.c:1310 #12 _gtk_marshal_VOID__OBJECT_BOXED_BOOLEAN_BOOLEANv at gtkmarshalers.c:5027 #13 _g_closure_invoke_va at gclosure.c:867 #16 gtk_cell_area_apply_attributes at gtkcellarea.c:2373 #17 gtk_tree_view_column_cell_set_cell_data at gtktreeviewcolumn.c:2820 #18 set_cell_data at a11y/gtktreeviewaccessible.c:336
Created attachment 1267485 [details] File: backtrace
Created attachment 1267486 [details] File: cgroup
Created attachment 1267487 [details] File: core_backtrace
Created attachment 1267488 [details] File: dso_list
Created attachment 1267489 [details] File: environ
Created attachment 1267490 [details] File: limits
Created attachment 1267491 [details] File: maps
Created attachment 1267492 [details] File: mountinfo
Created attachment 1267493 [details] File: namespaces
Created attachment 1267494 [details] File: open_fds
Created attachment 1267495 [details] File: proc_pid_status
Created attachment 1267496 [details] File: var_log_messages
Well, currently I am unable to reproduce this. If you can reproduce this, can you make a movie for this?
Created attachment 1268918 [details] The requested movie with the moment of crash
Alright, please find the attached ogv. I've observed the problem more closely now. Seems there needs to be a couple (more than 1) folders in the working folder. The files are not needed. You can copy/paste any arbitrary string into the address bar, it will still cause the crash. The required condition is the list of subfolders that appears below after you put the "/" at the end of the folder name in the address bar. Regards
Thank you for providing movie. Well, however still I cannot reproduce this issue. Backtrace shows that the crash happens at: https://github.com/lxde/libfm/blob/1.2/src/gtk/fm-path-entry.c#L759 i.e. path completion function (i.e. trying to "complete" /tmp/test/XXXXXX), however looking at the code, the code seems something such crash should not happen. If you can try, would you try below? * Install libfm-debuginfo, pcmanfm-debuginfo by # dnf --enablerepo=\*debuginfo install libfm-debuginfo pcmanfm-debuginfo * Install valgrind by # dnf install valgrind * Invoke pcmanfm via valgrind as: # valgrind pcmanfm * If this crash still happens, would you write that valgrind log says?
Created attachment 1269191 [details] Log saved by running with valgrind Alright, debuginfo installed, the crash still happens. However running pcmanfm via valgrind drops back to shell and stops writing to the log. I even tried increasing the verbosity without luck. Attaching the log just in case. The log stops just after pcmanfm GUI appears.
(In reply to blachniom from comment #17) > Created attachment 1269191 [details] > Log saved by running with valgrind > > Alright, debuginfo installed, the crash still happens. > However running pcmanfm via valgrind drops back to shell and stops writing > to the log. > I even tried increasing the verbosity without luck. Attaching the log just > in case. > The log stops just after pcmanfm GUI appears. Ah, perhaps pcmanfm is already running as --desktop mode then. If you do $ ps auwwx | grep pcmanfm and when you see pcmanfm process is already running, please first kill it by $ pcmanfm --desktop-off If the above does not work, send SIGTERM (not SIGKILL) as $ killall -SIGTERM pcmanfm then try $ valgrind pcmanfm again. Thank you for trying!!
Created attachment 1269284 [details] Valgrind/pcmanfm log gathered again Ok, much better now. Didn't know desktop mode pcmanfm could cause such behaviour :) The attached log contains now a stack trace from the moment of the crash. Hope that's enough for you, I can't make much of it apart from some mallocfree. Thanks
Now this issue is reproducible to me.
libfm-1.2.5-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-185a953346
libfm-1.2.5-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9b0b1e1d7f
libfm-1.2.5-3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-c74484d3bd
Great! I've just downloaded libfm and the required dependencies from Koji. Everything seems alright so far. Thank you!
libfm-1.2.5-3.fc24 has been pushed to the Fedora 24 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-2017-185a953346
libfm-1.2.5-3.fc25 has been pushed to the Fedora 25 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-2017-9b0b1e1d7f
libfm-1.2.5-3.fc26 has been pushed to the Fedora 26 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-2017-c74484d3bd
libfm-1.2.5-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
libfm-1.2.5-3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
libfm-1.2.5-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.