Bug 922845 - [abrt] fontconfig-2.10.91-3.fc19: FcValueCanonicalize: Process /home/pungi/fedora/work/x86_64/yumroot/usr/bin/fc-cache was killed by signal 11 (SIGSEGV)
Summary: [abrt] fontconfig-2.10.91-3.fc19: FcValueCanonicalize: Process /home/pungi/fe...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cdbe47c13f617bb2174967d5a3b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-18 16:30 UTC by Sergio Basto
Modified: 2013-04-01 10:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-01 10:33:44 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (4.85 KB, text/plain)
2013-03-18 16:30 UTC, Sergio Basto 		no flags Details
File: build_ids (287 bytes, text/plain)
2013-03-18 16:30 UTC, Sergio Basto 		no flags Details
File: cgroup (129 bytes, text/plain)
2013-03-18 16:30 UTC, Sergio Basto 		no flags Details
File: environ (2.71 KB, text/plain)
2013-03-18 16:30 UTC, Sergio Basto 		no flags Details
File: limits (1.29 KB, text/plain)
2013-03-18 16:30 UTC, Sergio Basto 		no flags Details
File: maps (4.08 KB, text/plain)
2013-03-18 16:30 UTC, Sergio Basto 		no flags Details
File: open_fds (118 bytes, text/plain)
2013-03-18 16:31 UTC, Sergio Basto 		no flags Details
File: proc_pid_status (914 bytes, text/plain)
2013-03-18 16:31 UTC, Sergio Basto 		no flags Details
File: var_log_messages (368 bytes, text/plain)
2013-03-18 16:31 UTC, Sergio Basto 		no flags Details
View All

Description Sergio Basto 2013-03-18 16:30:35 UTC 
Description of problem:
composing f19 or rawhide with pungi 

Version-Release number of selected component:
fontconfig-2.10.91-3.fc19

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/fc-cache -f
core_backtrace: ac2f20e48715ae0113f48be73d22c9e1c54ca470 0x1a042 FcValueCanonicalize /lib64/libfontconfig.so.1 ca5f3247f8539fc35490452190ca28386761835e
crash_function: FcValueCanonicalize
executable:     /home/pungi/fedora/work/x86_64/yumroot/usr/bin/fc-cache
kernel:         3.8.3-201.fc18.x86_64
rootdir:        /home/pungi/fedora/work/x86_64/yumroot
uid:            0

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 FcValueCanonicalize at /lib64/libfontconfig.so.1
Comment 1 Sergio Basto 2013-03-18 16:30:38 UTC 
Created attachment 712097 [details]
File: backtrace
Comment 2 Sergio Basto 2013-03-18 16:30:40 UTC 
Created attachment 712098 [details]
File: build_ids
Comment 3 Sergio Basto 2013-03-18 16:30:43 UTC 
Created attachment 712099 [details]
File: cgroup
Comment 4 Sergio Basto 2013-03-18 16:30:50 UTC 
Created attachment 712100 [details]
File: environ
Comment 5 Sergio Basto 2013-03-18 16:30:55 UTC 
Created attachment 712101 [details]
File: limits
Comment 6 Sergio Basto 2013-03-18 16:30:57 UTC 
Created attachment 712102 [details]
File: maps
Comment 7 Sergio Basto 2013-03-18 16:31:01 UTC 
Created attachment 712103 [details]
File: open_fds
Comment 8 Sergio Basto 2013-03-18 16:31:08 UTC 
Created attachment 712104 [details]
File: proc_pid_status
Comment 9 Sergio Basto 2013-03-18 16:31:11 UTC 
Created attachment 712105 [details]
File: var_log_messages
Comment 10 Akira TAGOH 2013-03-21 09:45:24 UTC 
backtrace seems broken or stack was totally corrupted.

Is this issue reproducible? what fonts were on chroot?
Comment 11 Sergio Basto 2013-03-22 03:17:03 UTC 
(In reply to comment #10)
> backtrace seems broken or stack was totally corrupted.
> 
> Is this issue reproducible? what fonts were on chroot?

I think is not, not try it really, in reply of 2nd question, no idea. May be effects like in bug #907692 and unset DISPLAY, I _think_ that help on fontcfonfig works when compose repo f19 with pungi. 
but could be a mixed up fonts from different repos ..., so I think this bug can be closed ...
Comment 12 Akira TAGOH 2013-04-01 10:33:44 UTC 
Please retest with fontconfig-2.10.92-2. that may be improved perhaps. closing so far please reopen if you still this issue. thanks!
Note You need to log in before you can comment on or make changes to this bug.