Re: Strange font / frame size problem makes emacs unusable.

[Gaute Amundsen <gaute@div.org>]

On Mon, 2010-04-26 at 07:28 +0200, tomas@tuxteam.de wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sun, Apr 25, 2010 at 11:49:20PM +0200, Peter Dyballa wrote:
> >
> > Am 25.04.2010 um 21:43 schrieb Gaute Amundsen:
> >
> >> read(3, 0x9f10018, 4096)                = -1 EAGAIN (Resource
> >> temporarily unavailable)
> >> read(3, 0x9f10018, 4096)                = -1 EAGAIN (Resource
> >> temporarily unavailable)
> >
> > What is there "temporarily unavailable?" And why at all?
> >
> >> poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3,
> >> revents=POLLOUT}])
> >> writev(3, [{"2\30\21\0\1\0<\0", 8},
> >> {"-misc-fixed-medium-r-normal--161"..., 60}, {"", 0}], 3) = 68
> >
> >
> > [...] Find and check them! Some trace variant is able to record files 
> > being opened.
> 
> As Peter says, try to find what fd=3 is (somewhere higher in the trace
> there should be a call to open/connect returning 3).

Searching backwards for ' = 3$' in less gets me this bit:

socket(PF_FILE, SOCK_STREAM, 0)         = 3
connect(3, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X0"}, 20) = 0
getpeername(3, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X0i\1"}, [20])
= 0

To me that looks like a socket to the current X server.

> Linux makes it difficult to find the "other end" of a Unix domain
> socket; nevertheless, if you say "ls -l /proc/fd/<pid of your Emacs>,

ls -l /proc/<pid>/fd/ gives me "3 -> socket:[1218659]"
the first socket emacs opened.

> you'll see where fd3 is going to; with "lsof" or "netstat -axp" you'll
> "see" the connection, but not which process is at the other end...

Both say about the same yes.

emacs   11410 gaute    3u  unix 0xdd478000      0t0 1218659 socket

unix  3      [ ]         STREAM     CONNECTED     1218757  11410/emacs


> So your best bet is to search for connect/open/whatever other calls
> might be returning an fd of 3 up your trace.

Precisely :) 

So emacs is waiting a lot on X..
Particularly while doing something related to one enormous font.

But I can't say I've noticed any particular slowness otherwise..

And what related to X could have been disturbed by my moving of the
system.. 
The xorg.conf is default and as simple as can be.

My first intuition was that X somehow has saved, or relies on an
external "pointer", to a "video device" that is no longer there, and
emacs relies on some info about screen size that is now wrong or
missing.

Guess I could try to reproduce the problem in some other program that
relies on X... but what?

or I could try to start emacs with a remote X server in different ways.
Perhaps I could sidestep gnome somehow, and see if that's related.

But I ramble :)

Gaute