Description of problem: Sorry for my poor english. I can reproduce this abort as I want. 1 - I choose the first font (Abyssibicia SIL, 9) in xfce4-apparence-setting, I validate and close xfce4-setting-manager 2 - With Thunar I right-clic on a file and choose "open with another application" Then thunar abend. Version-Release number of selected component: Thunar-1.6.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/Thunar crash_function: allocator_memalign executable: /usr/bin/thunar kernel: 3.8.3-203.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #8 allocator_memalign at gslice.c:1381 #9 allocator_add_slab at gslice.c:1252 #10 slab_allocator_alloc_chunk at gslice.c:1300 #11 magazine_cache_pop_magazine at gslice.c:724 #12 thread_memory_magazine1_reload at gslice.c:794 #13 g_slice_alloc at gslice.c:992 #14 pango_item_copy at pango-item.c:62 #15 pango_item_split at pango-item.c:146 #16 process_item at pango-layout.c:3420 #17 process_line at pango-layout.c:3595
Created attachment 715321 [details] File: backtrace
Created attachment 715322 [details] File: cgroup
Created attachment 715323 [details] File: core_backtrace
Created attachment 715324 [details] File: dso_list
Created attachment 715325 [details] File: environ
Created attachment 715326 [details] File: limits
Created attachment 715327 [details] File: maps
Created attachment 715328 [details] File: open_fds
Created attachment 715329 [details] File: proc_pid_status
Created attachment 715330 [details] File: var_log_messages
I have the same abend when I select a file in thunar and try to delete it whith keys shift+delete.
And if you set the font back to default the issue goes away?
(In reply to comment #12) > And if you set the font back to default the issue goes away? Yes, thunar works well when I use back the Sans font.
Would you care to file this upstream (bugzilla.xfce.org) ? Or would you prefer I do so?
(In reply to comment #14) > Would you care to file this upstream (bugzilla.xfce.org) ? Or would you > prefer I do so? I don't understand the question. Can you use more simple words and syntaxe ?
Can you file this bug again at bugzilla.xfce.org for the authors of the software to look at? Or, if you don't want to, I would be happy to do so. Just let me know. ;)
(In reply to comment #16) > Can you file this bug again at bugzilla.xfce.org for the authors of the > software to look at? > > Or, if you don't want to, I would be happy to do so. Just let me know. ;) Thank you to file this bug at bugzilla.xfce.org.
Upstream bug: https://bugzilla.xfce.org/show_bug.cgi?id=9953
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.