RE: [maemo-developers] Maemo in Suse Linux 9.1.
On Fri, 2005-12-30 at 11:07 +0200, [EMAIL PROTECTED] wrote: > SSH X11 forwarding works in SuSE out of the box. That's supposed to be > used instead of pure TCP. > Wrong way of thougt. I suppose an os-upgrade NOT to break my configuration. I don't care if some guy at a distro-packager thinks he must save the world by disabling essential services just because they are "insecure" in his opinion. Thats not only true for X11, but for other things too. regards, marvin. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] Maemo in Suse Linux 9.1.
>Form my point of view it is just annoying (on the desktop). If >the network is SUCH a security risk, why even install drivers >for the lan card ? SSH X11 forwarding works in SuSE out of the box. That's supposed to be used instead of pure TCP. - Jussi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
Hi, > [sbox-SDK_PC: ~] > maemo_af_desktop[8054]: GLIB CRITICAL ** GLib-GObject > - g_object_set: assertion `G_IS_OBJECT (object)' failed > > Does it mean that GLIB in my machine is not working? No, it means that there's a bug in Desktop or in one of its applets code, which Glib noticed. (Desktop applets are the windows you see on the desktop at startup, menus on the vertical panel at left and menus on the top). - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
Hi, It seems that Xephyr is now working. Thanks for the helps. When I executed ./start-xephyr.sh &, a window open. However when I execute af-sb-init.sh start after starting scratchbox I get the following errors: [sbox-SDK_PC: ~] > maemo_af_desktop[8054]: GLIB CRITICAL ** GLib-GObject - g_object_set: assertion `G_IS_OBJECT (object)' failed Does it mean that GLIB in my machine is not working? - Ed. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
Hi, >> No, the correct way is to remove the idiotic host part check from >> the sb-af-init.sh script (AFAIK this is fixed in newer SDK). >> Just change the 'exit' inside the host check in the script to 'echo' >> or comment it out. > > Well, the "correct way" to me is anything that works at all. I > needed aworking tcp-X11 on my workstation anyway, so i was going this > route. If the connection is through tcp-X11 socket, shared memory is not used for transferring images from client to server. This is one more difference to how things work on the target. On principle these kind of differencies should be minimized. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
On Thu, Dec 29, 2005 at 06:20:30PM +0800, Edlinoor Syahril Ramlan wrote: > I am running Xephyr from outside Sbox. Sbox is locate at /scratchbox so I > put start-xephyr.sh outside Sbox that is in the / directory so when I try > to execute the file I'm using ./start-xephyr.sh and with the existing user > in the machine. existing user = the same one with which you logged onto your desktop? > So do I still need to do anything with the .Xauthority file? Are you executing it from your normal desktop shell, or from inside Scratchbox? If latter, you need the .Xauthority file. If former, you should be able to run Xephyr like you can run any other X program (e.g. xterm). - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
On Thu, 2005-12-29 at 14:08 +0200, Eero Tamminen wrote: > On the actual device X server doesn't listen on inet sockets either, > only on local ones. I'm not sure why this is done on the target, > but at least on desktop it's for obvious security reasons... Form my point of view it is just annoying (on the desktop). If the network is SUCH a security risk, why even install drivers for the lan card ? I find it extremely annoying to run after more-or-less undocumented changes in new versions of distributions. This is not only true for suse, but for all of them. (However, suse is the undisputed world champion in this discipline). > No, the correct way is to remove the idiotic host part check from > the sb-af-init.sh script (AFAIK this is fixed in newer SDK). > Just change the 'exit' inside the host check in the script to 'echo' > or comment it out. Well, the "correct way" to me is anything that works at all. I needed a working tcp-X11 on my workstation anyway, so i was going this route. regards, marvin ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
Hi,
> Under 9.2 there is a (strange) default setting for the X11-server to
> deny any access over TCP.
On the actual device X server doesn't listen on inet sockets either,
only on local ones. I'm not sure why this is done on the target,
but at least on desktop it's for obvious security reasons...
> As the DISPLAY variable in scratchbox must
> have a host part ("localhost:0.0", not ":0.0") xephyr cannot connect
> correctly. The solution is to remove the option "-nolisten tcp" in
> the file "/etc/X11/xdm/Xservers" for display 0.
No, the correct way is to remove the idiotic host part check from
the sb-af-init.sh script (AFAIK this is fixed in newer SDK).
Just change the 'exit' inside the host check in the script to 'echo'
or comment it out.
- Eero
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
On Thu, 2005-12-29 at 15:29 +0800, Edlinoor Syahril Ramlan wrote:
> Hi,
>
> Unfortunately it give me this error:
>
> Xephyr cannot open host display. Is DISPLAY set?
>
I had a very simmilar problem under 9.2:
Under 9.2 there is a (strange) default setting for the X11-server to
deny any access over TCP. As the DISPLAY variable in scratchbox must
have a host part ("localhost:0.0", not ":0.0") xephyr cannot connect
correctly. The solution is to remove the option "-nolisten tcp" in the
file "/etc/X11/xdm/Xservers" for display 0.
Then execute "xhost +" outside of scratchbox and xephyr should run
correctly.
Hope this helps,
marvin
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo in Suse Linux 9.1.
- Original Message - From: "Eero Tamminen" <[EMAIL PROTECTED]> To: Sent: Thursday, December 29, 2005 5:22 PM Subject: [maemo-developers] Maemo in Suse Linux 9.1. Hi, I was trying to installed Maemo SDK in Suse Linux 9.1. I followed all the instructions inside the tutorial and all work well until the part where I have to setup Xephyr. I created one file as suggested in the manual and place it inside the / by using root. Which file you're referring to? The file i'm reffering to is start-xephyr.sh. I re-login by using the user that I created during the setup process and try to execute Xephyr by using this command: ./start-xephyr.sh &. I think the instructions assume you give as Sbox-user a user already existing on your machine. (the user running the desktop) Setting up multi-user Sbox setup is slightly more complicated. Yes I am using the same existing user in the machine. Unfortunately it give me this error: Xephyr cannot open host display. If you're running an X program (such as Xephyr) as another user, you need to tell your X server that this other user should be able to connect his X clients to your X server. There are several ways to do this: - "xhost +localhost" as the normal user, or - copying the .Xauthority from your normal home directory to the home directory of the new user (home directory of course depending on whether you're running Xephyr from outside or inside Sbox) (There are some other ways too, but these are easiest) I am running Xephyr from outside Sbox. Sbox is locate at /scratchbox so I put start-xephyr.sh outside Sbox that is in the / directory so when I try to execute the file I'm using ./start-xephyr.sh and with the existing user in the machine. So do I still need to do anything with the .Xauthority file? Is DISPLAY set? I ignored the error and went on to procedd with the next section that is: Maemo programs cannot run if they don't have an X server (in this case Xephyr) on where to show their UIs. FYI: Xephyr is a "virtual" X server for the Maemo applications that has correct screen size and bit-depth. It uses your desktop X server window as it's framebuffer. (Note: Xephyr is a real X server unlike Xnest which is just an X server proxy i.e. limited to the capabilities of the X server which it's proxying. Xephyr can support X extensions that your desktop XFree86 X server propbably doesn't, such as Xdamage, Xcomposite etc.) - Eero ___ 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] Maemo in Suse Linux 9.1.
Hi, Eero Tamminen wrote this on message "Re: [maemo-users] Issues with RC6 and Maemopad / Tutorial?" on Wednesday 23 November 2005 09:24 - If you run Xephyr from inside the Scratchbox, it cannot access the .Xauthority file in your home directory (on the host) so that it could authenticate that you're the same user. There are several different ways to get around this: - Copy the ~/.Xauthority file to your Sbox home directory - Use "xhost +localhost" outside Sbox - Run your desktop X server without any access control using the -ac option (not recommended for obvious reasons :)) - Run Xephyr (which is inside Sbox) from outside the Sbox, this is easiest done with a script like at the bottom The reason why Xephyr can connect your desktop X server from inside the Sbox even with normal unix socket is that Sbox shares the /tmp/ with the host system. There's more information about this on the Sbox site. - Eero - I think it's the most detailed explanation on this issue I have ever read on maemo lists ;) On Thursday 29 December 2005 08:29, Edlinoor Syahril Ramlan wrote: > Hi, > > I was trying to installed Maemo SDK in Suse Linux 9.1. I followed all the > instructions inside the tutorial and all work well until the part where I > have to setup Xephyr. I created one file as suggested in the manual and > place it inside the / by using root. I re-login by using the user that I > created during the setup process and try to execute Xephyr by using this > command: ./start-xephyr.sh &. > > Unfortunately it give me this error: > > Xephyr cannot open host display. Is DISPLAY set? > > I ignored the error and went on to procedd with the next section that is: > > export DISPLAY=:2 > af-sb-init.sh start > > Maemo doesn't start and I get these errors: > > sapwood-server[9864]: GLIB WARNING ** Gdk - cannot open display: (null) > matchbox-vm: can't open display! check your DISPLAY variable. > hildon-input-method[9884]: GLIB WARNING ** Gtk - cannot open display: > maemo_af_desktop[9894]: GLIB WARNING ** Gtk - cannot open display: > > I really do not understand what's going on. Need help please. > > Thanks. > > Ed. -- Eloi Crespillo Itchart ZEN Programari lliure i xarxes SLL [EMAIL PROTECTED] | [EMAIL PROTECTED] www.ikuszen.com | www.grupoikusnet.com ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
