Bug 50482 - gnome-session will not start on 4.8-RC, X 4.3,
Summary: gnome-session will not start on 4.8-RC, X 4.3,
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-gnome (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-31 15:50 UTC by Joe Kelsey
Modified: 2003-04-04 07:53 UTC (History)
0 users

See Also:


Attachments
truss-sess (161.31 KB, text/plain)
2003-03-31 16:55 UTC, Joe Kelsey
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Kelsey 2003-03-31 15:50:08 UTC
	Installed latest gnome, fontconfig, pango, X 4.3, cvsup src-all,
	ports.  gnome-session will no longer start due to fontconfig
	problems.  However, I performed a truss of gnome-session and I
	can clearly see fontconfig reading all of the font-cache-1 files
	in the system.

How-To-Repeat: 	Install X4.3 from ports.
	Install Gnome2 from ports.
	Watch as gnome-session refuses to start.
Comment 1 Joe Marcus Clarke freebsd_committer 2003-03-31 16:35:14 UTC
Responsible Changed
From-To: freebsd-ports-bugs->gnome

Over to maintainers
Comment 2 Joe Marcus Clarke freebsd_committer 2003-03-31 16:35:28 UTC
State Changed
From-To: open->feedback

It works just fine for me on two RC machines.  Problems with fontconfig not 
finding ports should have been resolved with pango 1.2.1_2.  Try running 
fc-cache -f -v.  If that doesn't work, send me the output of the previous  
command. 

In the future, it would be helpful to get a little more info (like errors,  
truss output, etc.) to aid in troubleshooting.
Comment 3 Joe Kelsey 2003-03-31 16:52:56 UTC
I can send truss output.

There is absolutely no problem with fontconfig.  I re-install it and 
pango and everything else I can think of.  I run fc-cache -f -v multiple 
times.  I manually verify the font-cache-1 files.

The truss output clearly shows *something* opening and reading every 
single one of the font-cache files, so your blithe remarks about *it 
works for me" are completely useless and do nothing to solve the very 
real problems that I experience day in and day out.

You have done nothing to help solve the multiple fontconfig problems 
appearing in the field.  fc-cache is not the solution.

/Joe
Comment 4 Joe Marcus Clarke freebsd_committer 2003-04-04 07:53:25 UTC
State Changed
From-To: feedback->closed

This has been fixed by fontconfig 2.1.92.