Re: [maemo-developers] 770 display failure workaround
Hi, What I mean to say is, it's a Hardware failure...but with a software workaround...so it's a software failure not to handle the potential hardware failure. But obviously the powers that be don't agree. I say put the code in the official kernel image... Or? Regards, -- Philippe Laporte Software Gatespace Telematics Första Långgatan 18 41328 Göteborg Sweden Phone: +46 702 04 35 11 Fax: +46 31 24 16 50 Email: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: -- original message -- Subject:Re: [maemo-developers] 770 display failure workaround From: Ed Okerson [EMAIL PROTECTED] Date: 27th March 2006 3:37:59 pm Hi, Does anyone have a patch for the 770 display failure? How about a kernel image? :-) Software cannot fix a hardware failure. --- i heard from a good source that it's a software failure, and of a workaround. White vertical lines, no nokia splash... ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Hi...Please clarify my doubt
Hi Friends,I am new for this group. Recently, I got Nokia 770 Internet tablet. Now, I am using SuSe Linux 9.3 in my system. Just, I want to display "Hello World" in my Nokia 770 device, which is developed in GTK (As recommonded). How can I port the "hello world" program into my device. Can you please tell me the step by step procedure to solve my problem. This is very urgent. I will be waiting for your reply.Thank you.With regards, CrazyBoy. Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1/min.___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building deb packages for the Nokia 770 is very easy
Hi, I added a HowTo to the Maemo Wiki: http://maemo.org/maemowiki/HowTo_SimpleDeb regards, Armin. -- --- May the Source be with you! Linux. --- --- secure eMail: http://www.gnupg.de/ --- --- My Homepage http://armin-warda.de/ --- pgptKIcqY9qUe.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Hi...Please clarify my doubt
Crazy Boy wrote: I am new for this group. Recently, I got Nokia 770 Internet tablet. Now, I am using SuSe Linux 9.3 in my system. Just, I want to display Hello World in my Nokia 770 device, which is developed in GTK (As recommonded). How can I port the hello world program into my device. Can you please tell me the step by step procedure to solve my problem. This is very urgent. I will be waiting for your reply. For urgent cases I recommend using a search engine (e.g. with keywords maemo hello world or maemo tutorial). This will lead you to http://www.maemo.org/platform/docs/howtos/howto_making_an_application_package.html and http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html, respectively. HTH, -- Jussi Kukkonen [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Scheme for 770 available
Stephen DeGabrielle [EMAIL PROTECTED] writes: I have just made mzscheme for the In roughly the same area, I've been working on Guile packages for the 770. So far I have guile, slib, g-wrap and guile-gnome packaged. They basically work, but there are issues to iron out with how some of the Gtk and Hildon widgets are wrapped, so I wouldn't say it's fully ready yet. (If anyone is interested to help me with this, please let me know.) Neil ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: Building deb packages for the Nokia 770 is very easy
Thanks Armin, It's good to see how these things fit together. I'd really like to just use 'dpkg-buildpackage -rfakeroot -b' but it spits errors at me; My problem seems to be that I use ./configure;make;make install to compile. the Maemo Tutorial seems to want me to 'Run autogen.sh to generate application build configures: ' I don't have an autogen.sh to run to I fell back on to good old ./configure;mke;make install I believe this is why my attempts at a standard package fail; -- [EMAIL PROTECTED]:~$ /scratchbox/login Welcome to maemo Development Platform 1.1! For further information please check out the official maemo website at http://www.maemo.org/. Copyright (c) 2005 Nokia [sbox-SDK_ARM: ~] cd plt [sbox-SDK_ARM: ~/plt] cd src/ [sbox-SDK_ARM: ~/plt/src] ls Makefile README config.h.in config.status ltmzscheme wxxt Makefile.in autogen.sh config.log configure mred wxcommon [sbox-SDK_ARM: ~/plt/src] dpkg-buildpackage -rfakeroot -b dpkg-parsechangelog: error: cannot open debian/changelog to find format: No such file or directory dpkg-buildpackage: unable to determine source package [sbox-SDK_ARM: ~/plt/src] -- [I even went to the extent of building from the latest stable source package for plt-scheme from the debian packages repository. ] I am tempted to package it up by hand - do you think I could just make up the contents of the 'control' file? eg --control-- Package: mzscheme Version: 209 Section: unstable Priority: optional Architecture: arm Depends: maemo Installed-Size: what here Maintainer: Stephen De Gabrielle Stephen.DeGabrielle AT gmail.com Description: mzscheme --end- What do you think? (I would really just prefer 'dpkg-buildpackage -rfakeroot -b' ) Stephen On 3/28/06, Armin M. Warda [EMAIL PROTECTED] wrote: Hi Stephen, On Tuesday 28 March 2006 07:27, Stephen DeGabrielle wrote: [...] as I have not worked out how to package it yet [...] Building deb packages for the Nokia 770 is actually very easy, if you know how. This posting explains the basic structure of a simple package: http://maemo.org/pipermail/maemo-users/2006-March/000853.html regards, Armin. -- --- May the Source be with you! Linux. --- --- secure eMail: http://www.gnupg.de/ --- --- My Homepage http://armin-warda.de/ --- -- -- Stephen De Gabrielle ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] 770 display failure workaround
Ok. So, for the second time, what is the workaround? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Philippe Laporte Sent: Tuesday, March 28, 2006 1:11 AM To: maemo developers Subject: Re: [maemo-developers] 770 display failure workaround Hi, What I mean to say is, it's a Hardware failure...but with a software workaround...so it's a software failure not to handle the potential hardware failure. But obviously the powers that be don't agree. I say put the code in the official kernel image... Or? Regards, -- Philippe Laporte Software Gatespace Telematics Första Långgatan 18 41328 Göteborg Sweden Phone: +46 702 04 35 11 Fax: +46 31 24 16 50 Email: [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: -- original message -- Subject: Re: [maemo-developers] 770 display failure workaround From: Ed Okerson [EMAIL PROTECTED] Date: 27th March 2006 3:37:59 pm Hi, Does anyone have a patch for the 770 display failure? How about a kernel image? :-) Software cannot fix a hardware failure. --- i heard from a good source that it's a software failure, and of a workaround. White vertical lines, no nokia splash... ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: Building deb packages for the Nokia 770 is very easy
disse -- Stephen DeGabrielle originais - My problem seems to be that I use ./configure;make;make install to compile. Not sure about this but could you not use checkinstall (http://asic-linux.com.mx/%7Eizto/checkinstall/) to make the .deb? abraços Ian -- .''`. : :' : `. `'` `- Orgulhoso ser MetaRecicleiro ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: Disconnect rfcomm stays between bt_disconnected and rf_disconnected
2006/3/28, Jari Tenhunen [EMAIL PROTECTED]:
On Tue, Mar 28, 2006 at 04:45:05PM +0200, koos vriezen wrote:
2006/3/27, Jari Tenhunen [EMAIL PROTECTED]:
I don't really follow, what are you trying to say here?
We will release the BT plugin soon and Tapio will probably release an
updated GpsDrive package that will work with it.
That is great. I got the impression that there wasn't any work being
done for this. The version at ApplicationCatalogWip is from nov'05.
Is there a public CVS repository or snapshots available. (my problem
is that I need it ASAP, will be on the road a lot the coming weeks).
Would be great if I can test your newly BT plugin and see if it's any
better than what I have now (eg. could be my el-cheapo GPS receiver as
well).
Can you answer this please, I really want to get this going real soon.
Currently there is no CVS or SVN repository for the project but we hope
to get one real soon. The updated GpsDrive might available already
tonight, I'll send you an email once it's there.
If you're *really* in a hurry and can't wait for the official release
(should happen some time this week) I can send you a binary pre-release
of the BT plugin (the configuration tool I mentioned) that works with
the updated GpsDrive.
Patience, my friend ... =)
Ok, this week sound fast enough ;-)
Maybe you can help solving the PIN issue. If I connect, I get the
'pin_req' signal, but where should I send the pin to? I did register
an object path with 'com.nokia.btpin.request.register' (and I did do
'dbus_bus_acquire_service' and 'dbus_connection_register_object_path'
for it), but the callback is never called.
How does that work?
What now happens is a pin popup, which also works for setting up this
connection.
My code is based on Tomas Junnonen's btkeyboard-plugin,
http://770.fs-security.com/keyboards.html, you may find some help there.
I can get back on this issue later when I'm not so busy...
Darn I made a mistake, shouldn't have added the 'request' path on
btpin. Anyhow, my version works for me. Attached the source for anyone
that may need some extra references on dbus-0.23 (I didn't find
anything useful for this version, only at
https://stage.maemo.org/viewcvs.cgi/maemo/projects/haf/branches/libosso/0.9-branch/src/
).
This is really a quick dirty tool to get it working, run as
LD_LIBRARY_PATH=/var/lib/install/usr/lib bt-gps BT-Address PIN
(library path is for launching gpsd)
I also noted that once gpsdrive reports a timeout on the GPS, gpsd
hangs and isn't killable w/ INT or TERM. Only KILL will do then, so
this little app also does that :-)
Koos
//#include config.h
// gcc -o bt-gps bt-gps.cpp `pkg-config --cflags dbus-glib-1 --libs` -s
#include math.h
#include string.h
#include stdlib.h
#include stdio.h
#include unistd.h
#include signal.h
#define DBUS_API_SUBJECT_TO_CHANGE
#include dbus/dbus.h
#include dbus/dbus-glib.h
#include dbus/dbus-glib-lowlevel.h
#include bt-dbus.h
static GMainLoop * g_event_loop;
static DBusConnection * sys_conn;
static DBusPendingCall * pending;
static bool interupted;
static const char * object_path = /com/nokia/bt-gps;
static const char * service = com.nokia.bt-gps;
static char * bt_address;
static char * bt_rfcomm;
static char * bt_pin;
void bt_connected () {
printf (bt_connected\n);
}
void bt_disconnected () {
printf (bt_disconnected\n);
}
void rf_connected () {
printf (rf_connected\n);
}
void rf_disconnected () {
printf (rf_disconnected\n);
g_main_loop_quit (g_event_loop);
}
static DBusHandlerResult filter_func (DBusConnection * connection,
DBusMessage *message, void * user_data) {
const char *sender = dbus_message_get_sender (message);
int message_type = dbus_message_get_type (message);
bool handled = false;
if (message_type == DBUS_MESSAGE_TYPE_SIGNAL
!strcmp (dbus_message_get_interface (message),
BTCOND_SIG_INTERFACE)) {
do {
DBusMessageIter iter;
dbus_message_iter_init (message, iter);
int type = dbus_message_iter_get_arg_type (iter);
const char * method = dbus_message_get_member (message);
handled = true;
if (!strcmp (method, BTCOND_CONNECTION_STATUS_SIG)) {
printf (sig connection status\n);
if (type != DBUS_TYPE_STRING)
break;
const char * bt = dbus_message_iter_get_string (iter);
if (!dbus_message_iter_next (iter))
break;
type = dbus_message_iter_get_arg_type (iter);
if (type != DBUS_TYPE_STRING)
break;
const char * state = dbus_message_iter_get_string (iter);
if (!strcmp (state, disconnected))
bt_disconnected ();
else if (!strcmp (state, connected))
bt_connected ();
else
Re: [maemo-developers] Re: Building deb packages for the Nokia 770 is very easy
Stephen DeGabrielle [EMAIL PROTECTED] writes: I'd really like to just use 'dpkg-buildpackage -rfakeroot -b' but it spits errors at me; My problem seems to be that I use ./configure;make;make install to compile. Me too, and I haven't had a problem with this. the Maemo Tutorial seems to want me to 'Run autogen.sh to generate application build configures: ' I think that's assuming that you're starting from the developers' CVS repository for a product. I recommend starting from the most recently released tarball for the product in question, and then following the Debian new maintainer guide. At least that worked for me. In outline, in other words: - Get and unpack a pristine released tarball. - Go into the root dir of the unpacked tarball. - Do the dh_make step as described in the new maintainer guide. - Edit the debian/* files generally as described by the new maintainer guide, but removing lots of stuff that the 770 doesn't need or can't handle: pre and post scripts, manpage, etc.; also change debian/control so that the only dependency is maemo. - In debian/rules, make two key changes. - Change the configure line so that it has --prefix=/var/lib/install/usr. This means that the package will find its files in the right place once it has been installed. - Add two lines like this after the $(MAKE) install line: mv $(CURDIR)/debian/PACKAGE/var/lib/install/* $(CURDIR)/debian/PACKAGE/ rm -rf $(CURDIR)/debian/PACKAGE/var (replacing PACKAGE by your package name). This means that the files in the .deb appear to be rooted at /usr, which is what the 770's application installer needs. - dpkg-buildpackage -rfakeroot Good luck! Neil ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Core-iSCSI/Nokia 770
Greetings all, Things have been moving along well getting iSCSI running and usable on the Nokia 770. Around 95% of the functionality of core-iscsi and core-iscsi-tools is up and stable on the 32-bit ARM-OMAP device. MPEG1 and MPEG4 movies play smoothly on iSCSI mounted LUs over the 802.11gb, the persistent mounting scripts are working, as well as the iSNS package is up. The next steps involve getting everything packaged up and investigating a UI for controlling iSCSI initiators on small devices such as the Nokia 770. I am very interested in hearing from voluenteers from the Maemo community who would be interested in developing a UI that makes script calls in order to control the core-iscsi (and eventually open-iscsi) stacks. I am still working on some of the various bits, and am aiming to have downloadable .debs ready by the end of this weekend for those interested parties. In the mean time I have put some screenshots online: http://www.linux-iscsi.org/index.php/Core-iSCSI/Nokia_770 Enjoy! -- Nicholas A. Bellinger [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] SDK upgrade failed
I had similar problem but then i noticed that I am supposed to be using 0.9.8.6 and that solved it. Devesh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ext Nils Faerber Sent: 28 March, 2006 18:02 To: maemo-developers@maemo.org Subject: [maemo-developers] SDK upgrade failed Hi! I just upgraded my SDK setup to scratchbox 0.9.8.5 and SDK rootstrap to 1.1. After that I cannot start the GUI environment anymore: [sbox-i386: ~/bin] af-sb-init.sh start Note: For remote X connections DISPLAY should contain hostname! Sample files present. Starting Maemo Launcher: maemo-launcher. Starting DBUS system bus Starting D-BUS session bus daemon Error loading /usr/bin/dbus-daemon-1 Error loading /usr/bin/dbus-daemon-1 Starting Sapwood image server Error loading /usr/lib/sapwood/sapwood-server Starting Matchbox window manager Error loading /usr/bin/matchbox-window-manager Starting Keyboard Error loading /usr/bin/hildon-input-method Starting MAEMO AF Desktop [sbox-i386: ~/bin] Error loading /usr/bin/maemo_af_desktop Any idea what is wrong now? Cheers nils faerber -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen Mob: +49-176-21024535 -- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] SDK upgrade failed
Hello, You have/had some different problems. Maemo 1.1 works with scratchbox 0.9.8.5 and the newer version was never required. Nils: which version did you have before you did the upgrade? 1.0 or 1.1 RC5? Cheers, ferenc ext [EMAIL PROTECTED] wrote: I had similar problem but then i noticed that I am supposed to be using 0.9.8.6 and that solved it. Devesh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ext Nils Faerber Sent: 28 March, 2006 18:02 To: maemo-developers@maemo.org Subject: [maemo-developers] SDK upgrade failed Hi! I just upgraded my SDK setup to scratchbox 0.9.8.5 and SDK rootstrap to 1.1. After that I cannot start the GUI environment anymore: [sbox-i386: ~/bin] af-sb-init.sh start Note: For remote X connections DISPLAY should contain hostname! Sample files present. Starting Maemo Launcher: maemo-launcher. Starting DBUS system bus Starting D-BUS session bus daemon Error loading /usr/bin/dbus-daemon-1 Error loading /usr/bin/dbus-daemon-1 Starting Sapwood image server Error loading /usr/lib/sapwood/sapwood-server Starting Matchbox window manager Error loading /usr/bin/matchbox-window-manager Starting Keyboard Error loading /usr/bin/hildon-input-method Starting MAEMO AF Desktop [sbox-i386: ~/bin] Error loading /usr/bin/maemo_af_desktop Any idea what is wrong now? Cheers nils faerber -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen Mob: +49-176-21024535 -- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] SDK upgrade failed
True, Sorry for confusion :)true, I had even older SB ;) 0.9.8.4 and then i upgraded to 0.9.8.5 and my troubles were with dist upgrade, not getting to start the env My mistake ! Devesh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ext Ferenc Szekely Sent: 29 March, 2006 09:36 Cc: maemo-developers@maemo.org Subject: Re: [maemo-developers] SDK upgrade failed Hello, You have/had some different problems. Maemo 1.1 works with scratchbox 0.9.8.5 and the newer version was never required. Nils: which version did you have before you did the upgrade? 1.0 or 1.1 RC5? Cheers, ferenc ext [EMAIL PROTECTED] wrote: I had similar problem but then i noticed that I am supposed to be using 0.9.8.6 and that solved it. Devesh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ext Nils Faerber Sent: 28 March, 2006 18:02 To: maemo-developers@maemo.org Subject: [maemo-developers] SDK upgrade failed Hi! I just upgraded my SDK setup to scratchbox 0.9.8.5 and SDK rootstrap to 1.1. After that I cannot start the GUI environment anymore: [sbox-i386: ~/bin] af-sb-init.sh start Note: For remote X connections DISPLAY should contain hostname! Sample files present. Starting Maemo Launcher: maemo-launcher. Starting DBUS system bus Starting D-BUS session bus daemon Error loading /usr/bin/dbus-daemon-1 Error loading /usr/bin/dbus-daemon-1 Starting Sapwood image server Error loading /usr/lib/sapwood/sapwood-server Starting Matchbox window manager Error loading /usr/bin/matchbox-window-manager Starting Keyboard Error loading /usr/bin/hildon-input-method Starting MAEMO AF Desktop [sbox-i386: ~/bin] Error loading /usr/bin/maemo_af_desktop Any idea what is wrong now? Cheers nils faerber -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen Mob: +49-176-21024535 -- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- -- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] SDK upgrade failed
Hi, please check your DISPLAY variable. The error message indicates that this could be the problem. I, for example, use 127.0.0.1:2 . I have a vague recollection that using IP address instead of localhost is requred for Xephyr et. al. to work properly. But according to the log the d-bus daemon can not be started either so the display variable can not really have effect here. And also the whining is about loading the binaries. I don't know, but my wild quess would be that you have accidently asked scratchbox to use qemu arm emulation for an x86 target? And when you ask qemu to run an x86 binary on arm emulator.. Well you know. Inside scratchbox please check the contents of /targest/[target-name].config In your case the target name seems to be i386. Around line 9 you should see something like: SBOX_CPUTRANSPARENCY_METHOD=false This means that the binaries are run natively on your host CPU. But if this line states that SBOX_CPUTRANSPARENCY_METHOD should be qemu-arm, you are in trouble :-) I'm not sure, but the error log about failing to load binary could sound like this kind of issue. This is not an user-error, but usability problem in the target configuration of the ancient scratchbox you are using. :-) Br, Sampo -Original Message- From: [EMAIL PROTECTED] on behalf of Nils Faerber Sent: Tue 3/28/2006 6:02 PM To: maemo-developers@maemo.org Subject: [maemo-developers] SDK upgrade failed Hi! I just upgraded my SDK setup to scratchbox 0.9.8.5 and SDK rootstrap to 1.1. After that I cannot start the GUI environment anymore: [sbox-i386: ~/bin] af-sb-init.sh start Note: For remote X connections DISPLAY should contain hostname! Sample files present. Starting Maemo Launcher: maemo-launcher. Starting DBUS system bus Starting D-BUS session bus daemon Error loading /usr/bin/dbus-daemon-1 Error loading /usr/bin/dbus-daemon-1 Starting Sapwood image server Error loading /usr/lib/sapwood/sapwood-server Starting Matchbox window manager Error loading /usr/bin/matchbox-window-manager Starting Keyboard Error loading /usr/bin/hildon-input-method Starting MAEMO AF Desktop [sbox-i386: ~/bin] Error loading /usr/bin/maemo_af_desktop Any idea what is wrong now? Cheers nils faerber -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen Mob: +49-176-21024535 -- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] SDK upgrade failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] schrieb: Hi, Hi1 please check your DISPLAY variable. The error message indicates that this could be the problem. I, for example, use 127.0.0.1:2 . I have a vague recollection that using IP address instead of localhost is requred for Xephyr et. al. to work properly. But according to the log the d-bus daemon can not be started either so the display variable can not really have effect here. And also the whining is about loading the binaries. I don't know, but my wild quess would be that you have accidently asked scratchbox to use qemu arm emulation for an x86 target? And when you ask qemu to run an x86 binary on arm emulator.. Well you know. Inside scratchbox please check the contents of /targest/[target-name].config In your case the target name seems to be i386. Around line 9 you should see something like: SBOX_CPUTRANSPARENCY_METHOD=false Good catch! That was it, now it works. Thanks a lot! Cheers nils faerber - -- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen Mob: +49-176-21024535 - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEKj4cJXeIURG1qHgRAqjSAJ9/9ytps81TxutbXI3caXyspocywwCg2SHR R3L+/vsPIYXozDVRcVjf9c0= =MGR0 -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
