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
m
>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
_
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
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_o
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
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
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 annoyi
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..
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 a
- 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
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 aut
11 matches
Mail list logo
