Bug 892450 - [abrt] nautilus-sendto-3.6.0-1.fc18: case_insensitive_hash: Process /usr/bin/nautilus-sendto was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-sendto-3.6.0-1.fc18: case_insensitive_hash: Process /usr/bin/...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus-sendto
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5fd0a84a9f4194f19f43b8de009...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-07 07:07 UTC by D. Charles Pyle
Modified: 2014-02-05 14:30 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:29:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (50.54 KB, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: cgroup (129 bytes, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: core_backtrace (5.53 KB, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: dso_list (19.29 KB, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: environ (1.75 KB, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: limits (1.29 KB, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: maps (99.06 KB, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: open_fds (346 bytes, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: proc_pid_status (935 bytes, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: smolt_data (2.78 KB, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details
File: var_log_messages (347 bytes, text/plain)
2013-01-07 07:07 UTC, D. Charles Pyle
no flags Details

Description D. Charles Pyle 2013-01-07 07:07:34 UTC
Description of problem:
Ran last collection of updates a few minutes ago. After that, printing crashes the system, sending files does not work, and I cannot even do day-to-day stuff involving printing pictures without some crash happening somewhere. The crashes happen 100% of the time.

Version-Release number of selected component:
nautilus-sendto-3.6.0-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        nautilus-sendto /tmp/shotwell-heThQS/Dreidel.png
crash_function: case_insensitive_hash
executable:     /usr/bin/nautilus-sendto
kernel:         3.7.1-2.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 case_insensitive_hash at fonts.c:757
 #1 pango_font_description_hash at fonts.c:786
 #2 pango_fc_fontset_key_hash at pangofc-fontmap.c:407
 #3 g_hash_table_lookup_node at ghash.c:401
 #4 g_hash_table_lookup at ghash.c:1074
 #5 pango_fc_font_map_load_fontset at pangofc-fontmap.c:1733
 #6 pk_pango_fc_font_map_load_fontset at pk-gtk-module.c:247
 #7 itemize_state_update_for_new_run at pango-context.c:1356
 #8 itemize_state_process_run at pango-context.c:1395
 #9 itemize_with_font at pango-context.c:1558

Comment 1 D. Charles Pyle 2013-01-07 07:07:37 UTC
Created attachment 673772 [details]
File: backtrace

Comment 2 D. Charles Pyle 2013-01-07 07:07:39 UTC
Created attachment 673773 [details]
File: cgroup

Comment 3 D. Charles Pyle 2013-01-07 07:07:40 UTC
Created attachment 673774 [details]
File: core_backtrace

Comment 4 D. Charles Pyle 2013-01-07 07:07:42 UTC
Created attachment 673775 [details]
File: dso_list

Comment 5 D. Charles Pyle 2013-01-07 07:07:44 UTC
Created attachment 673776 [details]
File: environ

Comment 6 D. Charles Pyle 2013-01-07 07:07:45 UTC
Created attachment 673777 [details]
File: limits

Comment 7 D. Charles Pyle 2013-01-07 07:07:46 UTC
Created attachment 673778 [details]
File: maps

Comment 8 D. Charles Pyle 2013-01-07 07:07:48 UTC
Created attachment 673779 [details]
File: open_fds

Comment 9 D. Charles Pyle 2013-01-07 07:07:49 UTC
Created attachment 673780 [details]
File: proc_pid_status

Comment 10 D. Charles Pyle 2013-01-07 07:07:51 UTC
Created attachment 673781 [details]
File: smolt_data

Comment 11 D. Charles Pyle 2013-01-07 07:07:52 UTC
Created attachment 673782 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2013-12-21 10:13:49 UTC
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.

Comment 13 Fedora End Of Life 2014-02-05 14:30:01 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.