Reply
Thread Tools
Posts: 439 | Thanked: 192 times | Joined on Oct 2009 @ spain-aragon-zaragoza
#1
Hello i open in a xterminal:

samipower@samipower-System-Product-Name:~$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &
[1] 1966
samipower@samipower-System-Product-Name:~$ Unrecognized option: -kb
use: X [:<display>] [option]
-a # default pointer acceleration (factor)
-ac disable access control restrictions
etc............................................... .................................................. ........................

and in other xterminal

samipower@samipower-System-Product-Name:~$ export DISPLAY=:2
samipower@samipower-System-Product-Name:~$ af-sb-init.sh start
af-sb-init.sh: orden no encontrada
samipower@samipower-System-Product-Name:~$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.
See /scratchbox/doc/ for documentation.

[sbox-FREMANTLE_X86: ~] > export DISPLAY=:2[sbox-FREMANTLE_X86: ~] > af-sb-init.sh startNote: For remote X connections DISPLAY should contain hostname!
Sample files present.
Starting DBUS system bus
Starting D-BUS session bus daemon
Starting Maemo Launcher: maemo-launcher.
maemo-launcher: warning raising the oom shield for pid=2098 status=5632
Starting Sapwood image server
Starting hildon-desktop
maemo-launcher: invoking '/usr/bin/hildon-desktop.launch'
maemo-launcher: invoking '/usr/bin/hildon-home.launch'
maemo-launcher: invoking '/usr/bin/hildon-status-menu.launch'
hildon-desktop[2133]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - remote volume monitor with dbus name org.gtk.Private.HalVolumeMonitor is not supported
hildon-home[2134]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - remote volume monitor with dbus name org.gtk.Private.HalVolumeMonitor is not supported
hildon-status-menu[2135]: GLIB WARNING ** GVFS-RemoteVolumeMonitor - remote volume monitor with dbus name org.gtk.Private.HalVolumeMonitor is not supported
sapwood-server[2113]: GLIB WARNING ** Gdk - cannot open display:
maemo-launcher: opening of /usr/bin/hildon-status-menu.launch took 17990 usec
maemo-launcher: opening of /usr/bin/hildon-home.launch took 38605 usec
hildon-status-menu[2135]: GLIB WARNING ** Gtk - cannot open display: :2
maemo-launcher: opening of /usr/bin/hildon-desktop.launch took 86815 usec
maemo-launcher: child (pid=2135) terminated due to exit()=1
Starting Keyboard
hildon-desktop[2133]: GLIB WARNING ** Gtk - cannot open display: :2
maemo-launcher: child (pid=2133) terminated due to exit()=1
hildon-input-method[2152]: GLIB WARNING ** Gtk - cannot open display: :2
Starting browser daemon: Initializing trackerd...
trackerd[2156]: GLIB DEBUG Tracker - Checking XDG_DATA_HOME is writable and exists
trackerd[2156]: GLIB MESSAGE Tracker - XDG_DATA_HOME set to '/home/samipower/.local/share'
trackerd[2156]: GLIB DEBUG Tracker - Path is OK
trackerd[2156]: GLIB MESSAGE Tracker - Setting IO priority
maemo-launcher: child (pid=2134) terminated due to signal=11
mafw-dbus-wrapper[2159]: GLIB WARNING ** mafw-gst-renderer - Could not initialize hal
trackerd[2156]: GLIB MESSAGE Tracker - Setting up stopword list for language code:'en'
trackerd[2156]: GLIB MESSAGE Tracker - Tracker couldn't read stopword file:'/usr/share/tracker/languages/stopwords.en', Failed to open file '/usr/share/tracker/languages/stopwords.en': open() failed: No such file or directory
trackerd[2156]: GLIB MESSAGE Tracker - Setting up stemmer for language code:'en'
browserd[2163]: GLIB WARNING ** Gtk - cannot open display: :2
browserd
/usr/bin/af-sb-init.sh: line 302: 2132 Segmentation fault /usr/bin/hildon-home
trackerd[2156]: GLIB MESSAGE Tracker - Registering DBus service...
Name:'org.freedesktop.Tracker'
[sbox-FREMANTLE_X86: ~] > Starting log:
File:'/home/samipower/.local/share/tracker/trackerd.log'
trackerd[2156]: GLIB CRITICAL ** Tracker - Could not initialize the HAL context, no error, is hald running?
Initializing tracker-indexer...
Starting log:
File:'/home/samipower/.local/share/tracker/tracker-indexer.log'
trackerd[2156]: GLIB WARNING ** Tracker - Could not add monitor for path:'/home/samipower/MyDocs/.camera'
trackerd[2156]: GLIB CRITICAL ** Tracker - Could not open directory 'file:///home/samipower/MyDocs/.camera': No such file or directory
[sbox-FREMANTLE_X86: ~] >


n900 emulator in my ubuntu 10.10 not open , why???

thanks

Last edited by samipower; 2011-01-27 at 11:49.
 
Posts: 1,463 | Thanked: 1,916 times | Joined on Feb 2008 @ Edmonton, AB
#2
well your first terminal window shows an error, you can't continue the steps until you resolve that.
try to remove the -kb since it is not recognizing that
it's a known issue that they removed the -kb option, i'm not sure why nobody updates the instructions, sorry...

Last edited by Creamy Goodness; 2011-01-26 at 01:48.
 

The Following User Says Thank You to Creamy Goodness For This Useful Post:
Posts: 439 | Thanked: 192 times | Joined on Oct 2009 @ spain-aragon-zaragoza
#3
I saw it, but if the original command line are

Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &

but it error

what do i use now?ŋ
 
Posts: 1,463 | Thanked: 1,916 times | Joined on Feb 2008 @ Edmonton, AB
#4
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac &
 

The Following User Says Thank You to Creamy Goodness For This Useful Post:
Posts: 439 | Thanked: 192 times | Joined on Oct 2009 @ spain-aragon-zaragoza
#5
thanks n900 emulator running

http://www.youtube.com/watch?v=LcL-2I7F_zc

Last edited by samipower; 2011-01-27 at 00:53.
 

The Following User Says Thank You to samipower For This Useful Post:
Posts: 1,048 | Thanked: 1,127 times | Joined on Jan 2010 @ Amsterdam
#6
Why they donīt update the instructions, you ask?

Have a look at this ancient rant asking, over and over, the same question. Great read if you ask me. Must read. Prior to install, that is...

http://mat.exon.name/logs/maemo

This whole SDK just seems to be a bunch of tools thrown together by a Fin that had a drink or two too much. Or perhaps he was short on drinks. Donīt know.
 
Posts: 1,463 | Thanked: 1,916 times | Joined on Feb 2008 @ Edmonton, AB
#7
samipower, glad you got it working now, hope you find it useful!

anthonie:
haha well the wiki has decent instructions now, and anyone can edit
them. i guess i'm just asking why i am too lazy myself
 

The Following User Says Thank You to Creamy Goodness For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 06:58.