Description of problem: Adjusting witdth of file name. I was unable to do so. The width went to minimum and when I tried to expand it the crash occurred. Version-Release number of selected component: pcmanfm-1.1.2-2.D20130830gitfc8adaab77.fc19 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: pcmanfm --desktop --profile LXDE crash_function: gtk_cell_renderer_get_aligned_area executable: /usr/bin/pcmanfm kernel: 3.11.2-201.fc19.x86_64 runlevel: N 5 type: CCpp uid: 500 var_log_messages: Oct 6 10:48:18 tower abrt[20361]: Saved core dump of pid 27668 (/usr/bin/pcmanfm) to /var/tmp/abrt/ccpp-2013-10-06-10:48:17-27668 (143847424 bytes) Truncated backtrace: Thread no. 1 (10 frames) #4 gtk_cell_renderer_get_aligned_area at gtkcellrenderer.c:1727 #5 render_cell at gtkcellarea.c:1151 #6 gtk_cell_area_box_foreach_alloc at gtkcellareabox.c:1296 #7 gtk_cell_area_real_render at gtkcellarea.c:1216 #8 _gtk_tree_view_column_cell_render at gtktreeviewcolumn.c:2956 #9 gtk_tree_view_bin_draw at gtktreeview.c:5121 #10 gtk_tree_view_draw at gtktreeview.c:5393 #11 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #12 gtk_widget_draw_marshallerv at gtkwidget.c:906 #13 _g_closure_invoke_va at gclosure.c:840
Created attachment 808624 [details] File: backtrace
Created attachment 808625 [details] File: cgroup
Created attachment 808626 [details] File: core_backtrace
Created attachment 808627 [details] File: dso_list
Created attachment 808628 [details] File: environ
Created attachment 808629 [details] File: limits
Created attachment 808630 [details] File: maps
Created attachment 808631 [details] File: open_fds
Created attachment 808632 [details] File: proc_pid_status
Is this still reproducible? If so, for sure what the following returns? $ rpm -q libfm
libfm-1.1.2.2-2.fc19.x86_64 I'm not sure if it's valid or not. I cannot reproduce it. I let abrt enter a bug just in case. I do know that it won't autosize the name field correctly. It will autosize based on the icon size. Weird. I'll see if there is some sort of bug report against that and file one.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.