[indiana-discuss] evince hangs in b101 after suspend-resume

[Andrew Gabriel]

solarg wrote:
> solarg wrote:
>>
>> Jürgen Keil wrote:
>
>>>
>>> Does a truss with option "-v all" reveal the IP address and TCP port 
>>> number
>>> that we're trying to connect to?
>>>
>>>   
>> i'm not able to reproduce the problem with evince, at the moment, it 
>
> correcxtion: the problem arises now when i'm trying to go into 
> submenus of evince, and truss reveals the same port and unix socket 
> concerned:
> /1:     connect(23, 0x08857618, 16, SOV_DEFAULT)        Err#146 
> ECONNREFUSED
> /1:             AF_INET  name = 127.0.0.1  port = 46541
> /1:     close(23)                                       = 0
> /1:     so_socket(PF_UNIX, SOCK_STREAM, 0, 0x00000000, SOV_DEFAULT) = 23
> /1:     fcntl(23, F_SETFL, FNONBLOCK)                   = 0
> /1:     fcntl(23, F_SETFD, 0x00000001)                  = 0
> /1:     getuid()                                        = 101 [101]
> /1:     connect(23, 0x087DD648, 48, SOV_DEFAULT)        Err#146 
> ECONNREFUSED
> /1:             AF_UNIX  name = 
> /var/tmp/orbit-henry/linc-2d4-0-49a39032c7fd8
> /1:     close(23)                                       = 0
> /1:     so_socket(PF_UNIX, SOCK_STREAM, 0, 0x00000000, SOV_DEFAULT) = 23 

On my system, the /var/tmp/orbit-* socket files seem to be applications 
connected to the /usr/lib/gconfd-2 process.
Do you have a gconfd-2 process running? If so, you could try trussing it 
to see if it looks wedged.
My gconfd-2 is also listening on a TCP port, although not the same port 
number as your connections are trying, but that might be dynamically 
chosen. I suspect applications may try the TCP connection if the named 
pipe connection fails, as there don't seem to be any actual TCP 
connections to my gconfd-2 process.

As to what gconfd-2 does, I've no idea.

-- 
Andrew