Ben NanoNote

Sign in or create your account | Project List | Help

Issue 18: vido white screen and hangs ben

Reported by David Samblas, Dec 18, 2009

Using unmodified , jut reflased Nanonote using the reflash_ben.sh.
Using this zim file (3,2GB) from a ext2 formated Sandisk 8Gb uSD
http://tmp.kiwix.org/zim/wikipedia_es_kiwix_120000+_06_2009_alpha4.zi

m

Result: just a blank screen and I need to reboot the  device,  here 
is the output

#vido wikipedia_es_kiwix_120000\+_06_2009_alpha4.zim 
commandline read: vido

   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.2 
|~~~~~~~~~~~~~~~~~~~~~~~~~~
        (c) 2001-2009  The world wide DirectFB Open Source Community
        (c) 2000-2004  Convergence (integrated media) GmbH
      
----------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2009-12-15 22:50) 
(*) Direct/Thread: Started 'VT Switcher' (624) [CRITICAL OTHER/OTHER 

0/0] <2093056>...
(*) Direct/Thread: Started 'VT Flusher' (625) [DEFAULT OTHER/OTHER 
0/0] <2093056>...
(*) DirectFB/FBDev: Found 'JZ4740 FB' (ID 0) with frame buffer at 
0x01980000, 300k (MMIO 0x13050000, 64k)
(*) Direct/Thread: Started 'Linux Input' (626) [INPUT OTHER/OTHER 
0/0] <2093056>...
(*) DirectFB/Input: gpio-keys (1) 0.1 (directfb.org)
(*) Direct/Thread: Started 'Linux Input' (627) [INPUT OTHER/OTHER 
0/0] <2093056>...
(*) DirectFB/Input: matrix-keypad (2) 0.1 (directfb.org)
(*) DirectFB/Graphics: Generic Software Rasterizer 0.6 
(directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(*) Direct/Thread: Started 'EventBufferFeed' (628) [MESSAGING 
OTHER/OTHER 0/0] <2093056>...
GConf Error: Failed to contact configuration server; some possible 
causes are that you need to enable TCP/IP networking for ORBit, or 
you have stale NFS locks due to a system crash. See 
http://www.gnome.org/projects/gconf/ for information. (Details -  1: 

Failed to get connection to session: dbus-launch failed to 
autolaunch D-Bus session: Autolaunch requested, but X11 support not 
compiled in.
Cannot continue.
)
GConf Error: Failed to contact configuration server; some possible 
causes are that you need to enable TCP/IP networking for ORBit, or 
you have stale NFS locks due to a system crash. See 
http://www.gnome.org/projects/gconf/ for information. (Details -  1: 

Failed to get connection to session: dbus-launch failed to 
autolaunch D-Bus session: Autolaunch requested, but X11 support not 
compiled in.
Cannot continue.
)

gtkhtml-ERROR **: gconf error: Failed to contact configuration 
server; some possible causes are that you need to enable TCP/IP 
networking for ORBit, or you have stale NFS locks due to a system 
crash. See http://www.gnome.org/projects/gconf/ for information. 
(Details -  1: Failed to get connection to session: dbus-launch 
failed to autolaunch D-Bus session: Autolaunch requested, but X11 
support not compiled in.
Cannot continue.
)

aborting...
(!) [  622:    0.000] --> Caught signal 6 (sent by pid 622, uid 
0) <--

Comment 1 by David Samblas, Dec 18, 2009

Bug identified by Mirko Vogt
"That's because of a bug / special behaviour (?) of dbus.
The short version:
vido is using gtkhtml, gtkhtml is using gconf, gconf is spawning
"dbus-launch --autolaunch". However the 
"--autolaunch" argument is only
available when dbus was compiled with libX11-support. As we're using
DirectFB instead of Xorg there's no need for libX11 support."

Patch in progress

Comment 2 by Wolfgang Spraul, Oct 2, 2010

vido is unmaintained, but won't be fixed
Status: WontFix

Created: 10 years 10 months ago by David Samblas

Updated: 10 years 18 days ago

Status: WontFix

Followed by: 1 person

Labels:
Type:Defect
Priority:Medium



interactive