Re: [maemo-developers] New version of VNC viewer available plus source code
Thanks a lot for the response,
I fixed the problem with vino. It seems to be a bug in
VCNViewer,
both other encodings are buggy:
void vnc_viewer_configure(VncViewer *vnc, gint fd, gboolean
shared,
VncViewerDepthType depth)
{
guint32 encodings[] =
{
//rfbEncodingHextile,
// rfbEncodingCoRRE,
// rfbEncodingRRE,
rfbEncodingCopyRect, rfbEncodingRaw
};
please disable rfbEncodingCoRRE rfbEncodingRRE and in
vnc-viewer.c .
I can connect to vino now. The performance is not too good, but
I can not compare...
Detlef Schmicker
Am Montag, den 23.01.2006, 10:39 -0800 schrieb Aaron Levinson:
> The original author of gnome-vnc-viewer wrote the Hextile code (back in
> 1999)--I haven't really looked at it yet or tested it yet, and I assume
> that he disabled it because it wasn't ready when he published the 0.1
> release of gnome-vnc-viewer. The next version of the maemo port will
> likely support the Hextile encoding type.
>
> The GNOME VNC server (vino) apparently has a bug that causes it to report
> an encoding type that is not advertised or supported by the VNC viewer
> client. If there is a way to manually force vino to use a different
> encoding type, then you might be able to fix it this way. Users have had
> success with tightvncserver and vncserver.
>
> Aaron
>
> On Mon, 23 Jan 2006, Detlef Schmicker wrote:
>
> > I looked at the source code an found, that you started to integrate
> > Hextile encoding.
> >
> > It is still buggy and you uncommented it. In case you have patches, I
> > will try it.
> >
> > With the current version I can not connect to the gnome vnc server.
> >
> > Detlef
> >
> > --
> > Detlef Schmicker <[EMAIL PROTECTED]>
> >
> > ___
> > 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
>
--
Detlef Schmicker <[EMAIL PROTECTED]>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] VirtualKeyboard service/API
hi Aaron,I didn't mention this in my last e-mail, but you'll also need to setup a
signal handler for the GtkIMContext object's "commit" signal. I have it (the 'commit' signal) already connected and also its callback defined as it is in your post at
http://maemo.org/pipermail/maemo-developers/2006-January/002337.html - cool !!! ... But problem begins after creating the IM_Context object and associating it with the GdkWindow of my GtkMozEmbed object : the mozilla_engine stop recognizing any input from the vkb, except if I press 'backspace' ...
bwt, in 'commit_cb' method, it prints what I type at the console but doesn't add nothing at the HTML form (detail: it does with no context associated or if I type from the physical keyboard) ...
static gboolean
gtk_moz_embed_im_context_commit_cb (GtkIMContext *ctx, const gchar *str, GtkMozEmbed *aEmbed) {
gunichar uChar = 0;
guint keyval = 0;
gchar *text2 = (gchar *) str;
printf ("\n [GTK_MOZ_EMBED] it gets here '%s'
\n", str);
// the string is in UTF-8 format--iterate through the characters
while (*text2) {
uChar = g_utf8_get_char(text2);
keyval = gdk_unicode_to_keyval(uChar);
//
// do something with the character here
//
text2 = g_utf8_next_char(text2);
}
}ps: again, I'm able to pop up / hide the vkb, but not to typing into it ...many thanks for you attention
AaronOn Sat, 21 Jan 2006, Antonio Gomes wrote:> Aaron,>> I got the kb syncrhnized with the focus (in/out) events of HTML forms (the
> focus in -> vk pops up and vice-versa) - many thanks, btw.>> But no text can be entered from typing frm the vk ... And before getting the> "synchronism" working (partially), I was able to do so. Could it be a
> 'context' problems ?>> Thoughts ?>> thanks>> On 1/20/06, Aaron Levinson <
[EMAIL PROTECTED]> wrote:> >> > I have to admit that I don't understand why you would need to use this
> > specialized function in your case. The situation with osso-xterm is a> > specialized one, since the GtkIMContext object's window needs to be> > activated as the result of a menu action. In your case, however, you
> > already have a GtkWidget (GtkMozEmbed), so you should be able to do the> > following:> >> > 1. Create a GtkIMMultiContext in the "constructor" for your object.> > 2. In the realize function for your class (or as a response to the
> > "realize" signal), call gtk_im_context_set_client_window(). Also call it> > for unrealize.> > 3. Handle the "focus-in" and "focus-out" signals appropriately for the
> > widget by calling gtk_im_context_focus_in() and> > gtk_im_context_focus_out(), respectively.> > 4. Set up key-press and key-release signal handlers for the widget and> > call gtk_im_context_filter_keypress() in each signal handler.
> >> > Take a look at the source code for vncviewer or osso-xterm for examples.> > You can also examine the code for various GTK classes, such as> > GtkTextEntry. Also, you can refer back to some previous e-mails that I
> > wrote to this list regarding input methods.> >> > Aaron> >> > On Fri, 20 Jan 2006, Aaron Levinson wrote:> >> > > You can use gtk_im_context_show() to force the window for a GtkIMContext
> > > object to be displayed. This function isn't mentioned in the> > > documentation for the class, but it is in the include file. An example> > of> > > using this function can be found in the osso-xterm code.
> > >> > > Aaron> > >> > > On Fri, 20 Jan 2006, Antonio Gomes wrote:> > >> > > > otherwise, there is no way to force it Pop UP manually ?
> > > >> > > > regards> > > >> > > >> > > > On 1/20/06, Antonio Gomes <
[EMAIL PROTECTED]> wrote:
> > > > >> > > > >> > > > > On 1/18/06, Aaron Levinson <
[EMAIL PROTECTED]> wrote:> > > > >
> > > > > Hi Aaron,> > > > >> > > > > One possibility is to use gdk_window_foreign_new() to wrap the> > native> > > > > > window in a GdkWindow object.
> > > > >> > > > >> > > > > Maybe I can jump this first step, once I already have a GtkWidget> > the> > > > > wraps mozilla guts the make easier called GtkMozEmbed, provided by
> > the> > > > > mozilla embedding API. Make sense for you ?> > > > >> > > > >> > > > > > Then, after creating a GtkIMMulticontext,
> > > > > > you could try using gtk_im_context_set_client_window() with the> > new> > > > > > GdkWindow object. You'll want to listen for key-press and> > key-release
> > > > > > signals (hard to do without a GtkWidget, but you should be able to> > > > > > handle> > > > > > this by listening for these signals on the HildonApp widget), and
> > when> > > > > > you> > > > > > get these signals you can route them to the GtkIMContext that you> > > > > > created> > > > > > earlier if appropriate. Also, look for other e-mails regarding
> > input> > > > > > methods in the archives for this e-mail list. Maybe this will> > work,> > > > > > although I'm not too hopeful. You might also consider creating a
> > > > > > special> > > > > > GtkWidget class that can wrap an arbitrary GdkWindow. I would> > have> > > > > > suggested the GtkPlu
Re: [maemo-developers] VirtualKeyboard service/API
Hi Antonio, I didn't mention this in my last e-mail, but you'll also need to setup a signal handler for the GtkIMContext object's "commit" signal. You may also want to setup a signal handler for the "preedit-changed" signal, although this signal is not used by the virtual keyboard input method. I'm pretty sure that the handwriting input method uses this signal, and the xim input method (used with BT keyboards) may use it as well. I discussed the "commit" signal in an earlier e-mail to this list. Aaron On Sat, 21 Jan 2006, Antonio Gomes wrote: > Aaron, > > I got the kb syncrhnized with the focus (in/out) events of HTML forms (the > focus in -> vk pops up and vice-versa) - many thanks, btw. > > But no text can be entered from typing frm the vk ... And before getting the > "synchronism" working (partially), I was able to do so. Could it be a > 'context' problems ? > > Thoughts ? > > thanks > > On 1/20/06, Aaron Levinson <[EMAIL PROTECTED]> wrote: > > > > I have to admit that I don't understand why you would need to use this > > specialized function in your case. The situation with osso-xterm is a > > specialized one, since the GtkIMContext object's window needs to be > > activated as the result of a menu action. In your case, however, you > > already have a GtkWidget (GtkMozEmbed), so you should be able to do the > > following: > > > > 1. Create a GtkIMMultiContext in the "constructor" for your object. > > 2. In the realize function for your class (or as a response to the > > "realize" signal), call gtk_im_context_set_client_window(). Also call it > > for unrealize. > > 3. Handle the "focus-in" and "focus-out" signals appropriately for the > > widget by calling gtk_im_context_focus_in() and > > gtk_im_context_focus_out(), respectively. > > 4. Set up key-press and key-release signal handlers for the widget and > > call gtk_im_context_filter_keypress() in each signal handler. > > > > Take a look at the source code for vncviewer or osso-xterm for examples. > > You can also examine the code for various GTK classes, such as > > GtkTextEntry. Also, you can refer back to some previous e-mails that I > > wrote to this list regarding input methods. > > > > Aaron > > > > On Fri, 20 Jan 2006, Aaron Levinson wrote: > > > > > You can use gtk_im_context_show() to force the window for a GtkIMContext > > > object to be displayed. This function isn't mentioned in the > > > documentation for the class, but it is in the include file. An example > > of > > > using this function can be found in the osso-xterm code. > > > > > > Aaron > > > > > > On Fri, 20 Jan 2006, Antonio Gomes wrote: > > > > > > > otherwise, there is no way to force it Pop UP manually ? > > > > > > > > regards > > > > > > > > > > > > On 1/20/06, Antonio Gomes <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > On 1/18/06, Aaron Levinson <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi Aaron, > > > > > > > > > > One possibility is to use gdk_window_foreign_new() to wrap the > > native > > > > > > window in a GdkWindow object. > > > > > > > > > > > > > > > Maybe I can jump this first step, once I already have a GtkWidget > > the > > > > > wraps mozilla guts the make easier called GtkMozEmbed, provided by > > the > > > > > mozilla embedding API. Make sense for you ? > > > > > > > > > > > > > > > > Then, after creating a GtkIMMulticontext, > > > > > > you could try using gtk_im_context_set_client_window() with the > > new > > > > > > GdkWindow object. You'll want to listen for key-press and > > key-release > > > > > > signals (hard to do without a GtkWidget, but you should be able to > > > > > > handle > > > > > > this by listening for these signals on the HildonApp widget), and > > when > > > > > > you > > > > > > get these signals you can route them to the GtkIMContext that you > > > > > > created > > > > > > earlier if appropriate. Also, look for other e-mails regarding > > input > > > > > > methods in the archives for this e-mail list. Maybe this will > > work, > > > > > > although I'm not too hopeful. You might also consider creating a > > > > > > special > > > > > > GtkWidget class that can wrap an arbitrary GdkWindow. I would > > have > > > > > > suggested the GtkPlug class, but GtkPlug widgets are top-level > > widgets, > > > > > > which won't work here. > > > > > > > > > > > > > > > > > > > > Please note that the virtual keyboard is provided in the form of a > > GTK > > > > > > input method, and you'll basically need to use the standard GTK > > > > > > mechanisms > > > > > > for working with input methods if you want to use it. > > > > > > > > > > > > > > > but I'm already using Vb successfully and there is no synchronising > > > > > between the rendered HTML forms and the Kb ... (focus in -> pop up > > vk / > > > > > focus out -> vk gets down). > > > > > > > > > > many thanks > > > > > > > > > > > > > > > > > Hi there, > > > > > > > > > > > > > > I'm wondering how I can get the Virtual Keyboard service to > > > > > >
Re: [maemo-developers] New version of VNC viewer available plus source code
The original author of gnome-vnc-viewer wrote the Hextile code (back in 1999)--I haven't really looked at it yet or tested it yet, and I assume that he disabled it because it wasn't ready when he published the 0.1 release of gnome-vnc-viewer. The next version of the maemo port will likely support the Hextile encoding type. The GNOME VNC server (vino) apparently has a bug that causes it to report an encoding type that is not advertised or supported by the VNC viewer client. If there is a way to manually force vino to use a different encoding type, then you might be able to fix it this way. Users have had success with tightvncserver and vncserver. Aaron On Mon, 23 Jan 2006, Detlef Schmicker wrote: > I looked at the source code an found, that you started to integrate > Hextile encoding. > > It is still buggy and you uncommented it. In case you have patches, I > will try it. > > With the current version I can not connect to the gnome vnc server. > > Detlef > > -- > Detlef Schmicker <[EMAIL PROTECTED]> > > ___ > 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] Evince 0.5.0 Released
2006/1/22, Larry Battraw <[EMAIL PROTECTED]>: > Another huge thank you for the work you've done in porting this app! This > is one of those must-have applications (IMHO), I definetly agree with you! PDF reading is one of the reasons I own a 770. >since I tend to carry manuals > in PDF format for reference. With 24M of swap I can breeze through them > without any problems. My only suggestion would be assigning the D-pad > center button to be next page; as it is you end up scrolling a lot to get > from page to page. I use 16M of swap, and out of memory occours sometime; i will try to increase swap space. In addition to last page button, I would love also to use the same panning function found in the default pdf viewer; combined with continuous scrolling it would be more confortable than scrollbars. Roberto. > > Larry > > > On 1/20/06, Eduardo de Barros Lima <[EMAIL PROTECTED]> wrote: > > Hi all, > > > >A new stable version of Evince was released yesterday and I have > > built the package for nokia 770. It still depends on libgnomeprintui. > > Aditional information can be found at my blog: > > > > > http://etrunko.blogspot.com/2006/01/evince-050-is-out.html > > > >Hope you enjoy it. Best regards, Eduardo (etrunko). > > > > -- > > Eduardo de Barros Lima > > INdT - Instituto Nokia de Tecnologia > > [EMAIL PROTECTED] > > > ___ > 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: email source code available
Hi, the SDK doesn't contain osso-icons, osso-default-theme. Use sdk-default-theme, sdk-default-theme-config, and sdk-default-icons instead. Please note that osso-memory-backend binary and source debian packages are now available in maemo1.1 repository. Just do an 'apt-get update; fakeroot apt-get install osso-memory-backend' and you should be OK after that. The rest of the runtime dependencies you're mentioning below are unfortunately not available. Regards, - Pete - -Original Message- From: [EMAIL PROTECTED] on behalf of Antti P Miettinen Sent: Mon 1/23/2006 4:55 PM To: maemo-developers@maemo.org Subject: [maemo-developers] Re: email source code available >> - osso-memory-backend > > This is provided by 'gtkfilesystemmemory' source package. > https://stage.maemo.org/svn/maemo/projects/haf/trunk/gtkfilesystemmemory/ OK - with the osso-memory-backend installed I can compile the osso-email package. So the rest of the dependencies are not critical? What about the runtime dependencies: dpkg: dependency problems prevent configuration of osso-email-ui: osso-email-ui depends on osso-icons-theme; however: Package osso-icons-theme is not installed. and dpkg: dependency problems prevent configuration of osso-email: osso-email depends on osso-email-ui; however: Package osso-email-ui is not configured yet. osso-email depends on hildon-task-navigator-mail (>= 0.8.9-6); however: Package hildon-task-navigator-mail is not installed. osso-email depends on osso-email-search-plugin (>= 0.1.4); however: Package osso-email-search-plugin is not installed. osso-email depends on osso-contacts-search-plugin (>= 0.1.3); however: Package osso-contacts-search-plugin is not installed. So, seems that these are also somehow related: - osso-icons-theme - hildon-task-navigator-mail - osso-email-search-plugin - osso-contacts-search-plugin But not critical? I just removed the dependencies from debian/control and now I can install and launch the email app. Lets see if I can debug it.. :-) -- http://www.iki.fi/~ananaza/ ___ 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] Re: email source code available
>> - osso-memory-backend > > This is provided by 'gtkfilesystemmemory' source package. > https://stage.maemo.org/svn/maemo/projects/haf/trunk/gtkfilesystemmemory/ OK - with the osso-memory-backend installed I can compile the osso-email package. So the rest of the dependencies are not critical? What about the runtime dependencies: dpkg: dependency problems prevent configuration of osso-email-ui: osso-email-ui depends on osso-icons-theme; however: Package osso-icons-theme is not installed. and dpkg: dependency problems prevent configuration of osso-email: osso-email depends on osso-email-ui; however: Package osso-email-ui is not configured yet. osso-email depends on hildon-task-navigator-mail (>= 0.8.9-6); however: Package hildon-task-navigator-mail is not installed. osso-email depends on osso-email-search-plugin (>= 0.1.4); however: Package osso-email-search-plugin is not installed. osso-email depends on osso-contacts-search-plugin (>= 0.1.3); however: Package osso-contacts-search-plugin is not installed. So, seems that these are also somehow related: - osso-icons-theme - hildon-task-navigator-mail - osso-email-search-plugin - osso-contacts-search-plugin But not critical? I just removed the dependencies from debian/control and now I can install and launch the email app. Lets see if I can debug it.. :-) -- http://www.iki.fi/~ananaza/ ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] New version of VNC viewer available plus source code
I looked at the source code an found, that you started to integrate Hextile encoding. It is still buggy and you uncommented it. In case you have patches, I will try it. With the current version I can not connect to the gnome vnc server. Detlef -- Detlef Schmicker <[EMAIL PROTECTED]> ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to lock a User in a Sandbox
Hi, I'm also trying to accomplish the same thing. I want to capture the Home-key from application, ie prevent the system to display the desktop when the user presses the key. First, I tried to remove the keysnooper installed by the Hildon framework: http://maemo.org/lxr/source/hildon-lgpl/hildon-lgpl/hildon-app.c#297 In emulator (i386 SDK and Xephyr) removing that snooper seemed to do the trick, but not in the device. Then I found this in the Hildon Navigator sources: http://maemo.org/lxr/source/maemo-af-desktop/hildon-navigator/application-switcher.c#1669 Is there some way to prevent Navigator receiving those Home key DBus events? Br, Aki Benjamin Zeller wrote: Hello, Hope someone can help me here. Is it possible to write a programm which i can use to lock a User in a Sandbox? The User should only be able to use a few Programms, if someone want to use the full system he has to type a password and quit the "sandbox". Because of this the Programm needs to catch all Messages (the Home Button Message) to prevent unauthorised access to the full system. How can i do this (catch the messages)? sorry for my bad english greets Benjamin ___ 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] Building Maemo from scratch
Hi, Russell Geldmacher wrote: > I was under the impression that when OE sees a package that has > (R)DEPENDS on another package, it will go find the one marked > (R)PROVIDES for that functionality and build it. Is that wrong? more or less, yes - but RDEPENDS/RPROVIDES ends up in the package dependencies only. So if an alternate package doesn't set PROVIDES you will run into build time dependency trouble. Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] How to lock a User in a Sandbox
Hello, Hope someone can help me here. Is it possible to write a programm which i can use to lock a User in a Sandbox? The User should only be able to use a few Programms, if someone want to use the full system he has to type a password and quit the "sandbox". Because of this the Programm needs to catch all Messages (the Home Button Message) to prevent unauthorised access to the full system. How can i do this (catch the messages)? sorry for my bad english greets Benjamin ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] ssh + display
Hi, Gary Godfrey wrote: > osso_initialize() WARNING: if the system bus activated this program, Libosso > does not connect to the session bus! > osso_initialize() failed! > > Is there a way to get this working? you are missing some environment settings. Start it in this way: run-standalone.sh /var/lib/install/usr/bin/osso-xterm Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: email source code available
On Sat, 2006-01-21 at 23:26, ext Antti P Miettinen wrote: > Any progress on publishing the osso-email build dependencies? > According to debian/control the following are still needed: > > - libcst-dev > - libosso-certman-dev > - osso-memory-backend This is provided by 'gtkfilesystemmemory' source package. https://stage.maemo.org/svn/maemo/projects/haf/trunk/gtkfilesystemmemory/ I don't know about the others. BR, Kimmo > > Or am I just unable to find these? ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] ssh + display
On Mon, 2006-01-23 at 12:13, ext Kuisma Salonen wrote: > Lassi Syrjälä wrote: > > Hi, > > > > I think you need to: > > > > $ . /etc/osso-af-init/af-defines.sh > > Just as quick comment, if your application uses X, it needs to have > DISPLAY defined. If it uses D-BUS in any means (like use libosso), it > needs the D-BUS environment variables to be set correctly. If you want > GTK to be themed you need to set up GTK2_RC_FILES and so forth. This > little script will set up every needed envvar. It does not set Gtk variables (only D-BUS stuff). Use the run-standalone.sh script to get all variables defined. BR; Kimmo > > Just wanted to say that if you have simple custom X application all you > need is to have DISPLAY properly set. > > -- Kuisma > ___ > 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 for the iPaq?
Hi Amaury, I am not aware of a project to port maemo on iPAQ yet. This would surely be a challenging project! Porting maemo to iPAQ will bring a few issues, to start with: the screen size (several UI elements have hardcoded pixel values for nokia 770), and the different hardkeys. We would be very happy to help maemo to support various devices! A page to start is http://maemo.org/maemowiki/MaemoScalability For iPAQ hardware support (drivers), you should see also http://www.handhelds.org Br, luc On Thu, 2006-01-19 at 11:33 -0800, ext Amaury Rodriguez wrote: > A friend of mine owns an iPaq with an ARM processor > and he is tired of the silly OS that runs it (Windows > Mobile). Is there any project to port the maemo OS to > other devices besides the Noki 770? If there is any I > would like to get involved in development. > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > ___ > 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] Insmod error
Hi all: I had a question is similar as below: http://lists.scratchbox.org/pipermail/scratchbox-users/2004-October/91.html My host machine which contains scratchbox has a 2.6.XX kernel.Thanks all! What are the most popular cars? Find out at Yahoo! Autos ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] ssh + display
Lassi Syrjälä wrote: Hi, I think you need to: $ . /etc/osso-af-init/af-defines.sh Just as quick comment, if your application uses X, it needs to have DISPLAY defined. If it uses D-BUS in any means (like use libosso), it needs the D-BUS environment variables to be set correctly. If you want GTK to be themed you need to set up GTK2_RC_FILES and so forth. This little script will set up every needed envvar. Just wanted to say that if you have simple custom X application all you need is to have DISPLAY properly set. -- Kuisma ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] dpkg blues
On Tue, 2006-01-10 at 22:58 -0500, Vladislav Grinchenko wrote: > Hi, > > I am trying to build arm debian package of libsigc++ installable > on nokia 770. dpkg-buildpackage builds it just fine: ... > However, in order for me to use AppInstaller, I have to make it > dependable on pseudo-package maemo: --- > However, installing it both on 770 and in scratchbox SDK_ARM fails > bitterly: ... > Can someone explain to me why I get this error? > > failed to chroot to `/var/lib/install' > It's been two weeks, but in case you're still wondering about this: You probably have maintainer scripts (eg. prerm, postinst) in your package. Those are not allowed with app-installer-tool, and may prevent the package from being correctly installed and uninstalled. There is a separate how-to about packaging: http://maemo.org/platform/docs/howtos/howto_making_an_application_package.html HTH, -- Jussi Kukkonen ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Reverse Shell
Hi Just a quick note for now to get your attention! More later if there are to be interested users.. Now there are at least 2 ways to do remote login on Nokia 770: 1) Setup ssh daemon and then take ssh connection from other machine to Nokia 770. I quess this requires setting of keys and user passwords somehow. 2) Have dropbear-client installed on Nokia 770. Then Install revsh_1.91_arm.deb on Nokia 770. Launch "RevSH Tunnel" from extras menu. Make revsh connection from that program to other machine and then on that other machine, issue "revsh [EMAIL PROTECTED] shell" (Ok. second option requires compiling revsh on other machine and copying the binary somewhere on path there (and have ssh up&running there)) If you're interested, check http://www.iki.fi/too/sw/revsh/ for more information... Tomi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Version of tools in Toolchain?
Hi You could talk to Paul Guyot : He has built a version of his Newtown Emulator (Einstein) on a mac ! Fred Dr. H. Nikolaus Schaller wrote: I am currently building a toolchain by using crosstools for running on MacOS X 10.4 / Darwin 8 since Scratchbox does not work on MacOS. For that I need a spec which version of gcc and glibc and Linux headers I should build into my toolchain. By looking in the file system of the N770 I found that it currently comes with glibc-2.3.2. And the Internet says it uses Linux 2.6.11. But nothing on the gcc version. Is that all correct? And should I use arm-unknown or something else? What about softfloat? And, can I use a more recent header or glibc? -- hns ___ 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: email source code available
Hi, As far as I know libcst is under LGPL licence. So, I hope its sources will be published soon. On Sat, 2006-01-21 at 23:26 +0200, ext Antti P Miettinen wrote: > Any progress on publishing the osso-email build dependencies? > According to debian/control the following are still needed: > > - libcst-dev > - libosso-certman-dev > - osso-memory-backend > > Or am I just unable to find these? > -- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
