Re: Cannot install Maemo SDK 1.2 in Ubuntu Lucid: dependencies problems
On 05/03/2010 09:40 PM, ext Marcin Juszkiewicz wrote: Dnia poniedziałek, 3 maja 2010 o 08:03:57 tero.k...@nokia.com napisał(a): Try: ~# echo 0 /proc/sys/vm/mmap_min_addr At least that is what people more knowledgeable than me tell to do. It has something to do with the recent kernels and QEMU. Better would be qemu update to 0.12 which does not need that trick anymore. But such sugestion is WONTFIX for fremantle rather. scratchbox qemu has had that fix for ages... The bug is in ubuntu lucid's kernel. As non-root you no longer can read /proc/sys/vm/mmap_min_addr. See: https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/568844 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Mon, May 03, 2010 at 02:14:00PM +0200, Carsten Munk wrote: X-Fade said we should set up a IRC meeting to get this accomplished - he can take care of server side. Cool :-) Got a suggestion for a time during this week? Any evening (UTC) is fine. If it has to be during office hours, Thursday or Friday morning will probably do. I prefer UTC office hours as MeeGo already tends to steal some evenings. L. -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: GSoC 2010, eBook reader. Looking for feedback and ideas.
On Sat, May 1, 2010 at 12:15 AM, Roland Whitehead rol...@quru.com wrote: On 30 Apr 2010, at 09:46, Juhana Jauhiainen wrote: Changing font size is a very useful feature so it should be included. What comes to scrolling, I was planning to use paging instead of a continuous scrollable textview. When using a book reader with scrolling I often loose the spot I was at when I need to scroll, but of course automatic scrolling wouldn't have the same problem. Do most people prefer scrolling or paging? We have been playing around with ePub books quite a lot this week (we have to be publishing around 400 a year from now on) and so I've been trying all sorts of devices. The ones that I like are those that page. Those that scroll are good when there is no choice (like with the EPUBReader Firefox plugin that's available for Firefox on the N900 which is otherwise pretty cool) but I definitely like the paging devices. iBooks would be the best at this so far for reading but its ruined by Apple playing big brother and not letting you download .epub files from anywhere else but (you guessed) the Apple Appstore or via (you also guessed) iTunes. So please also make it really easy to work with URLs or local files and if it could be set up as a browser helper app then you could click on an .epub URL in the microB and have it open in your app. Opening local files would be useful and perhaps the library could be just a folder in MyDocs so it would be easy to copy books to it. A feature I'd like to see is a way for eBooks to open at the last page they were on when last opened. It might work if you only ever open one book but if you open many it would help if it always went to that last page that you were on in that particular book. It could be automatic or it could be manual (UI hint - some people ruin printed books by folding over the top outer corner of the page, I use a post-it note or a business card). This is something I am planning to include. An index of annotations would be good. I have printed books with lots of mini-post-it notes sticking out, each one indicating something of particular interest with one or two words written on it. Some people use those clever colour coded post-it book-marks. They are book specific as opposed to bookmarks for all eBooks. Could annotations be tagged so that you can filter annotations by the tags? Color coding annotations and bookmarks would be very useful and there definitely should be an easy way to browse them. Tags would be nice but I'm not going to promise too much. Are you going to do this in Qt and C, C++ or PyQt? I'm going to do this with C++ and Qt. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Howto grab all Maemo5 zoom key events in SDL/SDL_gles app?
Frantisek Dufka wrote: I am not sure why there are three X windows in info.info.x11 structure (fswindow, wmwindow and window). From brief look into SDL sources it seems to me like the 'window' is used when SDL is initialized with not owned pre-created window passed to SDL via SDL_WINDOWID variable, otherwise wmwindow and fswindow are used depending of full screen state. In case you are not using SDL_WINDOWID maybe setting wmwindow and fswindow would help you with volume keys? WMwindow and FSwindow are containers for window (aka gfxwindow) which is the one where images are pushed into. On the Fremantle SDL, WMwindow and FSwindow are alternatively mapped when changing from windowed to fullscreen mode and viceversa -- on a normal SDL, WMwindow is always mapped. Also, gfxdisplay - window (gfxwindow) display - wmwindow,fswindow Else you will get permission errors when you start trying to do more complicated things. -- Javier ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Howto grab all Maemo5 zoom key events in SDL/SDL_gles app?
On Tue, 2010-05-04 at 16:01 +0200, ext Javier S. Pedro wrote: Frantisek Dufka wrote: I am not sure why there are three X windows in info.info.x11 structure (fswindow, wmwindow and window). From brief look into SDL sources it seems to me like the 'window' is used when SDL is initialized with not owned pre-created window passed to SDL via SDL_WINDOWID variable, otherwise wmwindow and fswindow are used depending of full screen state. In case you are not using SDL_WINDOWID maybe setting wmwindow and fswindow would help you with volume keys? WMwindow and FSwindow are containers for window (aka gfxwindow) which is the one where images are pushed into. On the Fremantle SDL, WMwindow and FSwindow are alternatively mapped when changing from windowed to fullscreen mode and viceversa -- on a normal SDL, WMwindow is always mapped. Sounds a bit brain-damaged to have two windows when others do fine with one... But if it must be so, you need to put the ZOOM_KEY property to both windows because the topmost counts. -Kimmo Also, gfxdisplay - window (gfxwindow) display - wmwindow,fswindow Else you will get permission errors when you start trying to do more complicated things. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
Thanks to Niels who spent this afternoon working on this, we now have maemo.org signed repositories! Without further ado, they are: deb http://repository.maemo.org/community/ diablo free non-free deb http://repository.maemo.org/community-testing/ diablo free non-free The community/ one is supposed to be the stable one and is currently empty, while community-testing now holds the contents of my private testing repository. To anyone interested in testing: 1. Understand that these packages are unofficial software updates provided by the maemo.org community with no warranty expressed or implied and are not supported by Nokia. Is is highly recommended that you have a recent backup before proceeding. 2. Make sure you have not (perhaps unintentionally) removed the appropriate osso-software-version-rxXX package for your device, of if you have re-install it as SSU simply won't work without it. 3. Visit http://repository.maemo.org/community-testing/community-testing.install with the built-in browser (microb) and open it with the application manager when prompted. This will install the community-testing repository and an enabler package that loads its public key and sets up the package domain with a higher priority than the nokia-system one so that nokia-system packages can be updated. 4. Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update. 5. Install the update. 6. Report any issues to http://talk.maemo.org/showthread.php?t=30648 (for now, I'll be bugging Andre for a bugs.maemo.org product soon). To anyone interested in contributing: look at http://wiki.maemo.org/Talk:Diablo_Community_Project for the backlog and see if anything grabs your interest. N810W (RX48) owners are particularly welcome, as are people who are willing to review source packages :-) L. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Community updates for diablo
I don't know if I missed some previous post but I have some questions: 1. Was diablo officially discontinued by nokia? 2. Where can we find what has changed/benefits of upgrading? 3. Does this in any way or shape relate to having qt 4.6 on Diablo? Does it make any easier/harder? Felipe -Original Message- From: maemo-developers-boun...@maemo.org [mailto:maemo-developers-boun...@maemo.org] On Behalf Of Lucas Maneos Sent: Tuesday, May 04, 2010 12:04 PM To: maemo-developers@maemo.org Subject: Re: Community updates for diablo Thanks to Niels who spent this afternoon working on this, we now have maemo.org signed repositories! Without further ado, they are: deb http://repository.maemo.org/community/ diablo free non-free deb http://repository.maemo.org/community-testing/ diablo free non-free The community/ one is supposed to be the stable one and is currently empty, while community-testing now holds the contents of my private testing repository. To anyone interested in testing: 1. Understand that these packages are unofficial software updates provided by the maemo.org community with no warranty expressed or implied and are not supported by Nokia. Is is highly recommended that you have a recent backup before proceeding. 2. Make sure you have not (perhaps unintentionally) removed the appropriate osso-software-version-rxXX package for your device, of if you have re-install it as SSU simply won't work without it. 3. Visit http://repository.maemo.org/community-testing/community-testing.install with the built-in browser (microb) and open it with the application manager when prompted. This will install the community-testing repository and an enabler package that loads its public key and sets up the package domain with a higher priority than the nokia-system one so that nokia-system packages can be updated. 4. Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update. 5. Install the update. 6. Report any issues to http://talk.maemo.org/showthread.php?t=30648 (for now, I'll be bugging Andre for a bugs.maemo.org product soon). To anyone interested in contributing: look at http://wiki.maemo.org/Talk:Diablo_Community_Project for the backlog and see if anything grabs your interest. N810W (RX48) owners are particularly welcome, as are people who are willing to review source packages :-) L. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Community updates for diablo
Am Dienstag, den 04.05.2010, 12:16 -0400 schrieb Felipe Crochik: 1. Was diablo officially discontinued by nokia? I don't know of any official statement, however reality shows that it's defacto discontinued (or did you see any Diablo updates in the last 16 months after 5.2008.43-7?). andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Tue, May 04, 2010 at 12:16:20PM -0400, Felipe Crochik wrote: I don't know if I missed some previous post but I have some questions: Most of the discussion has happened in http://talk.maemo.org/showthread.php?t=30648. 1. Was diablo officially discontinued by nokia? Not explicitly as far as I know, but at this stage I think it's safe to assume there will be no more updates unless something extraordinary happens. 2. Where can we find what has changed/benefits of upgrading? Here's the collected changelog of what's currently in the repository (it's also visible in the application manager before upgrading): busybox: * Fixes: BMO#3917: Missing Large File Support (CONFIG_LFS) in Busybox. * Fixes: BMO#3951: Incompatible quote handling in Busybox xargs (FEATURE_XARGS_SUPPORT_QUOTES disabled?) * Enable FEATURE_XARGS_SUPPORT_ZERO_TERM for consistency with FEATURE_FIND_PRINT0 (mentioned in BMO#3951/BMO#4248). * Fixes: BMO#3957: Busybox does not support ls -Q which some scripts need. * Fixes: BMO#3968: grep -r can output corrupt data in error message if file cannot be read. * Fixes: BMO#4174: shell history file is overwritten after every command. * Fixes: BMO#4175: History cross-contamination between concurrently running shells * Fixes: BMO#7014: ash saves only 15 lines of history (increased to 100). * Workaround for BMO#5317: Shell does not save command history / Busybox doesn't handle SIGHUP properly. * Fix for multi-column ls -Q output. * Fixes: BMO#419: Enable IPv6 support in busybox (and PING6). * Fixes: BMO#3989: Busybox ls -s dereferences the file. * Fixes: BMO#4248: Enable features in Busybox to increase its tools GNU/Debian compatibility. * Fixes: BMO#4079: busybox df does not handle root filesystem on command line. * Fixes: BMO#6606: No getopts, called by init-functions (lsb-base). * Fixes: BMO#8291: Enable CONFIG_LOCALE_SUPPORT in busybox. * Build with -mthumb to match the official Nokia package. * Make df rootfs mangling conditional on filesystem arguments. dnsmasq: * Fixes: BMO#995: DNS resolution ignores local domain. * Removed unused resolvconf script. kernel-diablo: * Fixes: BMO#2249: FM Radio frequency not set for use in Japan. Martin Grimme martin.grimme at lintegra.de * Fixes: BMO#2491: cant run camera applications with v4l2. Sakari Ailus sakari.ailus at nokia.com * Fixes: BMO#3123: Patch to kernel to allow DSP framebuffer sharing on N8x0 devices. Simon Pickering S.G.Pickering at bath.ac.uk * Fixes: BMO#3519: Integrate screen rotation patches into stock kernel. Luarvique L. Luarvique luarvique at gmail.com * Changed debian/rules to do a parallel make because Diablo's dpkg-buildpackage is too old to support -j and I'm lazy. loudmouth: * Fixes: BMO#3455: telepathy-gabble deadlooping * Fixes: BMO#4119: digest-uri omits the serv-name part causing authentication failure when host != serv-name Sjoerd Simons sjoerd at debian.org modest: * Fixes: BMO#2553: Please make folder view finger-sized. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#2554: Add Move to folder button in main view. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#3004: Modest pops up even when only read messages are in IMAP inbox. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#3498: Add Zooming to x% messages to Modest. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#3941: Signature separator misses trailing space (RFC 3676 violation). tinymail: * Fixes: BMO#4803: Modest sends empty ENABLE command when IMAP server advertises ENABLE but not CONDSTORE or QRESYNC capabilities. osso-pdf-viewer: * Fixes: BMO#2150/NB#76448/NB#120388: PDF Reader doesn't support internal document hyperlinks. xujun Jun.Xu at plenware.com * Fixes: BMO#2704: PDF Reader needs more zoom levels between 50% and 150% Sandu Gherbe pursisimplu2004 at yahoo.com * Fixes: BMO#2714: Page up should go to Bottom of Previous Page (instead of Top). yanghua Hua.Yang at plenware.com * Fixes: BMO#4930: PDF Reader doesn't use optimal screen width in fit width mode. Hauweele Pierre antegallya at gmail.com xserver-xomap: * Fixes: BMO#3519: Integrate screen rotation patches into stock kernel and X server. Luarvique L. Luarvique luarvique at gmail.com * Force building with vfp on ARM to match the official Nokia package, and since it doesn't compile without it anyway. * Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=6502: RandR fails after some time. Marius Gedminas mgedmin at b4net.lt 3. Does this in any way or shape relate to having qt 4.6 on Diablo? Does it make any easier/harder? No, or at least not yet. I honestly don't know what issues there are to be solved for this, but if there's anything we can do I'm all ears. L. ___ maemo-developers mailing list
Re: Community updates for diablo
Am Dienstag, den 04.05.2010, 17:04 +0100 schrieb Lucas Maneos: 4. Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update. At least for me the bottom right button was disabled. I had to click Check for updates first which enabled the button and then listed OS2008 Community SSU 5.2010.16-1, 4.4MB. Installing worked perfectly fine. Congrats and big kudos to everybody involved! andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Tuesday 04 May 2010 17:04:07 Lucas Maneos wrote: Thanks to Niels who spent this afternoon working on this, we now have maemo.org signed repositories! Without further ado, they are: deb http://repository.maemo.org/community/ diablo free non-free deb http://repository.maemo.org/community-testing/ diablo free non-free The community/ one is supposed to be the stable one and is currently empty, while community-testing now holds the contents of my private testing repository. Will there be any SDK/autobuilder updates to go with this? I am assuming anything built with the current autobuilder should work with this community update -- is that right? Are there any updates to any libraries? Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
autobuilder (non) optification ?
Did anyone have problems with autobuilder optification lately ? On user request, I have just dropped 'auto' into the debian/optify file as usual to some of the bigger packages, but to my surprise the package went through the autobuilder unoptified. Niels gave it a cursory look and apparently there is nothing wrong with the package (except for a botched timestamp which should have no effect on optification), so it's a bit of a puzzle as to what happened here. A source package demonstrating the problem: http://maemo.org/packages/source/view/fremantle_extras- devel_free_source/abiword/2.8.1-2/ Any ideas or similar experiences ? Regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: git over ssh access for garage projects - calling for brave testers
On Wed, Apr 28, 2010 at 3:50 PM, Ferenc Szekely fer...@maemo.org wrote: Our git over ssh support works side by side with the current WebDAV access, so you can use both for reading / writing the repo. Quick how-to 1. Upload your public SSH key to garage: https://garage.maemo.org/account/ Has been this disabled? It sounds stupid, but I'm not able to find the box to fill the SSH public key. Javier Palacios ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
