On 3/12/09 21:25, Wolf Drechsel wrote:
On 3/12/09 17:29, Wolf Drechsel wrote:
console.log
XFree86 Version 4.4.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) [DRI] screen 0 installation complete Screen 0 added: 1280x1024 @ (0,0) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! bash: no job control in this shell Setting Language: de_DE.UTF-8 Xlib: extension "RANDR" missing on display ":0.0".
o.k. - if the extension "RANDR" thing doesnt matter - can this be the problem?
system.log doesnt have any entries, crashreporter neither - so where else could I search for traces?
- No other error messages after 'Xlib: extension "RANDR" missing on display ":0.0".'?
Nope.
- Is the Inkscape icon appearing in the dock?
Yes.
- Did you try to rename the dot-directories that 'Inkscape Native'
uses ('~/.config/inkscape' and ~/.inkscape-etc') before launching 'Inkscape X11'?
Yes - doesnt matter.
- Last resort (as always): cleared the font cache with 'rm ~/.fontconfig/*' before launching 'Inkscape X11'?
Yes - doesnt matter.
(you could try to set the log file in 'Console.app' to 'All Messages' instead of 'Console messages', maybe there are some messages not included in the default 'Console' view)
How do I do that? -
nevermind - if you looked at system.log you saw all there is... (on Leopard: in 'Console.app' menu 'View > Log List', in the log list (sidebar on the left) expand the top most entry 'LOG DATABASE QUERIES' and select 'All Messages')
Interesting to watch is that according to "top" inkscape-bin grabs 90% of CPU power and stays on that for many minutes (tried it for nearly 40 minutes).
I'm clueless at the moment. What you could try to get more data while inkscape-bin is running:
1) open 'Activity Monitor' (graphical 'top') 2) select 'inkscape-bin' 3) 'View > Inspect Process', select 'Open Files and Ports' look at the list for any suspicious files inkscape-bin loads from outside the application bundle 5) 'View > Sample Process', save the result as text file and attach it, maybe it helps to determine where inkscape-bin hangs
Another thing you could test: rename (temporarily) your MacPorts tree '/opt/local' so that Inkscape can't load any files from there.
~suv