Bug 24

Summary: kserver-kdrive-fbdev {1.1.0,1.3.0} exits after first client disconnects
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Matt Hoosier <matt.hoosier>
Component: meta-yoctoAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: poky.bs.watcher, poky.watcher
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: x86   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Matt Hoosier 2007-07-14 19:49:10 UTC
Start the server:

  root@poky:# Xfbdev :0 -ac                                          
  _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6                
  _XSERVTransOpen: transport open failed for inet6/qemuarm:0                      
  _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6        
  Extended Input Devices not yet supported. Impelement it at line 637 in
  kinput.c

Do something with a client:

  root@poky:# DISPLAY=:0 xdpyinfo
  ...

Now the server aborts as soon as that client finishes:

  Fatal server error:                                                             
  could not open default font 'fixed'

I don't think that the problem is really a lack of built-in font information;
the enable-builtin-fonts patch is applied, and basically looks like the same
version that I've successfully used in non-Poky builds of X.

Moreover, the first client connects and does all its client-side font
manipulations with no trouble. Not sure why X would suddenly decide that it
needs to display a message on its own behalf.
Comment 1 Richard Purdie 2007-07-23 19:48:34 UTC
Dodji should have fixed this in r2212 (and filed the patch upstream)