Bug 24 - kserver-kdrive-fbdev {1.1.0,1.3.0} exits after first client disconnects
Summary: kserver-kdrive-fbdev {1.1.0,1.3.0} exits after first client disconnects
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 x86
: high normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2007-07-14 19:49 UTC by Matt Hoosier
Modified: 2010-12-21 06:07 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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)